Skip to content

SPF & DMARC Checker - Validate Email DNS Records

What this checker tests

Enter a domain or an email address. The tool reads the domain's TXT records and the TXT record at _dmarc. on that domain, straight from Google Public DNS in your browser. It then validates them the way a receiving mail server would and gives each part a pass, warning or fail with a plain-English fix.

  • SPF: one record only, valid syntax, every include resolved, the 10 DNS lookup limit counted across the whole chain, void lookups (includes that return nothing), and a safe all at the end.
  • DMARC: one record, a valid p= policy, subdomain policy sp=, pct=, report addresses rua= and ruf=, and alignment modes adkim= and aspf=.
  • DKIM (optional): the public key at selector._domainkey, whether it has been revoked, and its approximate RSA key size.

How SPF, DKIM and DMARC fit together

SPF lists the servers allowed to send mail for your domain. DKIM adds a signature to each message that receivers check against a public key in DNS. DMARC ties them to the address people see in the From line: a message passes DMARC if SPF or DKIM passes and the domain they checked matches the From domain. Your DMARC policy then tells receivers what to do with mail that fails, and where to send reports. Gmail, Yahoo and Microsoft now expect all three from anyone sending in bulk.

Example

A domain publishes v=spf1 a mx include:_spf.google.com include:sendgrid.net include:mailgun.org include:spf.protection.outlook.com ?all. That looks like six lookups, but some providers nest includes. Google and Microsoft cost one lookup each, SendGrid two, and Mailgun five, because mailgun.org includes two records that each include two more. With a and mx the total is 11. The checker reports a fail for going over 10 and a warning for ?all, which offers no protection. Dropping the unused a and mx brings it to 9; ending with ~all fixes the warning.

The same domain has v=DMARC1; p=none and no rua=. The checker warns that p=none does not block spoofing and that without rua you get no reports. A better starting record is v=DMARC1; p=none; rua=mailto:dmarc@example.com, moving to p=quarantine once the reports look clean.

Limits of this check

The tool fetches include and redirect targets to count lookups. It does not resolve every a, mx or exists target, so void lookups from those are not detected. Each check makes a bounded number of DNS queries (at most about 20). DMARC is read only from _dmarc on the exact domain you enter. A subdomain such as mail.example.com with no record of its own is covered by the parent domain's policy, so check example.com as well before treating a missing DMARC record as a problem. To see the raw TXT records, use the DNS lookup. If you are moving mail providers, the propagation checker shows when the new records are live.

Related Tools

Frequently Asked Questions

What is the SPF 10 lookup limit?
A receiver may make at most 10 DNS lookups while checking SPF. Each include, a, mx, ptr, exists and redirect costs one, and includes inside includes count too. Over 10, the result is PermError, which most receivers treat as a fail. The checker follows the include chain and gives you the total.
Can I have two SPF records?
No. A domain must publish exactly one TXT record starting with v=spf1. Two cause a PermError. Merge them: one v=spf1 at the start, the include and ip4 terms combined, and a single all at the end.
Should I use ~all or -all?
Either works once DMARC is in place, because DMARC decides what happens to failing mail. ~all (softfail) is safer while you are still finding all your senders; -all (fail) is stricter. Never use +all, which authorises every server on the internet.
Is p=none a valid DMARC policy?
Yes, and it is the right place to start: you get reports without affecting delivery. It does not stop spoofing. Read the rua reports for a few weeks, fix legitimate senders that fail, then move to p=quarantine and then p=reject.
Why does DMARC fail when SPF passes?
Alignment. SPF checks the envelope sender (the Return-Path), which for a mailing service is often its own domain, not yours. DMARC only counts an SPF pass if that domain matches the From domain. Set up DKIM signing with your own domain, or a custom return-path at the provider, and DMARC will pass.
How do I find my DKIM selector?
Open a message you sent, view the original headers and find DKIM-Signature. The s= tag is the selector. Google Workspace uses google, Microsoft 365 uses selector1 and selector2, and many services use k1, s1 or default. Scan common selectors tries those for you.