Email Deliverability check
Is your email actually arriving?
Almost every business we meet with an email problem thinks it has a content problem. They have rewritten the subject line six times and nothing moves. Put your domain in below and this page reads your live DNS — the three records mailbox providers actually check — and tells you what is missing and what order to fix it in.
Your domain only — the records are public, we read them straight from DNS in your browser, and nothing is stored or sent to us. An email address works too; we will take the part after the @.
The written version.
Send it over and we will read the whole picture — every source sending as your domain, whether your signatures actually align, and the order to fix it in without sending your own mail to junk. A person writes it.
What the check found travels with it, so the reply starts from your records rather than asking for them.
Why this happens at all.
The Ledger entry behind this tool walks through a real client whose list opened at half a percent in Gmail and twenty-four percent everywhere else, on the same send, on the same morning. It explains alignment, which is the part almost everyone misses, and why the records usually go missing during a website move.
Fix it in this order
The order matters more than the speed.
Tightening enforcement before the signatures exist will send your own legitimate mail to junk, including the mail your team types by hand. So this is the sequence, and it is the same one we run for clients.
- Set up a dedicated sending domain in your email platform.
It generates the records; you add them to your DNS exactly as given, then hit verify. This is the one that moves the open rate, because it is what makes your signature align with the address your customer actually sees.
- Add DKIM for your mailbox provider too.
Google Workspace or Microsoft 365, so the mail your team types by hand is signed as well, not just the marketing sends.
- Turn DMARC reporting on, still set to take no action.
p=nonewith arua=address. Nothing changes about how your mail is treated; you are only collecting evidence. Raw reports are unreadable XML, so point them at a free digest service that emails you a weekly summary. - Read the reports for two or three weeks.
They will show every source sending as your domain, including the things nobody remembered was still switched on.
- Then tighten, slowly.
Move to quarantine on a percentage of mail, raise it over a few weeks, and only then consider outright rejection. There is no prize for arriving early.
Being straight with you
What this check cannot see.
- It reads DNS, not your inbox placement. These three records are the half of deliverability that is publicly checkable. They are not the whole of it, and a clean result here does not guarantee the inbox.
- DKIM is a guess unless we find it. A DKIM record lives at a selector name your provider chose, and there is no way to list them. We probe the selectors the common platforms use. Not finding one does not prove you have none — it means it is not at a name we know, which is worth checking by hand.
- Alignment is the part that actually bites, and it needs a real message header to confirm. Your platform can sign every send validly and still fail, because the signature passes for the platform rather than for you. That is the single most common cause we see, and this page cannot see it.
- Reputation is slower than records. If your domain has been sending badly for months, fixing the DNS starts the recovery; it does not finish it. Expect a few clean sends before opinions revise.
Rather we just looked at yours?
Deliverability is one line item in the Growth Assessment: two weeks, fixed price, three prioritized moves with what each returns.