Email DNS Checker (SPF, DKIM, DMARC)

Audit a domain's email DNS in one report: MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT and BIMI — with pass/warn/fail badges.

868 views

Data: Google Public DNS (DoH) — queried from your browser.

Will Your Email Land in Inboxes?

Enter a domain and get its complete email-authentication report in one screen: MX (who receives mail), SPF (which servers may send), DKIM (cryptographic signing — common selectors are tried automatically, or enter your own), DMARC (the policy that ties it together), plus the modern extras MTA-STS, TLS-RPT and BIMI. Each check gets a pass/warn/fail badge and the raw record for inspection.

SPF and DMARC are parsed, not just displayed: the tool flags a missing record, a DMARC policy of p=none (monitoring only — no protection), multiple SPF records (a standards violation that breaks validation) and a missing all mechanism. Queries run from your browser via Google's DNS-over-HTTPS; nothing touches this site's server.

Frequently Asked Questions

Which DKIM selectors are tried automatically?

The common ones: default, google, selector1, selector2, k1, s1, mail, dkim. Providers publish under known selectors (Google Workspace uses "google", Microsoft 365 uses selector1/selector2). If yours is custom, type it into the selector field.

My DMARC says p=none — is that bad?

p=none only monitors: receivers report failures but deliver spoofed mail anyway. It is the right first step while collecting reports, but the destination should be p=quarantine or p=reject once your legitimate sources are aligned.

Why is having two SPF records an error?

The standard requires exactly one SPF record; validators treat multiple records as a permanent error, which can send your mail to spam. Merge them into a single v=spf1 string.

Does this check email content or blacklists?

No — it audits DNS configuration only. Blacklist status and content-based spam scoring are separate concerns; correct DNS is the foundation that everything else builds on.

Similar Tools