Email Health Check

One domain, one click: MX, SPF, DMARC, DKIM, reverse DNS and blacklist checks together.

Runs MX, SPF, DMARC, DKIM, reverse-DNS and blacklist checks in one pass. Nothing is stored.

Frequently asked questions

What does the Email Health Check test?

In one pass it checks your domain MX records, SPF record, DMARC policy, DKIM keys on common selectors, the reverse DNS (PTR) of your primary mail server, and whether that server appears on major blacklists.

Why do I need SPF, DKIM and DMARC together?

SPF says which servers may send for your domain, DKIM cryptographically signs each message, and DMARC ties them to your visible From address and tells receivers what to do on failure. All three working together is what actually stops spoofing and protects deliverability.

Why does DKIM show as not found when I have it set up?

DKIM keys live at a selector you choose, and there is no way to list every selector a domain uses. This tool probes the most common selectors (google, default, selector1, and others); if your provider uses a custom selector, look it up directly with the DKIM Checker.

What is a good DMARC policy?

Start with p=none to monitor without affecting delivery, then move to p=quarantine and finally p=reject once you confirm your legitimate mail passes. A policy of reject gives the strongest protection against spoofing.

Why does the blacklist check matter?

If your sending IP is listed on a DNS blacklist (RBL), many providers will reject or spam-folder your mail. The check looks up your primary mail server IP on several well-known blacklists so you can request delisting if needed.

Is reverse DNS really required for email?

For reliable delivery, yes. Many receivers reject or penalise mail from an IP whose PTR record is missing or does not match the sending host name. Forward-confirmed reverse DNS (FCrDNS) is considered a baseline requirement.

Do you store the domains I check?

No. Every lookup runs live and the results are returned straight to your browser. Nothing you enter is written to a database or a file.