Email Authentication Checker (SPF, DMARC, DKIM)
Check the DNS records that tell receivers whether mail from your domain is authorized: SPF, DMARC, DKIM and MTA-STS.
What it checks
- Reads the root TXT record for SPF and flags a missing all mechanism, or +all, ?all or ~all
- Estimates the SPF DNS-lookup count from include, a, mx, ptr, exists and redirect terms, against the limit of 10
- Reads the _dmarc TXT record and reports the p=, pct= and rua= values
- Probes ten common DKIM selectors and reports any that publish a DKIM1 key
- Checks the _mta-sts TXT record for v=STSv1 and lists MX hosts by priority
How to read the result
- Each warning carries a severity label (high, medium, low or info) set by the code. The labels are not a combined risk score.
- p=none only monitors and does not stop spoofed mail. p=quarantine and p=reject enforce the policy, and the tool suggests p=reject as the strictest setting.
- A DKIM miss means none of the ten selector names answered. Many senders use other selectors, so confirm the selector in your sending service's settings.
What it does not tell you
This is a DNS record check. It does not send mail, check SPF, DKIM and DMARC alignment, verify DKIM signatures or confirm how receivers enforce the policy. This is not a penetration test.
Data sources
TXT and MX records are requested over DNS-over-HTTPS from Cloudflare's public resolver for the domain, _dmarc, _mta-sts and the ten DKIM selector names.
No login · 30 calls / hour / IP · Data stored in the EU
FAQ
Does the tool check DMARC alignment?
No. It reads the DMARC policy tags but does not compare the From domain with the SPF or DKIM domains.
My DKIM shows as not found, but my mail is signed. Why?
Your sending service may use a selector name that is not in the tool's list of ten. A miss is therefore not conclusive.
Go deeper: Email Security engine (SPF, DKIM, DMARC and MTA-STS)
Guide: SPF, DKIM and DMARC setup guide: stop domain spoofing