Skip to content

Free tool

Email health check

Check MX, SPF, DKIM, and DMARC, the four records that decide whether a domain's email works, plus the optional MTA-STS and BIMI. One report, one verdict. Free, no signup.

Tryshipmail.togmail.com

Email Domain Checker is a free Chrome extension. Check any site’s domain from your toolbar

Need to inspect just incoming mail routing? View mail server hostnames and priorities with the free MX record check

What this checks

Four DNS records decide whether a domain can receive email and whether the email it sends is trusted. MX records route incoming mail. SPF lists the servers allowed to send for the domain. DKIM publishes the keys that sign outgoing mail. DMARC tells receivers what to do when a message fails those checks.

It also checks two optional records. MTA-STS makes senders deliver mail to you over TLS, and BIMI shows your logo in inboxes that support it. A domain without them can still pass, and a published record that is broken only lowers the verdict to a warning.

This report runs every lookup at once and rolls them into one verdict. Each section links to the full checker for that record when you need the detail.

How to read the verdict

A problem on MX, SPF, or DMARC is worth fixing this week: missing MX means bounced mail, a broken SPF record hurts every message you send, and no DMARC policy leaves the domain open to spoofing.

DNS cannot list a domain's DKIM selectors, so this report tries common selector names. When none of them answers, DKIM shows as not checked: it does not count as a problem, and the score counts only the checks that ran. Find the s= value in a message you sent and run the DKIM checker with it.

FAQ

Questions?

Talk to a human →
Is this the same as an email deliverability test?

It covers the DNS half. The email deliverability test covers the other half: send it one real message and it checks what DNS cannot show, such as the server your mail leaves from and the DKIM signature your provider adds. Reputation and content still matter, but broken MX, SPF, DKIM, or DMARC records are the most common and most fixable causes of mail landing in spam.

Why does DKIM show as not checked?

The combined report can only try common selector names like google or selector1. Providers that use dated or account-specific selectors, such as Google's own domains, Amazon SES and Postmark, are not found this way, so the report leaves DKIM unchecked instead of calling it a problem. Run the DKIM checker with your exact selector for a definitive answer.

What should a healthy domain look like?

MX records pointing at one provider, a single SPF record ending in ~all or -all within the 10 lookup limit, at least one strong DKIM key, and a DMARC policy of quarantine or reject with a rua reporting address.

How often should I run this?

After any DNS change, after adding or removing an email sending service, and once a quarter as a habit. Records break silently, usually during unrelated DNS edits.

Email, newsletters and booking pages on your own domain, in one plan.

Get started for free