Email Deliverability Checker
One domain, one score. Check SPF, DKIM, DMARC, MX, and BIMI together and get a 0-100 deliverability score with prioritized fixes.
What this deliverability checker does
This is the all-in-one check. Enter your domain and it runs your SPF, DKIM, DMARC, MX, and BIMI configuration in a single scan, then scores your setup out of 100 and lists what to fix first.
It's the fastest way to see whether your sending infrastructure is ready. Authentication is the foundation of deliverability: if SPF, DKIM, or DMARC is missing or misconfigured, your mail is far more likely to land in spam no matter how good your copy is.
What goes into the score
SPF (25 pts)
A valid record under the 10-lookup limit with a sane enforcement level. Partial credit if it's valid but near the limit.
DKIM (25 pts)
A valid public key found at a common selector, so your mail can be signed and verified.
DMARC (30 pts)
An enforcing policy (quarantine or reject) scores full; monitor mode (p=none) earns half.
MX (20 pts)
Working mail servers so the domain can send and receive.
BIMI (bonus)
Optional brand logo. A small bonus once everything else is in order, never counted against you.
What your score means
The number is a shorthand for how ready your sending setup is. Here is how to read the bands.
| Score | Grade | What it means |
|---|---|---|
| 90 to 100 | Excellent | Your infrastructure is solid. Maintain it and monitor for changes. |
| 70 to 89 | Good, room to improve | You reach the inbox most of the time, but specific issues are dragging the score down. |
| 50 to 69 | Needs attention | You're probably landing in spam for a meaningful share of recipients. |
| Under 50 | Serious problems | Most of your mail is likely going to spam or being rejected. |
What actually affects deliverability
Deliverability is reaching the inbox - not the spam folder, not a bounce, not a black hole. It isn't the same as delivery rate: delivery rate just counts accepted mail, while deliverability measures inbox versus spam.
The factors that decide it, roughly in order: sender reputation (history, complaints, bounces, engagement, volume patterns), authentication (SPF, DKIM, DMARC), list hygiene, sending patterns (consistent looks legitimate, erratic bursts look like spam), and content quality. Content matters, but less than most people think - authentication and reputation carry far more weight.
Deliverability for cold email
Cold email is held to a higher bar because you're emailing people who didn't opt in, so mailbox providers give you less room for error. The setup that survives it is specific: send from separate domains (never your primary business domain), authenticate every sending domain properly, warm up each mailbox gradually over two to four weeks, and rotate volume across mailboxes and domains rather than blasting from one.
A common symptom of getting this wrong is a cold-email open rate below 15 to 20 percent - almost always an authentication or reputation problem rather than a copy problem. Good cold email is also short (50 to 125 words), plain-text, with zero or one links, and reads like a human wrote it.
How to improve your deliverability
Work top to bottom - the earlier steps have the biggest impact.
Frequently asked questions
What is a good deliverability score?
Aim for 80 or above. That means SPF, DKIM, and DMARC are all in place and enforcing, with working mail servers. Below 50 means core authentication is missing or broken. In real terms, 85 percent or higher inbox placement is reasonable and top performers reach 95 percent-plus.
Does authentication guarantee inbox placement?
No. Authentication is necessary but not sufficient - content, sending reputation, warmup, and list quality also matter. But without it, even great campaigns struggle to reach the inbox.
How often should I test my deliverability?
Monthly as a baseline, and weekly if you run active cold email - plus any time you add a new sending service, change DNS, or launch onto a new domain.
What should I fix first?
Follow the prioritized findings: SPF and DKIM come first (they let receivers verify you), then move DMARC from monitor to enforcing. BIMI is last and optional.
How long does it take to improve deliverability?
Authentication fixes take effect within days. Rebuilding reputation after a rough patch takes two to four weeks of clean, consistent sending.
Is cold email deliverability different?
The fundamentals are identical, but the margin for error is smaller because recipients didn't opt in. Separate domains, proper authentication, warmup and volume rotation are what make it work.
Next steps
Stop configuring DNS by hand
Cladiant provisions real Google Workspace, Microsoft 365, and Azure Entra mailboxes with SPF, DKIM, and DMARC written and verified on every domain before a single message sends. No DNS headaches, no authentication gaps, one invoice.