Email Deliverability Check
Four DNS records decide whether a mail server trusts email sent from your domain. When they're wrong there's no bounce and no error — the message just quietly doesn't arrive. This reads all four and tells you which one to fix.
What gets checked
None of these live on your website. They're published in your domain's DNS, which is why a perfectly good site can sit alongside email that nobody receives.
The list of servers allowed to send email using your domain name. Without it, anyone can send mail that claims to be from you — and receivers have nothing to check yours against.
A signature on every message, so a receiver can prove it wasn't altered on the way and really came from you. It's the check that survives being forwarded, which SPF doesn't.
The instruction that turns the other two from published opinion into an enforced rule — and the only way to find out that somebody else is sending mail as you.
Where mail addressed to your domain gets delivered. Worth confirming even when you only send, because a missing one means anything sent back to you is going nowhere.
Getting these right is usually an afternoon with whoever runs your DNS. If the answer turns out to be that nobody does, that's what technical consulting is for.
Common questions
Because nothing tells you. There's no bounce and no error — a receiving server quietly decides your message looks unauthenticated and files it away. The customer says they never got the invoice, you assume they missed it, and you resend it into the same spam folder. It's the most expensive invisible problem a small business has, and it's diagnosable in about ten seconds from public records.
DKIM keys are published under a name your email provider picks — a "selector" — and DNS gives no way to list what exists under a domain. We try the dozen selectors the big providers use, so finding one is proof you have it, but not finding one only means it isn't on a name we could guess. That's why the result says "couldn't tell" rather than "missing". Your provider's admin settings will say whether DKIM is switched on.
SPF is allowed ten DNS lookups, counted across every record it refers to — not just the ones you wrote. Go over and the record becomes invalid, and most receivers treat it as though you had no SPF at all, even though it looks perfectly correct in your DNS. It usually happens quietly: you add a fourth sending service, and one of your providers' own records changes underneath you. Most free checkers count only your top-level includes and tell you you're fine. This one follows the tree.
No. Every answer here comes from public DNS records — the same ones any mail server in the world can read before it decides what to do with your message. No mailbox is touched, no message is sent, and nothing is stored. It's the same anonymous page-view counter as every other page on this site, and it never sees the domain you typed.
No, and nothing can. These four records are the part that's mechanical and checkable — they decide whether you're allowed to be believed. Whether you're actually wanted also depends on your sending history, how many people mark you as spam, and what else has been sent from your address in the past. Getting the records right removes the excuse; it doesn't remove the judgement.
Beyond the records
Records fixed is the part that's mechanical. Whether the message earns a reply is a different conversation, and a shorter one than you'd think.
Fixed price agreed before work starts. No hourly billing, no surprises.
