Email Checker
Check a domain's whole email setup in one go: MX, SPF, DMARC, DKIM, MTA-STS, TLS-RPT and BIMI, with a score and a list of what to fix.
What this tool checks
Enter a domain (or a full email address, from which we take the domain) and optionally a DKIM selector. The checker reads every DNS record that matters for email and evaluates it against the relevant standard:
| Check | What it looks at | Standard |
|---|---|---|
| MX | Where mail for the domain is delivered; null MX detection | RFC 5321, RFC 7505 |
| SPF | Which servers may send for the domain; DNS lookup count | RFC 7208 |
| DMARC | Policy for mail that fails authentication; reporting | RFC 7489 |
| DKIM | The public key for the selector you entered | RFC 6376 |
| MTA-STS | Whether senders must use verified TLS to reach your MX | RFC 8461 |
| TLS-RPT | Where reports about TLS delivery problems are sent | RFC 8460 |
| BIMI | Brand logo shown by supporting mailboxes | BIMI specification (industry draft) |
All DNS queries are sent from our server through a public resolver over DNS over HTTPS. For MTA-STS we also fetch the policy file from https://mta-sts.<domain>/.well-known/mta-sts.txt.
How to read the result
Each section lists findings, marked as OK, info, warning or error, each with a short explanation. At the top, a score from 0 to 100 summarises them. Errors (for example, no SPF record or two of them) weigh more than warnings (for example, a DMARC policy of none).
MX
Lists the mail servers in preference order. An error means there are none, or a target does not resolve. A null MX (0 .) is reported as intentional: the domain does not receive mail.
SPF
Shows the record, each mechanism with its qualifier, and the number of DNS lookups it needs. RFC 7208 allows at most 10 lookups (include, a, mx, ptr, exists and redirect, counted through every nested include) and at most 2 void lookups that return nothing. Over the limit, receivers return permerror and SPF fails. More in the SPF checker notes.
DMARC
Shows the policy (none, quarantine or reject), the reporting addresses and other tags. p=none is fine while you collect reports, but it does not protect against spoofing. More in the DMARC checker notes.
DKIM
Without a selector, this section stays informational, because DKIM keys can only be found by name. With a selector, it shows the key type and size. Keys shorter than 1024 bits are considered insecure; 2048 bits is the common recommendation. More in the DKIM checker notes.
MTA-STS
Checks the _mta-sts TXT record and the policy file: its mode (enforce, testing or none), the MX patterns it covers and its max_age. A warning appears if the policy does not cover all your MX hosts.
TLS-RPT
Checks the _smtp._tls TXT record and its rua reporting addresses. TLS-RPT reports tell you when other servers fail to deliver to you securely; they are especially useful with MTA-STS.
BIMI
Checks default._bimi for a logo URL (l=) and an optional certificate URL (a=). BIMI only works when DMARC is at enforcement (quarantine or reject), and several large mailbox providers display the logo only when a mark certificate is provided.
Requirements of large mailbox providers
Since 2024, Google and Yahoo require senders of bulk mail to their users to authenticate with SPF and DKIM and to publish a DMARC policy, among other rules such as easy unsubscribing. Other large providers have announced similar requirements. Even if you send little mail, having all three in place is the baseline for reliable delivery.
Common problems and fixes
- No SPF, or two SPF records. Publish exactly one TXT record starting with
v=spf1on the domain. - SPF over 10 lookups. Remove includes for services you no longer use, replace includes with
ip4/ip6ranges where the provider documents stable addresses, or move some senders to a subdomain. - DMARC at
p=nonefor months. Read the aggregate reports, make sure every legitimate sender passes SPF or DKIM with alignment, then move toquarantineand finallyreject. - DKIM selector not found. The selector is wrong, or DKIM is not enabled at your provider. Check the
s=tag in a real message header. - MTA-STS policy file unreachable. The
mta-stssubdomain needs a valid HTTPS certificate and must serve the file directly, without redirects. - Missing reverse DNS for sending IPs. Not part of this check, but often the cause of rejections. Use the reverse DNS tool.
Related guides
Frequently asked questions
Can you check if my domain or IP is on a blacklist?
Not at the moment. The major blocklists restrict commercial use of their query services, so we have chosen not to offer that check rather than use them outside their terms. Most blocklist operators offer a free lookup page on their own website.
Can you send a test email or test my SMTP server?
No. The site runs on an edge platform that cannot open outgoing connections on SMTP port 25, so every check here is based on DNS (plus the MTA-STS policy file, fetched over HTTPS). To test delivery, send a message to an external mailbox and inspect the headers.
Where do I find my DKIM selector?
Open a message sent from your domain, view the original or the full headers, and find the DKIM-Signature header. The value after s= is the selector and the value after d= is the signing domain. Enter that selector in the DKIM field.
Is the score an official rating?
No. It is our own summary of the findings, weighted towards the things that most affect deliverability and spoofing protection. Use it to prioritise, and read the individual findings for the details.
Does a perfect score guarantee my mail reaches the inbox?
No. Authentication is a requirement, not a guarantee. Mailbox providers also look at sending reputation, content, complaint rates and how recipients interact with your mail.