Email Deliverability Checker
Enter a domain or email address to check its SPF, DKIM, DMARC, MX and BIMI setup, and get a 0 to 100 deliverability score, a plain-English spam-filter risk read, and the exact fixes. This is the authentication foundation that decides whether Gmail, Yahoo and Outlook trust your mail. No records handy? Paste them in by hand instead.
🔎 Runs in your browser over public DNS (Cloudflare, then Google). No account, no server of mine.We look up public DNS records only. Enter a custom DKIM selector if you know it, otherwise we scan the common ones.
Checking...
This score, and the spam-filter risk beside it, grade the DNS authentication that mailbox providers check first: it is the foundation of deliverability, not a guarantee of inbox placement, and the risk figure is estimated from authentication strength, not a message-content test. A full spam-content score (the kind mail-tester gives) needs a real message sent to a probe inbox, which a browser tool cannot do. Records are read live from public DNS and nothing is stored.
Drag a .csv, .tsv or .xlsx file here, or . We read the domains from any column and check each one.
Up to 200 domains per run. Email addresses are reduced to their domain and duplicates are removed. In bulk, DKIM uses a quick scan of the most common selectors. An .xlsx file loads a small reader on demand.
Results
| Domain | Score | Verdict | SPF | DKIM | DMARC | MX | Top fix |
|---|
DNS authentication only, read live from public DNS. This is the deliverability foundation, not an inbox-placement or spam-content guarantee.
Paste the DNS records you already have and grade them with no lookup at all. Nothing leaves your browser. Use this on a network that blocks DNS-over-HTTPS, or to check records before you publish them. Leave a box blank only if that record does not exist; a blank box is graded as missing.
Checking...
Graded from the records you pasted, on the same 0 to 100 scale. This is the authentication foundation, not an inbox-placement guarantee, and the spam-filter risk beside it is estimated from authentication strength, not a message-content test.