Cloudflare Email Security Setup
Budget / Salary$10–30
TypeFreelance project
LocationRemote
Posted1 hour ago
I need clear, fool-proof written guidance that walks me through securing my domain’s email security inside Cloudflare. My mail is handled by a platform other than Gmail or Office 365, so please keep your examples using a template email address “info at example dot com”
The guide must cover:
• How to reach and edit the DNS zone from my domain registrar’s dashboard—Screenshots or annotated visuals are welcome, but text alone is fine as long as every click and menu name is spelled out.
• Exact TXT records I should publish for SPF, DKIM and DMARC, including syntax, recommended alignment settings and the reasoning behind each tag.
– SPF: single flattened record that avoids the 10-lookup limit.
– DKIM: key generation, selector naming, and where to paste the public key.
– DMARC: policy options (none, quarantine, reject) and guidance on moving from monitoring to enforcement without disrupting legitimate traffic.
• Any additional Cloudflare-specific toggles or “Email Security” features that harden the domain against spoofing (for example, orange-cloud vs grey-cloud behaviour on MX, opportunistic TLS, etc.).
• A simple validation checklist so I can confirm everything is propagating correctly with tools like dig, nslookup, Cloudflare’s DNS checker, or third-party DMARC analyzers.
I’ll consider the job done when I can copy your instructions verbatim, publish the records, and see them pass alignment tests on MXToolbox or similar lookup tools with no spoofing warnings and can successfully test email sending and receiving flow .
I will give preferrence to live one-on-one session to get this done
The guide must cover:
• How to reach and edit the DNS zone from my domain registrar’s dashboard—Screenshots or annotated visuals are welcome, but text alone is fine as long as every click and menu name is spelled out.
• Exact TXT records I should publish for SPF, DKIM and DMARC, including syntax, recommended alignment settings and the reasoning behind each tag.
– SPF: single flattened record that avoids the 10-lookup limit.
– DKIM: key generation, selector naming, and where to paste the public key.
– DMARC: policy options (none, quarantine, reject) and guidance on moving from monitoring to enforcement without disrupting legitimate traffic.
• Any additional Cloudflare-specific toggles or “Email Security” features that harden the domain against spoofing (for example, orange-cloud vs grey-cloud behaviour on MX, opportunistic TLS, etc.).
• A simple validation checklist so I can confirm everything is propagating correctly with tools like dig, nslookup, Cloudflare’s DNS checker, or third-party DMARC analyzers.
I’ll consider the job done when I can copy your instructions verbatim, publish the records, and see them pass alignment tests on MXToolbox or similar lookup tools with no spoofing warnings and can successfully test email sending and receiving flow .
I will give preferrence to live one-on-one session to get this done
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.