Email Configuration Checker

Validate your MX, SPF, DKIM and DMARC records for errors.

Email authentication lives in a handful of DNS records, and the rules around them are unforgiving: two SPF records instead of one breaks SPF entirely, an SPF that needs more than ten DNS lookups silently fails, an MX pointing at a host that no longer resolves drops your mail. None of this produces an obvious error — your email just quietly starts going to spam or bouncing. An email configuration checker validates these records against the rules and tells you exactly what is wrong.

What it checks
  • MX records present, and every mail host actually resolves (no dangling MX)
  • Exactly one SPF record (multiple is an error that breaks SPF)
  • SPF within the 10 DNS-lookup limit, with an "all" mechanism
  • A single valid DMARC record with a policy
  • DKIM signing key published, plus optional MTA-STS and TLS-RPT

Why it matters

These are correctness rules, not preferences — break one and authentication fails outright, no matter how good the rest of your setup is. The failures are invisible until deliverability drops, and they often appear right after a routine DNS change or adding a new sending tool. Validating the records continuously means a broken change is caught in hours, not after weeks of mail quietly landing in spam.

How BrandSentryPro does it

Add your domain and BrandSentryPro validates your MX, SPF (including a recursive count of its DNS lookups), DMARC, DKIM and modern TLS records, flags every error and weakness with how to fix it, and re-checks on a schedule — alerting you the moment a record breaks or changes.

Frequently asked questions

Why does having two SPF records break email?
The SPF specification (RFC 7208) allows only one SPF record per domain. When a receiver finds two, the result is a permanent error (permerror) and SPF is treated as failing — so a second record, often added by accident when onboarding a new sender, silently breaks authentication.
What is the SPF 10-lookup limit?
An SPF record may trigger at most 10 DNS lookups (from include, a, mx, ptr, exists and redirect mechanisms). Exceeding it causes a permerror and SPF fails. Stacking up several "include:" entries from different mail services is the usual cause; flattening or trimming includes fixes it.
What is a dangling MX record?
A dangling MX is an MX record pointing at a hostname that no longer resolves to an IP. Mail to the domain can fail or be delayed, and a dangling host can sometimes be claimed by an attacker. A checker flags MX hosts that do not resolve so you can fix or remove them.

Related checkers

All in one place

Run this check automatically

Add a monitor and BrandSentryPro keeps every check running for you — with alerts the moment something needs attention.

Get started