Free tool
Email deliverability checker
Check the four DNS records that decide whether your email reaches the inbox: SPF, DKIM, DMARC and MX. You get a plain-English verdict and the fix for each one.
Check a domain
Lookups run from your browser to Cloudflare’s public DNS; we don’t receive or store the domain you enter.
The resolver is cloudflare-dns.com. DNS records are public, so this only reads what any mail server can see.
What you will see
- SPF: Lists the servers allowed to send email as your domain.
- DKIM: A cryptographic signature that proves a message was not changed and really came from your domain.
- DMARC: Tells receivers what to do when SPF and DKIM fail, and sends you reports.
- MX: The servers that receive email for your domain, including replies and bounces.
Methodology
What we check and how
Each check reads public DNS records and applies the rules in the published standards. It cannot see inside your email platform, so a pass here means the DNS side is right, not that every message lands in the inbox.
SPF (RFC 7208)
We look for exactly one TXT record starting v=spf1 at your domain. We flag more than one record, a +all or ?all ending, a missing all, the deprecated ptr mechanism, and more than 10 DNS-lookup terms at the top level (nested includes add more, so a high count is a lower bound).
DKIM (RFC 6376, RFC 8301)
DKIM keys live at <selector>._domainkey.<domain>, and only your provider knows the selector name. We try your selector first, then the common ones listed above. We flag revoked keys (empty p=), RSA keys under 1024 bits (below the minimum) and under 2048 bits (below the recommendation).
DMARC (RFC 7489)
We look for one TXT record starting v=DMARC1 at _dmarc.<domain>. p=none passes Gmail's and Yahoo's bulk-sender rules but only monitors; p=quarantine or p=reject protects your domain. We also check for a rua= report address.
MX (RFC 5321, RFC 7505)
We list your mail servers in priority order. No MX records means replies and bounce reports cannot reach you; a "null MX" (0 .) means the domain deliberately accepts no email.
Why it matters now
Since 1 February 2024, Gmail asks everyone who sends to Gmail accounts to set up SPF or DKIM, and senders of more than 5,000 messages a day to set up SPF, DKIM and DMARC (a policy of none is accepted). Yahoo’s bulk-sender rules also ask for SPF, DKIM and a DMARC policy of at least p=none. Sources: Google email sender guidelines (opens in a new tab) and Yahoo sender best practices (opens in a new tab), both read on 15 November 2026.
What this check cannot see: whether each sending service signs with your domain (alignment), your sending IP’s reputation, list quality and complaint rates. A message header from a real send shows alignment; your email platform’s reports show the rest.
Next step
Want your records fixed and your email set up properly?
We set up SPF, DKIM and DMARC alongside your email marketing and CRM, and check them before anything goes out.