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.
Results for
gmail.com
Needs attention
2 of 3 required checks pass. DKIM was not checked.
MX: receiving mail
OKMX records tell other servers where to deliver mail for your domain. Without them, mail sent to you bounces.
What works
Mail is handled by Google Workspace
Mail for gmail.com is routed through Google Workspace.
OK
SPF: allowed senders
OKSPF lists the servers allowed to send mail as your domain. Receivers use it to spot forged mail, and a broken record sends your real mail to spam.
What works
SPF record looks good
1 of 10 DNS lookups are used.
OK
DKIM: message signing
Not checkedDKIM publishes a public key that receivers use to check the signature on your mail. A valid signature proves nobody changed the message on the way.
How to check it
No common DKIM selectors found
Your provider may use a custom selector. Open a message you sent, find the s= value in its DKIM-Signature header, and run the DKIM checker with that selector.
Not checked
DMARC: spoofing policy
WarningDMARC tells receivers what to do with mail that fails SPF and DKIM: deliver it, send it to spam, or reject it. It also sends you reports on who sends mail as your domain.
How to fix
Policy is p=none (monitoring only)
Spoofed mail is still delivered under this policy. Move to quarantine or reject once the reports look clean.
Warning
Optional
These records are not required. A domain without them can still pass, and a broken one only lowers the verdict to a warning.
MTA-STS: TLS for incoming mail
OKMTA-STS makes other servers use an encrypted connection when they deliver mail to you.
What works
Mode is enforce
Senders that support MTA-STS only deliver over TLS to the listed MX hosts.
OK
The policy covers every MX host
All 5 MX hosts match an mx line in the policy.
OK
TLS-RPT is set up
TLS failure reports go to mailto:sts-reports@google.com.
OK
BIMI: logo in the inbox
WarningBIMI shows your logo next to your mail in inboxes that support it, such as Gmail and Apple Mail.
How to fix
DMARC policy is p=none
BIMI needs p=quarantine or p=reject. Move the DMARC policy up before a logo can show.
Problem
No BIMI record
Inboxes that support BIMI show no logo for this domain. Publish a TXT record at default._bimi.gmail.com that links your SVG logo.
Warning
Fix the setup with Shipmail
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.
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