Email setup audit

Check a domain's whole email setup: mail servers, SPF, DMARC and DKIM, graded, with a fix for every problem.

A domain, URL or email address; for an email address only the part after @ is used.

More options

A DKIM selector to try first, such as s1.

A few free checks a day without an account. Sign in to use your credits.

Check many at once

Bulk checks aren't unlocked yet

Bulk checks unlock after your first credit purchase or plan. Single checks work as usual.

Sign up free

What this check looks at

Email depends on four kinds of DNS records working together, and a mistake in any one of them can send your mail to spam or let someone else send mail in your name. This check reads all four straight from DNS and tells you, in plain words, what each one says and whether it holds up.

  • Mail servers (MX) say where email for your domain is delivered. We look up every mail server's address and flag names with no address, aliases, IP addresses where a name belongs and private addresses.

  • SPF lists the servers allowed to send mail as your domain. We follow every include, count the DNS lookups a receiver would make and check the result against the limit of 10.

  • DMARC tells receivers what to do with mail that fails SPF and DKIM, and where to send reports. If a subdomain has no record, we read the main domain's, as receivers do.

  • DKIM keys let receivers verify the signature on each message. We look for keys at your mail provider's selectors and at the common ones, and check their size and settings.

  • MTA-STS, TLS-RPT and BIMI are checked by running the MTA-STS checker inside this check, at no extra cost. Missing ones cost nothing; published but broken ones count, because senders then act on a promise you can't keep.

How the grade works

Every check starts at 100. Each problem takes off the number of points it is worth: a missing SPF or DMARC record costs 20, a DMARC policy that only monitors costs 10, a 1024-bit DKIM key costs 5. Information and passing results cost nothing. 90 and above is an A, 80 a B, 65 a C, 50 a D, and anything lower an F.

A clean setup with Google Workspace or Microsoft 365, SPF ending in ~all, a DMARC policy of reject and a working DKIM key scores 100. The same setup with p=none scores 87, because forged mail still reaches inboxes. A domain with mail servers but no SPF, DMARC or DKIM scores 55.

Softer SPF endings are judged in context: ~all is a warning when DMARC is missing or only monitoring, and just a note when DMARC enforces a policy, because then DMARC does the stopping.

Domains that don't send email

Many domains never send or receive mail: parked names, old brands, redirect domains. They are favourite targets for phishing because nobody watches them. If your domain has a null MX record and no senders, we check it is locked properly: SPF v=spf1 -all and DMARC p=reject. Then we don't ask for DKIM or complain about SPF, since there is nothing to sign.

SPF lookups, explained

Receivers allow an SPF record at most 10 DNS lookups. Every include, a, mx, ptr, exists and redirect costs one, and so do the includes inside the records you include. Google Workspace alone uses four. Go over the limit and receivers stop with an error, so SPF fails for all your mail, even mail from servers you listed. The result shows the count, a meter, and the whole include tree, so you can see which service costs the most. More than two lookups that find nothing also cause an error, and we count those too.

What we don't do

We read public DNS records and fetch only the MTA-STS policy file, the BIMI logo and its certificate. We never connect to your mail servers, send test messages or look at mail. Reverse DNS for mail servers is left to the dedicated tools, so this check stays quick: most results arrive within a few seconds, section by section as each answer comes in.

Fixing what you find

Every problem links to a step-by-step guide with instructions for the common DNS hosts and mail providers. The SPF and DMARC sections link straight to the SPF builder and the DMARC builder with your current record filled in, so you can change it and check the result before you publish. For one DKIM key in detail, use the DKIM record validator.

The SPF checker and DMARC checker pages run this same check with that record shown first, if that's the part you care about today.

Questions

Can I check an email address instead of a domain?
Yes. Paste the address and we keep only the part after the @. The part before it never leaves your browser in our records, logs or usage history.
Why didn't you find my DKIM key?
DKIM keys live under a selector name that only your mail provider knows. We try your provider's selectors and about 40 common ones. If yours is different, enter it under More options; it appears in the s= tag of the DKIM-Signature header of any message you send.
My grade is B because of ~all. Should I change it?
Only once DMARC is enforcing or your reports show all your real mail passes. With a DMARC policy of quarantine or reject, ~all costs nothing in the grade, because DMARC already stops forged mail.
Why is there no grade on some results?
When the SPF or DMARC lookup fails, we don't guess. The result is marked partial, says which lookup failed, and leaves the grade out until a check can read both records.
What does a check cost?
In the browser you get a few free checks a day without an account. Through the API or MCP a check costs 2 credits, and a cached answer costs the same. Checks that fail upstream are free.