Email deliverability check

Four records decide whether your mail reaches the inbox, and they only work together. This runs all of them at once and tells you which one to fix first, because fixing them in the wrong order can make deliverability worse rather than better.

Try:

Free, no signup, no daily limit. We do not store what you check here.

The order matters more than the checklist

Publishing DMARC at reject before SPF and DKIM are correct does not protect your domain, it blocks your own mail - and the failure is silent, because rejected messages do not bounce back to you in any obvious way. The safe order is always: get MX and SPF right, add DKIM, publish DMARC at p=none with reporting, read the reports for two weeks, then tighten.

Why p=none is not the finish line

A DMARC record at p=none tells receivers to report what they see and deliver everything regardless. It is the correct place to start and the wrong place to stay: it gives you visibility and no protection. Most domains that publish DMARC never move past it, which is why an attacker can still send mail as them.

Questions

I have all four and mail still lands in spam. Why?

Authentication proves the mail is genuinely from you. It does not make it wanted. Content, sending reputation, list quality and complaint rates decide the rest, and a new domain has no reputation yet whatever its DNS says.

Do I need all four if I only send from one service?

Yes. Each answers a different question, and DMARC only means anything when at least one of SPF or DKIM aligns with the domain in the From header.

Related tools

When you need more than a free tool

This page answers what can be determined offline and from public DNS. The API adds live carrier and mailbox verification, a calibrated confidence score, and the full evidence trail behind every verdict.

Credits never expire. Inconclusive verdicts are never billed. Cancel in one call. See pricing or read the docs.