Enter a domain and we'll read the records that decide whether your mail is trusted — SPF, DMARC, DKIM and MX — and tell you plainly what's wrong and what to do about it. Nothing to send, nothing to set up.
An SPF record is allowed to trigger at most ten DNS lookups while it's being checked. Go over, and the result isn't “mostly fine” — it's a hard error, and receiving servers treat that as a failure. Your record can look perfectly sensible and still fail everywhere.
It creeps up on you. Every tool you add — a CRM, a helpdesk, an invoicing app — asks you to add one more include:, and each one quietly spends part of your budget. Nobody counts, so nobody notices until mail starts bouncing. That's the number we show you first.
One thing worth knowing if you use subdomains: SPF does not inherit. A record on example.com does nothing for mail.example.com — a lookup there returns nothing at all, which is not the same as passing. DMARC, confusingly, works the other way round: subdomains do inherit the parent policy unless you set sp=.
This reads public DNS. It doesn't send a message, so it can't see your sending reputation, your content, or whether a particular provider is filtering you. A domain can score well here and still land in spam. Treat a clean result as “nothing in the setup is working against you”, not as a delivery guarantee.
And if your mail path itself goes down, configuration won't tell you — for that you want something watching it. Our deliverability notes cover the monitoring side, or start with the other free tools.
This page checks once, right now. A free account checks on a schedule and emails you before something expires or goes down — 25 monitors, no card needed.
We'll watch it freeAlready have an account? Go to your dashboard