Cloudflare Email Authentication Guide

Before you start

• You need access to the DNS settings for your domain. This is usually at your domain registrar or DNS provider (Cloudflare, Namecheap, GoDaddy, etc.).
• You need to know which email service sends your mail (Google Workspace, Microsoft 365, etc.) so you can look up the correct SPF and DKIM values for that service.
• DNS changes take time to propagate. After saving a record, wait at least 15-30 minutes before testing.

SPF Setup for Cloudflare

SPF (Sender Policy Framework) is a DNS TXT record that lists which mail servers are allowed to send email on behalf of your domain. Receiving servers check it to decide whether to accept or flag your mail.

Cloudflare is a DNS and CDN provider, not an email sender. The SPF value depends on which email service you use. Add TXT records in Cloudflare's DNS panel with Proxy status set to DNS only (grey cloud).

SPF record for Cloudflare

Type: TXT    Host/Name: @    Value: v=spf1 include:YOUR-EMAIL-PROVIDER ~all

Steps

1. Open your DNS provider and look for an existing TXT record at host @ that starts with v=spf1.
2. If one exists, edit it and add the new include. Never create a second SPF record. If none exists, create a new TXT record at @ with the value above.
3. For Google Workspace on Cloudflare DNS, use v=spf1 include:_spf.google.com ~all. For Microsoft 365, use v=spf1 include:spf.protection.outlook.com ~all.
4. Use ~all (softfail) while testing. Move to -all (hardfail) only after confirming all legitimate senders are covered.
5. Save and wait for DNS propagation.

DKIM Setup for Cloudflare

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outgoing email. Receiving servers verify the signature against a public key you publish as a DNS TXT record. A valid DKIM signature proves the message was not altered in transit and that it came from an authorized sender.

Selector for Cloudflare: provided by your email service (depends on which platform sends your mail)

Steps

1. In Cloudflare, go to your site → DNS → Records → Add record.
2. Select TXT as the type. In the Name field, enter just the selector subdomain (for example, google._domainkey for Google Workspace).
3. Paste the full DKIM key value in the Content field.
4. Set Proxy status to DNS only (grey cloud). Click Save.

Verify DKIM

• Send a test email to a Gmail address and open it. Click the three-dot menu → "Show original". Look for dkim=pass in the authentication results.
• From the command line:
  

  dig TXT selector._domainkey.yourdomain.com +short

• Or use the InboxGreen DKIM checker.

DMARC Setup for Cloudflare

DMARC (Domain-based Message Authentication, Reporting, and Conformance) ties SPF and DKIM together. It tells receiving servers what to do with mail that fails both checks, and sends you reports about who is sending email on behalf of your domain. DMARC also requires alignment: the domain in your visible From header must match the domain authenticated by SPF or DKIM.

Add DMARC as a TXT record at host _dmarc in Cloudflare DNS with Proxy status set to DNS only (grey cloud). The record value is the same as for any other DNS provider.

The three-stage approach

Stage	DNS value	When to use it
Monitor	v=DMARC1; p=none; rua=mailto:[email protected]; fo=1	Start here. Collects reports without blocking any mail.
Quarantine	v=DMARC1; p=quarantine; pct=25; rua=mailto:[email protected]; fo=1	After 2-4 weeks at p=none with clean reports. Sends some failing mail to spam.
Reject	v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; fo=1	Full protection once SPF and DKIM alignment is verified.

Publish the DMARC record

1. Create a TXT record at host _dmarc (not @) with the p=none value above.
2. Replace [email protected] with a real inbox that can receive XML report emails.
3. Wait for DNS propagation, then verify with dig TXT _dmarc.yourdomain.com +short.
4. After 2-4 weeks, review the reports and tighten the policy when alignment looks healthy.

List-Unsubscribe for Cloudflare

The List-Unsubscribe header gives inbox providers like Gmail and Outlook a machine-readable way to offer a one-click unsubscribe button. When it is present and valid, Gmail shows an "Unsubscribe" link next to the sender name without the recipient needing to scroll to the bottom of the email. This reduces spam complaints and protects your sender reputation.

How to enable it

1. In your sending platform or email template, enable the List-Unsubscribe header option. Most platforms (SendGrid, Mailgun, Brevo, Shopify Email) have a toggle or a macro for this.
2. Use a one-click HTTPS unsubscribe URL as the primary method. Include a mailto: address as fallback.
3. Add the List-Unsubscribe-Post header to declare one-click support (required by Gmail's February 2024 guidelines for senders above 5,000 messages/day).

Example headers

List-Unsubscribe: <https://yourdomain.com/unsubscribe/TOKEN>, <mailto:[email protected]?subject=unsubscribe>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

Common mistakes

• Using a broken or expired token in the unsubscribe URL. Inbox providers test the link periodically.
• Only providing a mailto: link without a one-click HTTPS URL. Gmail and Outlook prefer the HTTPS method.
• Not honoring the unsubscribe request immediately. Gmail requires that one-click unsubscribes are processed within two business days.

To verify, send a test email to a Gmail address and look at "Show original". You should see the List-Unsubscribe header in the raw message headers.

Verify All Four Records

After publishing all records, run these checks:

Record	Command	What to look for
SPF	dig TXT yourdomain.com +short	One TXT record starting with v=spf1
DKIM	dig TXT selector._domainkey.yourdomain.com +short	A TXT record starting with v=DKIM1
DMARC	dig TXT _dmarc.yourdomain.com +short	A TXT record starting with v=DMARC1
All three	InboxGreen Free Check	Green pass on SPF, DKIM, and DMARC

Common Mistakes with Cloudflare

• Setting TXT records to Proxied (orange cloud) instead of DNS only (grey cloud). Proxied TXT records do not resolve correctly.
• Entering the full domain name in the Name field (like <code>google._domainkey.yourdomain.com</code>) when Cloudflare only needs the subdomain portion (<code>google._domainkey</code>).
• Checking propagation immediately after saving. Even though Cloudflare is fast, give it a few minutes before testing.

---

Free Deliverability Scan

Check SPF, DKIM, DMARC and List-Unsubscribe for your domain in seconds.

scan Run Scan

Related Tools

SPF Lookup

See your live SPF record, count DNS lookups, and spot duplicate records or syntax problems.

DKIM Checker

Look up any DKIM selector on any domain. Confirms the key exists and shows its length.

DMARC Lookup

Fetch your live DMARC record, validate syntax, and check policy and reporting configuration.

Email Header Analyzer

Paste raw email headers to see SPF, DKIM, and DMARC results in one view.

SPF Generator

Build a valid SPF record from scratch for any combination of sending services.

DMARC Generator

Build a DMARC record with the right policy, pct, and rua settings for your stage.

TXT Lookup

See all TXT records on your domain to catch duplicate SPF records or missing entries.

DKIM Generator

Generate a 2048-bit DKIM key pair if your ESP requires you to manage your own keys.

Related Reading

Common Questions

What DNS records do I need for Cloudflare?

Cloudflare is your DNS provider, not your email sender. The records you need depend on which email service you use. Check your email provider's documentation for the exact SPF, DKIM, and DMARC values, then add them as TXT records in Cloudflare's DNS panel with Proxy status set to DNS only (grey cloud).

How long does it take for SPF, DKIM, and DMARC to start working?

Most DNS changes propagate within 15 to 60 minutes, but the full TTL can extend to 48 hours on some registrars. Always wait at least 30 minutes before testing. If a change isn't showing up after an hour, use the SPF Lookup or DKIM Checker to query live DNS rather than relying on cached results.

Can I have two SPF records?

No. RFC 7208 requires exactly one SPF TXT record at your domain root. Two records cause a PermError regardless of their content. If you send through multiple services, merge all the includes into a single record: v=spf1 include:service1.com include:service2.com ~all. Use the TXT Lookup to confirm you only have one.

What DMARC policy should I start with?

Start with p=none to collect reports without affecting delivery. After 2 to 4 weeks of reports showing all legitimate sources passing alignment, move to p=quarantine at a low percentage (pct=10), then increase gradually. Move to p=reject only when you are confident every legitimate sending source aligns correctly.

Why does DMARC fail even though SPF and DKIM both pass?

DMARC requires alignment, not just a pass. SPF alignment means the envelope sender domain (the Return-Path address) must match your From: domain. DKIM alignment means the d= tag must match your From: domain. If your ESP signs with its own domain or uses its own envelope sender, both protocols pass independently but DMARC alignment fails. Fix this by enabling custom domain authentication at your ESP.

mail_lock

Get the Cloudflare authentication checklist

The exact DNS records, step-by-step verification commands, and the common mistakes to avoid.

mark_email_read Join newsletter

1-2 emails per week. Unsubscribe anytime.