Cloudflare DNS records for sending domains
Add and verify records when Cloudflare manages DNS.
Cloudflare is often the source of truth even when the domain was purchased elsewhere.
What this helps you do
Cloudflare is often the source of truth even when the domain was purchased elsewhere.
Recommended workflow in Outlio
Open the domain in Cloudflare and go to DNS Records.
Add MX, SPF, DKIM, and DMARC records from your email provider.
Set custom tracking CNAME records to DNS only when appropriate.
Avoid proxying mail authentication records.
Retest in Outlio after propagation.
Quality checks
- Orange-cloud proxy is for web traffic, not email authentication.
- TXT records should be copied exactly.
- Cloudflare propagation is usually fast, but external caches can lag.
Common mistakes to avoid
- Proxying a tracking CNAME when the target expects DNS-only.
- Editing registrar DNS when nameservers point to Cloudflare.
Done well, this should leave you with
A cleaner Outlio setup, fewer avoidable campaign issues, and a more reliable path from setup to replies.
Related articles
Why do I need DNS records?
Understand SPF, DKIM, DMARC, MX, and tracking records.
How to setup MX, SPF, DKIM, DMARC
Step-by-step DNS setup for sending domains.
SPF, DKIM, and DMARC for Google Workspace
Configure Google Workspace authentication for outreach.
SPF, DKIM, and DMARC for Microsoft 365
Configure Microsoft 365 authentication.
Namecheap DNS with Google Workspace
Add Google Workspace records in Namecheap.
Namecheap DNS with Microsoft 365
Add Microsoft 365 records in Namecheap.
Was this article helpful?
Need more help? Contact Support