Skip to content
SpoofKiller
Free tool · no signup

Your email records are only as trustworthy as the DNS that serves them.

Check the layer underneath SPF, DKIM, and DMARC: whether the zone is signed and validates, who your nameservers are, which authorities may issue your certificates, and whether inbound mail is required to arrive encrypted.

What the checker examines

Five records most domains have never looked at.

None of them is required for email to work. Each closes a specific gap that the authentication records leave open.

DNSSEC
Whether a DS record exists at the parent zone, whether the zone publishes DNSKEYs, and whether a validating resolver confirms the chain. Signed, unsigned, incomplete, and broken are four different states, and the checker tells them apart.
Nameservers
The NS records for the zone and the DNS host they belong to. A single nameserver is a single point of failure for the website and the mail together.
CAA
Records naming the certificate authorities permitted to issue certificates for the domain. Without them, any public authority may.
MTA-STS
The DNS record and the policy file it announces, fetched over HTTPS. The checker reads the mode, the max_age, and whether every MX host is covered by the policy (RFC 8461).
TLS-RPT
The record asking other mail servers to report when they cannot establish TLS with yours (RFC 8460). It is how you find out that MTA-STS is hurting before you enforce it.
Findings with fixes
Each problem is graded and paired with the correction. For the authentication records themselves, use the domain health check, which scores everything together.
How to read the result

SPF, DKIM, and DMARC are all promises made in DNS. This is about the DNS.

Every email authentication check ends in a DNS lookup. The receiver asks for your SPF record, your DKIM key, your DMARC policy, and believes what comes back. DNSSEC is the mechanism that lets a resolver verify the answer was not altered on the way. Without it, the records are published in good faith and received on trust.

DNSSEC has a reputation for being easy to break, and the reputation is earned. A signed zone whose DS record does not match its keys does not degrade gracefully: validating resolvers return nothing at all, and the domain disappears for everyone who uses them, mail included. That is the “broken” state, and it is worse than unsigned. If the checker reports it, fix it today. If you are enabling DNSSEC for the first time, most DNS hosts now do it with one switch and a DS record at the registrar; the Cloudflare DNS guide shows the pattern.

MTA-STS and TLS-RPT address transport. Mail between servers is encrypted opportunistically, which means an attacker who can interfere with the connection can quietly remove the encryption. MTA-STS lets you publish a policy saying: deliver to these hosts, over verified TLS, or not at all. Start in testing mode with TLS-RPT collecting reports, and enforce when the reports are clean. The policy must list your real mail servers, so check them with the MX lookup. Changes to any of these records are worth knowing about promptly, which is what domain security monitoring does on a schedule. The wider habits are in email authentication best practices.

Rows of keys hanging on a locksmith's board, with one bright yellow key among them.
Signing a zone is easy. Remembering which key the registrar is holding, a year later, is the hard part.
Common problems and fixes

What goes wrong at this layer.

  • A DS record with no matching keys

    Typically left behind when a domain moves to a DNS host that is not signing. Either enable signing at the new host and update the DS record, or remove the DS record at the registrar. Until then the domain fails to resolve for validating resolvers.

  • Signed, with no DS at the registrar

    The zone publishes keys, and nobody can verify them because the parent zone does not vouch for them. Copy the DS record from your DNS host to your registrar to complete the chain.

  • MTA-STS record without a reachable policy file

    The DNS record announces a policy; the file must be served at https://mta-sts.yourdomain/.well-known/mta-sts.txt with a valid certificate and no redirect. Senders ignore the record if they cannot fetch it.

  • MX hosts missing from the MTA-STS policy

    In enforce mode, senders refuse to deliver to an MX host the policy does not list. Add every host (or a matching wildcard), then change the id in the DNS record so senders refetch.

  • Policy changed and the id did not

    Senders cache the policy until the id in the TXT record changes. Edit the file, then update the id.

  • Only one nameserver

    If it is unreachable, so is everything. Use at least two, on separate networks. Then confirm the change reached public resolvers with the DNS propagation checker.

How to

How to check a domain's DNS security

Review DNSSEC, nameservers, CAA, MTA-STS, and TLS-RPT in one pass.

  1. 1

    Enter the domain

    Use the domain that receives your mail. Zone-level checks run against the registrable domain.

  2. 2

    Check the DNSSEC state

    Signed and validated is the goal. Broken needs immediate attention; unsigned is a gap, not an outage.

  3. 3

    Review transport security

    Confirm the MTA-STS policy file is reachable, lists your MX hosts, and note its mode. Confirm TLS-RPT has a reporting address.

  4. 4

    Work through the findings

    Fix high-severity items first, publish the changes, and run the check again after the TTL.

See all twelve free tools

FAQ

Questions about this tool

Straight answers. If yours is not here, ask us and a person will reply.

Ask a question

Free, no obligation

DNSSEC showing as broken?

Send us the domain. We will tell you which side, registrar or DNS host, is holding the mismatched record, and the order in which to fix it.

  • A person reads every message
  • No sales sequence, no list rental
  • Reply within one business day

We use your details to reply. Nothing else.

The foundation is checked. Now see what is built on it.

Create a free account to collect DMARC reports for your domain. On the Pro plan, DNS changes are checked every six hours and you are told when a record moves.