Guide · Cloudflare

Email authentication on Cloudflare: SPF, DKIM and DMARC

If Cloudflare runs your domain's DNS, this is where your email's three protections live: SPF, DKIM and DMARC. Here's how to set each one up in Cloudflare's dashboard, in the order that keeps your email working.

Cloudflare steps checked by hand on 22 Nov 2026 · Cloudflare's own help page

Check your domain first: the checkup shows exactly which of these steps you still need.

1. SPF: list the servers that send your email

Your email provider tells you what to put in SPF. For Google Workspace it's include:_spf.google.com, for Microsoft 365 include:spf.protection.outlook.com. A domain may have only one SPF record: if you already have a TXT record on @ that starts with v=spf1, edit that one and add the new include to it instead.

  1. Log in to Cloudflare at dash.cloudflare.com and click yourbusiness.com in your list of domains.
  2. In the menu on the left, open DNS, then Records.
  3. Click "Add record".
  4. In Type, choose TXT.
  5. In Name, type @ (Cloudflare's sign for yourbusiness.com itself): Name@
  6. In Content, paste: Contentv=spf1 include:_spf.google.com ~all
  7. Leave TTL on Auto and click Save. Changes usually show within a few minutes. Then check your domain with the box at the top of this page.

2. DKIM: publish your email provider's signing key

Your email provider creates the key and shows you the record to add: usually a TXT record (Google, Zoho) or CNAME records (Microsoft 365, Proton, Fastmail). Here it is with Google Workspace's TXT record; a CNAME works the same way, with Proxy status off.

  1. Log in to Cloudflare at dash.cloudflare.com and click yourbusiness.com in your list of domains.
  2. In the menu on the left, open DNS, then Records.
  3. Click "Add record".
  4. In Type, choose TXT.
  5. In Name, type only this. Cloudflare adds .yourbusiness.com for you: Namegoogle._domainkey
  6. In Content, paste the value your email provider shows (it starts with v=DKIM1).
  7. Leave TTL on Auto and click Save. Changes usually show within a few minutes. Then check your domain with the box at the top of this page.

3. DMARC: start by watching, then protect

Start with p=none: it changes nothing for your email, but receivers send you daily reports about who sends email in your name. Make sure the report address exists, or change it to one you read.

  1. Log in to Cloudflare at dash.cloudflare.com and click yourbusiness.com in your list of domains.
  2. In the menu on the left, open DNS, then Records.
  3. Click "Add record".
  4. In Type, choose TXT.
  5. In Name, type only this. Cloudflare adds .yourbusiness.com for you: Name_dmarc
  6. In Content, paste: Contentv=DMARC1; p=none; rua=mailto:dmarc-reports@yourbusiness.com
  7. Leave TTL on Auto and click Save. Changes usually show within a few minutes. Then check your domain with the box at the top of this page.

After two to four weeks of reports showing your real email passing, change p=none to p=quarantine, and later to p=reject. Our checkup tells you when your setup is ready.

Common mistakes

  • Leaving Proxy status on (orange cloud) for DKIM or verification CNAME records. They must be DNS only (grey cloud), or receivers can't read your key.
  • Adding a second SPF record instead of editing the first. With two, receivers ignore both.
  • Turning on Cloudflare Email Routing and forgetting that it adds its own SPF include. Keep one SPF record that lists every service that sends for you.
  • Leaving DMARC at p=none for ever. It's the right start, but it doesn't stop anyone sending email in your name.
  • Switching on DNSSEC in Cloudflare but never adding the DS record at your registrar (or adding it with a typo). Copy all four values exactly.

The examples use yourbusiness.com: put your own domain where you see it. Our checkup fills in your real values for you.