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
allat the end. - DMARC: one record, a valid
p=policy, subdomain policysp=,pct=, report addressesrua=andruf=, and alignment modesadkim=andaspf=. - 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:[email protected],
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
DNS Lookup
Look up A, AAAA, MX, TXT, NS, SOA, CAA, SRV, DS, HTTPS and more, or all records at once, via Google, Cloudflare or AliDNS.
Reverse DNS Lookup
Find the hostname associated with an IP address using PTR record lookups.
DNS Propagation Checker
Check whether a DNS change has propagated by comparing answers and TTLs across Google, Cloudflare and AliDNS resolvers.
WHOIS Lookup
Look up domain registration data via RDAP: registrar, expiry date, status codes, nameservers and DNSSEC.