The tools we use to find out what a domain is really telling the world.
Check, build, and analyze DMARC, SPF, DKIM, MX, BIMI, and DNS records. Real lookups, plain answers, and no form standing between you and the result.
Runs the full domain health check. Or pick a single tool below.
Look up what a domain publishes right now.
Live DNS lookups, explained in sentences. Start with the health check; the others go deeper on one record each.
- Domain Health CheckerRun a full email security scan on any domain. DMARC, SPF, DKIM, MX, DNSSEC, MTA-STS, and BIMI, scored and explained. No signup.Start here
- DMARC CheckerThe policy receivers actually apply, tag by tag.Open tool
- SPF Record CheckerThe full include tree and the lookup count against the limit of ten.Open tool
- DKIM Record CheckerKey type, length, and revocation for your selectors.Open tool
- MX Record CheckerMail servers, priorities, addresses, and the provider behind them.Open tool
- BIMI CheckerThe record, the logo, the certificate, and whether DMARC qualifies.Open tool
- DNS Security CheckerDNSSEC, nameservers, CAA, MTA-STS, and TLS-RPT in one pass.Open tool
- DNS Propagation CheckerThe same question asked of six public resolvers at once.Open tool
Write a record without learning the grammar.
Generators that run in your browser and produce a record you can paste, with the host name and the steps for your DNS provider.
Read the evidence email leaves behind.
One for the XML reports receivers send you, one for the headers on a single message.
A lookup is a question anyone may ask. We just answer it properly.
Email authentication lives in public DNS. Your SPF record, your DKIM keys, and your DMARC policy are there for any mail server to read, which means they are there for you to read too. The difficulty has never been access. It is that the answers come back as strings like v=spf1 include:_spf.example.net ~all, and the consequences of getting one wrong arrive weeks later as a customer asking why the invoice never came.
So each tool here does the reading and then says what it found, in order of how much it matters. If you are new to the subject, SPF vs DKIM vs DMARC explains the three standards in a few minutes, and how to configure DMARC takes you from no record to a published one. The tools will still be here when you come back to check your work.
What a lookup cannot do is watch. It cannot tell you that a server you have never heard of sent four hundred messages as your domain on Tuesday. That information exists, in the reports receivers send to the address in your DMARC record, and reading them continuously is what DMARC monitoring and spoofing detection are for. One domain is free. Plans are here, and if you look after other people’s domains, there is a version for that.

Questions about the free tools
Straight answers. If yours is not here, ask us and a person will reply.
Rather have someone run them for you?
Send us your domain. We will run the same checks and write back with what we found and what we would fix first.
- A person reads every message
- No sales sequence, no list rental
- Reply within one business day
Checked once is a start. Watched is the point.
Create a free account to collect DMARC reports for one domain and see what is being sent in its name.
Guides to read alongside
- Free toolDomain Health CheckerRun a full email security scan on any domain. DMARC, SPF, DKIM, MX, DNSSEC, MTA-STS, and BIMI, scored and explained. No signup.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
- 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
