Technical Deep-Dive & Remediation Playbook

Complete Copy-Paste Cloudflare DNS Table for Google Workspace

Exact Cloudflare DNS Records for Google Workspace

In your Cloudflare Dashboard, navigate to DNS → Records and ensure these authentication records are published (DNS records for TXT and MX are automatically set to DNS Only):

TypeName (Host)Content / ValueTTL
MX@1 smtp.google.comAuto
TXT@v=spf1 include:_spf.google.com ~allAuto
TXTgoogle._domainkeyv=DKIM1; k=rsa; p=MIIBIjANBgkqh... (From Google Admin)Auto
TXT_dmarcv=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@yourdomain.com;Auto

Critical Mistake to Avoid in Google Admin Console

After pasting your google._domainkey TXT record into Cloudflare, you must return to Google Admin Console → Apps → Google Workspace → Gmail → Authenticate email and click "Start Authentication". Until you click that button, Google Workspace will not sign your outgoing emails with DKIM!

Free Interactive Generator

SPF & DMARC Record Fix-It Builder

Select every service that sends email from your domain to generate a clean, merged SPF record (within the 10-lookup limit) and a compliant DMARC policy.

1. Select Your Email Providers & Marketing Senders

Generated SPF TXT Record
Host / Name: @
Est. DNS Lookups: ~3 / 10
v=spf1 include:_spf.google.com ~all
Generated DMARC TXT Record
Host / Name: _dmarc
RFC 7489 Compliant
v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@yourdomain.com; adkim=r; aspf=r;
Step-by-Step DNS Playbooks

Popular Email & DNS Provider Setup Guides

Copy-paste configurations for the most common domain registrars and email platforms.

Email Deliverability Knowledge Base

Frequently Asked Questions

Why does having two SPF records break email delivery?

RFC 7208 Section 3.2 explicitly states that a domain must not have multiple TXT records starting with v=spf1. If you add a second SPF record for Mailchimp or SendGrid instead of merging the include: tags into one record, receiving servers return SPF PermError and treat your authentication as failed.

How do I fix "SPF Too Many DNS Lookups" (>10 limit)?

Every include:, a, mx, ptr, and redirect= inside your SPF record (and nested inside your providers' SPF records) counts toward the strict 10-lookup ceiling. Remove unused senders, drop redundant a/mx tags, or move marketing/transactional emails onto a subdomain like mail.yourdomain.com.

Is DMARC p=none enough for Gmail and Yahoo?

v=DMARC1; p=none; satisfies the minimum entry requirement for bulk senders, but it offers zero protection against phishers spoofing your domain. Once you verify your legitimate email services pass SPF and DKIM, upgrade to p=quarantine or p=reject.

Why wasn't my DKIM key auto-detected?

Unlike SPF and DMARC (which live at fixed DNS locations), DKIM keys live at <selector>._domainkey.yourdomain.com. AmIInSpam.com automatically probes 16 common selectors (google, selector1, s1, k1, resend, etc.). If you use a custom selector, enter it in the DKIM Inspector box to verify it directly.