Security Tools

🩺 SPF / DMARC / DKIM Auditor

Enter a domain and check live whether it is protected against email spoofing. We query its SPF, DMARC and DKIM over DNS-over-HTTPS, grade them, tell you what fails and —depending on where you are— lay out the phased plan to p=reject without breaking legit mail.

📊 And big companies? This is how the IBEX 35 fares →

📐 How we score · methodology 2026.2

The grade combines SPF (35%), DMARC (40%) and DKIM (25%). It is the same in this auditor, on each result’s shareable page, in the badge and in the Posture Radar.

Capped by real protection. The grade cannot be better than the anti-spoofing protection your DMARC policy provides: without DMARC, anyone can spoof your domain in the visible sender, however good SPF and DKIM are.

DMARC policyMaximum grade
No DMARCF
Invalid p policyF
p=noneD
p=quarantine · pct<100C
p=quarantineB
p=reject · pct<100B
p=rejectno cap

Undetected DKIM is not penalised. Without knowing the selector, DKIM cannot be discovered through DNS, and many organisations use custom selectors. If we do not find it with the common ones, the grade comes from SPF and DMARC only. If we find it and it is wrong (revoked or 1024-bit key), it does count.

Scale: A ≥ 90 · B ≥ 75 · C ≥ 55 · D ≥ 35 · F < 35.

We only read public DNS records: the ones any mail server looks up when it receives a message from you. We send no mail and never connect to your servers.

Frequently asked questions

How does it query the records with no backend?
It uses Cloudflare DNS-over-HTTPS from your browser to read the domain's SPF, DMARC and DKIM TXT records. There is no intermediate server: the query goes from your browser to the DNS resolver, and the domain you audit is public information.
Why does it sometimes not detect DKIM?
DKIM is published under a "selector" (selector._domainkey.domain) that cannot be reliably guessed. We probe the most common selectors; if yours is custom, type it in the selectors field so it can be checked.
How is the grade calculated?
Each record is scored separately (the "all" policy in SPF, p/rua/pct in DMARC, key presence and strength in DKIM) and combined weighting DMARC and SPF more, since they are what actually stop spoofing. The grade runs A to F.
What if it finds problems?
Each issue comes with an explanation of how to fix it, plus a link to the SPF/DMARC/DKIM Generator to build the correct record and publish it in your DNS.