SPF
Published, one record only, under the ten-lookup limit, and how strictly it closes.
Free tool, no signup
Enter your domain. We read the records that decide whether your mail arrives, and tell you the specific thing to change. No score out of 100, no email address, nothing stored.
Six things, all of them public DNS records. Nothing here needs access to your mailbox.
Published, one record only, under the ten-lookup limit, and how strictly it closes.
Probes the selectors the common providers use, and decodes the key to report its real size.
Policy strength, whether reports are collected, and partial rollouts left switched on.
Whether mail sent to you has anywhere to go, and whether you have declared that it does not.
Whether your logo can show in supporting inboxes, and what is missing if not.
Your mail servers against public DNSBLs, with an honest answer when the lookup is refused.
A score invites you to optimise a number, and the number would be invented: a missing DMARC record and a short DKIM key are not comparable, so any weighting between them is made up. You get findings, each with its own fix.
DKIM selectors cannot be discovered from DNS. You can only look one up if you already know its name. We try seventeen that the common providers use, and if none answer we say we did not find one, not that you do not have one.
The blocklist check looks at the servers that receive your mail, because those are the ones DNS exposes. Those are often not the servers sending your campaigns. Treat it as a smoke test.
This page is a thin wrapper around an open-source package with no dependencies. Read all of it in ten minutes, or skip the page entirely and run the checks yourself. The hosted version and the command line cannot drift apart, because they are the same code.
The hard half is a sending programme that keeps its promises: one suppression list, something that actually reads the bounces, and outreach a person would not resent. That is the part we run for people.