Is your email set up right?
Check SPF, DKIM, DMARC and MX in one go. Get a score, see whether you meet Gmail’s, Yahoo’s and Microsoft’s rules, and a plain-English fix for every problem.
- Live DNS lookup
- Results in seconds
- No sign-up
- Free
Gmail, Yahoo & Microsoft basics
- A valid SPF record
- A DKIM key published
- A DMARC record (p=none or stricter)
Mail servers (MX)
1 server · Microsoft 365
SPF
10 of 10 lookups · ~all
DKIM
11 keys: google, selector1, k1, k2, k3, s1, s2, smtpapi, zendesk1, zendesk2, cm
DMARC
p=quarantine
Fix these first
- 1
SPF 10 of 10 DNS lookups used
Close to the limit. Adding one or two more services will make SPF fail; a provider changing its own include can push it over without you changing anything.
- 2
DKIM selector1, k1, smtpapi, cm: 1024-bit key
1024-bit keys still work, but 2048 bits is the current recommendation. Rotate to a 2048-bit key when you can.
Every check
Mail servers (MX) Good 1 server · Microsoft 365 Details
-
OK:One mail server
Email is handled by Microsoft 365.
SPF Needs attention 10 of 10 lookups · ~all Details
-
Warning:10 of 10 DNS lookups used
Close to the limit. Adding one or two more services will make SPF fail; a provider changing its own include can push it over without you changing anything.
-
OK:Ends with ~all (soft fail)
Servers not listed get a soft fail. With DMARC in place this is the usual choice; -all is stricter.
-
OK:One SPF record published
DKIM Needs attention 11 keys: google, selector1, k1, k2, k3, s1, s2, smtpapi, zendesk1, zendesk2, cm Details
-
Warning:selector1, k1, smtpapi, cm: 1024-bit key
1024-bit keys still work, but 2048 bits is the current recommendation. Rotate to a 2048-bit key when you can.
-
OK:google, k2, k3, s1, s2, zendesk1, zendesk2: 2048-bit RSA key
DMARC Good p=quarantine Details
-
Note:Failure reports requested (ruf=)
Few providers send them any more (Gmail doesn’t), for privacy reasons. Harmless, but don’t rely on them.
-
OK:Policy is quarantine
Mail that fails DMARC goes to spam. p=reject, the strictest setting, blocks it outright.
-
OK:Reports go to dmarc@github.com
-
OK:One valid DMARC record published
Advertisement
The four records behind email delivery
- MX tells other servers where to deliver mail for your domain. Wrong or missing MX records mean mail to you bounces.
- SPF lists the servers allowed to send as your domain.
- DKIM publishes the key your email service signs messages with, proving they weren’t forged or changed.
- DMARC tells receivers what to do when a message fails SPF and DKIM, and sends you reports. It’s what actually stops spoofing.
Since 2024, Gmail and Yahoo require all three of SPF, DKIM and DMARC from bulk senders, and Microsoft followed in 2025 for Outlook.com. Mail that doesn’t meet the rules is increasingly rejected rather than just sent to spam. See the full requirements and how the three records fit together.
Fix in this order
- Make sure MX points at your real email provider.
- Publish one SPF record that includes every service that sends for you.
- Turn on DKIM signing with your own domain in each of those services.
- Publish DMARC at
p=nonewith a report address, read the reports, then tighten it.
Frequently asked questions
What does the health check test?
The four DNS records that decide whether mail from your domain is trusted and whether mail to it arrives: MX (where your mail goes), SPF (which servers may send as you), DKIM (the key that signs your mail) and DMARC (what receivers do when those checks fail). Each links to its full checker.
How is the score worked out?
DMARC counts for 35 points, SPF and DKIM 25 each and MX 15. A section with no problems gets full marks, one with warnings half, one with errors none. The letter grade follows the score: A from 90, B from 80, C from 65, D from 50. It’s a guide to priorities, not a deliverability prediction: content, sending volume and reputation matter too.
It says no DKIM key was found, but I set DKIM up.
DKIM keys can’t be listed, so we try about 40 selectors common services use. Yours may use another one. Find the s= value in a sent message’s DKIM-Signature header and check it in the DKIM checker.
Does a good score mean my mail will reach the inbox?
It means the authentication side is in order, which Gmail, Yahoo and Microsoft now require. Inbox placement also depends on your sending reputation, complaint rate, list quality and content, which DNS can’t show.
Do you store the domains I check?
No. We run the lookups, show the results and keep them in memory for about a minute so a repeat check is fast. Like any website, our server’s access logs record the page address, which includes the domain; they aren’t used for anything else.
Did this tool do what you needed?
Related tools
All toolsSPF Record Checker
Validate an SPF record, follow every include and count DNS lookups against the limit of 10.
DMARC Record Checker
Read a domain’s DMARC policy in plain words and see what to change before tightening it.
DKIM Record Checker
Find DKIM keys under common selectors, or check your own, with key size and problems.
MX Lookup
See a domain’s mail servers, who hosts its email, and problems that stop mail arriving.