One combined score for MX, SPF, DKIM, DMARC and blacklist status - the DNS side of whether your mail actually lands in the inbox.
This score checks five DNS-visible signals that mailbox providers use (directly or indirectly) to decide whether to trust mail from your domain: whether it can receive mail at all (MX), whether it declares which servers may send for it (SPF), whether outgoing mail is cryptographically signed (DKIM), whether there's a policy for what to do with mail that fails those checks (DMARC), and whether its sending IP has a spam-listing history (blacklist/RBL). It is a DNS-configuration signal, not a guarantee of inbox placement - content, sending reputation, and volume all matter too.
Want the full raw records instead of a score? Run the detailed email DNS check.
Run the Email DNS CheckMailbox providers weigh several independent DNS signals when deciding whether to trust mail from a domain: can it receive mail at all (MX), does it declare which servers may send for it (SPF), is outgoing mail cryptographically signed (DKIM), is there an enforceable policy for mail that fails those checks (DMARC), and does the sending IP have a clean reputation (blacklist status). This score checks all five in one pass and combines them into a single number so you can see the overall picture instead of five separate pages.
The score is a DNS-configuration signal, not a guarantee of inbox placement. Content, sending volume, engagement, and list hygiene all affect deliverability too, and none of those are visible from DNS. A perfect score means your DNS-side setup is not the reason mail is misdelivered; it does not rule out every other cause.
If you need related checks, try Check Blacklist/RBL check online and DKIM check DNS lookup.
DNS-based scores can shift if a resolver query times out (shown as an "unknown" result rather than counted against you) or if an upstream provider changed something on their end, such as a DKIM key rotation. Re-run the check; a single transient resolver hiccup is common and not usually a real regression.
A domain that publishes a "null MX" (RFC 7505) is explicitly declaring it does not accept mail at all, which is a deliberate and valid configuration, for example on a domain used only to send transactional mail. This checker recognizes that pattern and scores it accordingly rather than treating it as a broken MX setup.
A fail means the check ran successfully and found a real problem (no SPF record, no DMARC policy). An unknown means the DNS query itself could not get a reliable answer, usually a resolver timeout, and should be treated as inconclusive rather than as evidence of a broken record.
Yes. Each of the five checks is independent. Use the DKIM checker, the SPF & DMARC generator, or the blacklist checker to fix a specific weak area, then re-run the combined score to confirm.
Partially. A DMARC record with p=none is scored as a warning rather than a full pass, since it provides reporting visibility but does not actually enforce anything against spoofed mail. Moving to quarantine or reject earns full marks.
Blacklists track the reputation of the IP that actually sends mail, which for most domains is the mail server behind the MX record, not the web server. The tool resolves the MX target specifically for this reason.