Email Deliverability Score
Score a domain's email authentication out of 100 with a shareable badge.
Enter a domain to get a single email deliverability score out of 100, with a letter grade and a transparent breakdown of how it was reached. We run five live DNS checks, covering DMARC, SPF, MTA-STS, DNSSEC and BIMI, and show exactly how many points each one earns. No sign-up, nothing stored. The weighting is published in full below, so you can see precisely why your domain scored what it did.
We check the public DNS for this domain only. Try your own domain, or a brand you receive mail from.
The Email Deliverability Score checks a domain's published email-authentication records and condenses them into a single figure out of 100, with a shareable badge. It looks at the records receivers actually use to decide whether your mail is trustworthy, so a high score signals that your domain is hard to spoof and well positioned to reach the inbox.
What the score measures
The tool inspects the live DNS for the building blocks of authentication and deliverability, then weights them:
- DMARC (RFC 7489): whether a record exists and, crucially, whether it is at enforcement (
p=quarantineorp=reject) rather thanp=none. - SPF (RFC 7208): a valid record that stays within the 10-DNS-lookup limit and ends in
-allor~all. - DKIM (RFC 6376): at least one selector publishing a healthy public key, ideally 2048-bit.
- Transport security: MTA-STS (RFC 8461) and TLS-RPT (RFC 8460), plus DNSSEC where present.
How to read and improve your score
The biggest single gain almost always comes from moving DMARC to enforcement, because a domain stuck at p=none still allows spoofing regardless of how tidy SPF and DKIM look. Next, fix any SPF record that exceeds 10 lookups, since that causes a permerror and silent failures, and rotate weak 1024-bit DKIM keys up to 2048-bit. Adding MTA-STS and TLS-RPT lifts the transport-security portion. Re-run the tool after each DNS change to confirm the score has risen. For a guided path to a perfect score, see our enforcement walkthrough or let DMARC Engine handle it as a done-for-you service.
Frequently asked questions
Does a high score guarantee inbox placement?
No. The score reflects your authentication and policy posture, which is a major factor receivers weigh, but inbox placement also depends on sender reputation, content and engagement. Strong authentication removes a common reason mail is filtered, but it is not the only signal.
Why does DMARC at p=none lower my score?
Because p=none only monitors: it tells receivers to take no action on messages that fail. Until you reach p=quarantine or p=reject your domain can still be spoofed, so the tool does not award the full DMARC weighting.
What pulls the score down most often?
The most common deductions are DMARC left at p=none, an SPF record that breaches the 10-DNS-lookup limit, and missing DKIM. Any one of these leaves a clear gap an attacker or a strict receiver can exploit.
Is the badge safe to embed publicly?
Yes. The badge only reports on records you have already published in public DNS, so it discloses nothing private. It is a useful trust signal on a marketing or status page.
How often should I re-check the score?
Re-check after any DNS change to your SPF, DKIM, DMARC or MTA-STS records, and periodically thereafter, since adding a new sending tool can quietly break SPF alignment or push you over the lookup limit.