Find out what your domain tells the world about who may send its mail.
One scan reads your DMARC, SPF, DKIM, MX, DNSSEC, MTA-STS, TLS-RPT, and BIMI records, scores them out of 100, and lists what to fix first. It takes a few seconds and asks for nothing but the domain.
Eight records, one verdict, no adjectives.
Every result comes from a live DNS lookup made when you press the button. Nothing is cached from last week and nothing is guessed.
- DMARC policy
- Whether a record exists, whether it parses, and which policy receivers will actually apply: none, quarantine, or reject. The DMARC checker goes through it tag by tag.
- SPF and its lookup budget
- The record, every nested include, and the count of DNS lookups against the limit of ten in RFC 7208. Over ten, SPF fails for everyone, including you. The SPF checker draws the whole tree.
- DKIM keys
- Keys published at selectors commonly used by popular providers, with key type and length. Selectors cannot be listed from DNS, so “none found” means only that. Test your own in the DKIM checker.
- Mail servers
- MX hosts, whether each one resolves, and the mistakes that lose mail quietly: an MX that is a CNAME, a host with no address, an address nobody outside your office can reach.
- DNSSEC and transport
- Whether the zone is signed and validates, whether MTA-STS and TLS-RPT are published, and whether the MTA-STS policy file is really there. Details live in the DNS security checker.
- The Protection Score
- SpoofKiller’s own 0 to 100 score, with the points shown per category. From a one-off scan it is partial, because two categories need report data. The scoring method is documented, weights and all.
A score is a summary. The findings are the work.
Most domains that fail this scan fail it the same way. There is an SPF record somebody wrote in 2019, a DMARC record set to p=none on the theory that it would be tightened later, and a list of sending services that has since doubled. Nothing is on fire. Anyone can still send mail that claims to come from the domain, and the domain has asked receivers, politely, to do nothing about it.
Read the findings from the top. Critical and high items are the ones that change how receivers treat your mail today. The lower items are housekeeping. Then look at the policy: a domain at p=none is being watched, not protected, and the route from there to enforcement runs through your reports.
Two cautions, because a number invites overconfidence. A score of 100 means the published controls are in order; it does not mean nobody can phish your customers from a lookalike domain. And a DNS scan sees records, not mail. Whether your invoices actually pass DMARC is a question only DMARC reports can answer, which is the part a free account takes over.

What the scan finds most often.
In rough order of how much trouble each one causes.
No DMARC record at all
Publish one at p=none with a reporting address. It blocks nothing and tells you who is sending. The DMARC generator writes it; this guide explains where it goes.
SPF needs more than ten lookups
Remove includes for services you no longer use, and move bulk senders to a subdomain with its own record. Common SPF errors covers the repair in order.
p=none, for years
Monitoring was meant to be a stage. Collect reports, fix the legitimate senders that fail, then move up. The staged plan is in how to reach p=reject.
Two SPF records
Usually one from the mailbox provider and one added later by a marketing tool. Receivers treat two records as a permanent error. Merge the mechanisms into a single record and delete the other.
No DKIM key found
Often a false alarm: the key exists under a selector we did not guess. Read the selector from a sent message with the header analyzer and test it directly.
A DMARC lookup that failed
When DNS does not answer, the scan says so and leaves the category unmeasured. Run it again. If it keeps failing, the problem is your nameservers, and it affects far more than email.
How to check a domain's email security
From a blank box to a prioritized list in under a minute.
- 1
Enter the domain
Type the domain your email addresses use, the part after the @ sign. Subdomains work too.
- 2
Run the scan
The scan performs live DNS lookups for DMARC, SPF, DKIM, MX, DNSSEC, MTA-STS, TLS-RPT, and BIMI records.
- 3
Read the findings in order
Start with critical and high findings. Each one states what is wrong and how to correct it.
- 4
Fix, then scan again
Change the DNS record, wait for the old record's TTL to expire, and run the scan again to confirm.
Questions about this tool
Straight answers. If yours is not here, ask us and a person will reply.
Want a person to read your result?
Send us the domain. We will look at the same records and write back, in plain English, with what we would fix first and why.
- A person reads every message
- No sales sequence, no list rental
- Reply within one business day
A scan is a photograph. Monitoring is the film.
Create a free account to collect and read the DMARC reports receivers are already willing to send you, for one domain, at no cost.
Related tools and guides
- SpoofKillerFree ToolsTwelve free tools for checking and building DMARC, SPF, DKIM, MX, BIMI, and DNS records. No signup for lookups.Read
- SpoofKillerFeaturesDMARC analytics, sender identification, spoofing detection, DNS change monitoring, blacklist checks, and reports.Read
- SpoofKillerKnowledge BasePlain-English guides to DMARC, SPF, DKIM, spoofing, and deliverability.Read
- GuideDMARC Alignment ExplainedWhy mail can pass SPF and DKIM and still fail DMARC, and what relaxed and strict alignment each require.Read
- GuideEmail Authentication Best PracticesThe habits that keep SPF, DKIM, and DMARC working after the day you set them up.Read
- GuideHow DMARC WorksFollow one email from send to inbox and see where SPF, DKIM, alignment, and policy each make their decision.Read
