Built for agencies and B2B sales teams.

Start free →

Free Email DNS Checker — MX, SPF, DKIM & DMARC

Check your domain's MX, SPF and DMARC records, plus its DKIM public key when you provide a selector. Review published DNS configuration, understand reported issues and see what to check next.

No signupCombined resultsActionable fixes
Email DNS CheckerFreeExample result
Your sending or business email domain
Without a selector, DKIM is not checked
EXAMPLE
92/100 (example)

Example report, not your domain

RecordStatusDetail
SPFPASSExample: 1 record, 3 of 10 lookups
DKIMPASSExample: selector google, public key published
DMARCWARNINGExample: p=none, monitoring only
MXPASSExample: 1 record found
This is sample data, including the 92/100 score. Run a check to see results for your domain.
Example priority: DMARC p=none requests no enforcement. Review it once your senders align
How it works

How to Check Your Email DNS Records

The checker reviews published DNS information used for email authentication and routing: SPF, DMARC and MX, plus DKIM when a selector is supplied or another supported discovery method returns a result.

  1. 01

    Enter the domain

    Use the domain you want to check, such as example.com.

  2. 02

    Review each record separately

    One successful result does not mean every other authentication or routing setting is correct.

  3. 03

    Fix, wait, recheck

    Save changes at your authoritative DNS provider, allow for DNS caching, and check again.

What each record tells you

SPF, DKIM, DMARC and MX: four different responsibilities

SPF: sender authorization

Defines which sending sources are authorized for the relevant envelope-sender or HELO identity. A published record does not prove a particular email passed SPF.

DKIM: published signing key

Keys live at a selector-specific name, for example selector1._domainkey.example.com. A published key does not prove a message passed signature verification, and a failed selector lookup does not prove DKIM is absent for the domain. Find your selector in provider settings or the s= value of a DKIM-Signature header.

DMARC: alignment and policy

Connects successful SPF or DKIM authentication to the visible From domain through alignment. A DNS record shows published policy and settings, not whether a specific message passed DMARC.

MX: inbound mail routing

Identifies the servers that receive email. Under RFC 5321 SMTP may fall back to an address record when no MX exists, and RFC 7505 Null MX explicitly says a domain accepts no mail. A missing MX needs context.

Incomplete DNS results

A timeout, resolver failure or restricted report is not a confirmed missing record. The result shows UNKNOWN, INCOMPLETE or NOT CHECKED instead of a pass or a zero.

Email DNS readiness score

When the checker supplies one, it summarizes the available checks. It is not an inbox-placement score, proof of message authentication or a guarantee of delivery.

Reading results

Pre-send checklist

Each record has a healthy signal and a warning sign. A timeout is not the same as a failure.

RecordHealthy signalWarning sign
SPFOne v=spf1 record, under 10 lookupsMultiple SPF records, or too many lookups
DKIMA public key published at the selector you suppliedNo key at that selector, or an empty p= tag
DMARCA policy with a working reporting addressNo record, or p=none treated as enforcement or as active reporting
MXThe routes you intend to use, or a Null MX if the domain accepts no mailStale routes after a migration
DNS lookupsClear answersA timeout, which should be rechecked rather than read as failure
Common issues

Common problems and how to fix them

Duplicate SPF policies

Two v=spf1 records at one name can cause a permanent error. Merge them into one.

Wrong or unknown DKIM selector

DNS cannot list selectors, so you must supply the right one.

Monitoring-only DMARC

p=none is valid, but it requests no enforcement and needs a valid rua address for reports.

Stale MX routes

After a mailbox migration, remove routes to the old provider.

Provider settings are authoritative

Authentication records confirm published configuration but do not guarantee inbox placement. Provider admin settings are authoritative over DNS results, and DNS changes may not appear everywhere at once because of caching. Use the dedicated SPF, DKIM, DMARC and MX tools when a result needs detailed investigation.

Comparison

Email DNS Checker vs Domain Health Checker

Email DNS Checker

Focuses on SPF, DKIM, DMARC and MX.

Domain Health Checker

Covers a broader set of supported domain diagnostics.

Email Header Analyzer

The next step for inspecting authentication and routing evidence from an actual email.

FAQ

Email DNS Checker FAQ

Still unsure? Read the DevBoxy blog or contact the team.

What is an email DNS checker?

It looks up the DNS records used for email authentication and routing, usually SPF, DKIM, DMARC and MX, and shows what is published, weak or missing.

Which DNS records matter most for email?

SPF lists authorized sending sources, DKIM publishes a signing key, DMARC sets policy and alignment with the visible From domain, and MX routes inbound mail.

Can SPF and DKIM pass while DMARC fails?

Yes. DMARC needs at least one of them to align with the visible From domain, so a pass without alignment can still fail DMARC.

Why do I need to enter a DKIM selector?

DNS cannot list every selector under a domain. The selector tells the checker exactly where to look for the public key, at selector._domainkey.yourdomain.com. Without one, DKIM is not checked.

Does a published DKIM key prove my email is signed?

No. It shows a public key is published. It does not prove that an actual message passed signature verification, and a failed selector lookup does not prove DKIM is absent for the domain.

Is p=none a valid DMARC policy?

Yes, but it requests no enforcement. Aggregate reports also need a valid reporting address, so p=none alone does not mean reporting is active.

How many SPF records should a domain have?

One. Multiple SPF records at the same name can cause a permanent error.

What is the SPF lookup limit?

SPF allows 10 DNS-querying terms. Includes and other mechanisms count toward the limit, including nested ones.

Is a missing MX record always a problem?

Not always. Under RFC 5321, SMTP may fall back to an address record when no MX exists, and RFC 7505 Null MX explicitly says a domain accepts no mail. A missing MX needs context.

What does an unknown or incomplete result mean?

A timeout, resolver failure or restricted report is not a confirmed missing record. Run the check again before changing DNS.

Does healthy DNS or a good score guarantee inbox placement?

No. The score summarizes available checks only. Reputation, complaint rates, content and provider policies also matter.

How is this different from the Domain Health Checker?

The Email DNS Checker focuses on SPF, DKIM, DMARC and MX. The Domain Health Checker covers a broader set of supported domain diagnostics.

When should I run the check again?

After DNS changes have propagated, which depends on your TTLs and caching, and after any provider or infrastructure change.

Pair DNS checks with list verification.

Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.