Free DNSSEC checker
Check whether your domain publishes DNSSEC records and see what needs attention.
Example report
example.com- 1 Low
DNSSEC is not enabledLow
No DS record exists for example.com, so its DNS answers are not signed.
Next step
Enable DNSSEC at your DNS provider, then publish the DS record it gives you at your registrar.
DNSSEC
- Zone
example.com- DS records at the parent
- None
- Answers validated
- No
What the DNSSEC check looks at
DS at the parent
Whether the parent zone publishes a DS record for the domain.
Validation
Whether a public resolver marked the answer as validated.
The zone
The zone the answer comes from, for a subdomain inside a signed zone.
Evidence
The DS records found, with key tag, algorithm and digest type.
A DS record shows DNSSEC was switched on at the parent, not that every signature behind it is valid; the check does not verify signatures itself.
Understand the issue and your next step
Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.
- Enter your domain
- Review the findings
- Follow the fix guides
DNSSEC is not enabledLow
No DS record was found for the domain at its parent zone, so DNS answers for it are not signed.
DS records at the parent zone: noneDNSSEC lets resolvers detect forged DNS answers. Without it, an attacker able to tamper with DNS traffic could redirect visitors or mail. Many domains run safely without it, so this is a hardening recommendation.
Enable DNSSEC at your DNS provider, then publish the DS record it gives you at your registrar. Many providers (Cloudflare, Route 53, Azure DNS) can do both in a few clicks.
Common DNSSEC issues you can put right
DNSSEC is not enabledLow
Without a DS record at the parent, resolvers cannot detect forged answers for your domain. Turn on signing at your DNS provider, then publish the DS record at your registrar.
Keep watch after you've fixed it
Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.
Free during the preview. Domain verification required.
- NewIssue detected
- FixedConfirmed by recheck
- ReopenedDetected again
How the check works
- The zone that contains the name you enter: for a subdomain without a zone of its own, the domain above it.
- Whether the parent zone publishes a DS record for that zone, the link your registrar adds when DNSSEC is switched on.
- The DS records found, with their key tag, algorithm and digest type.
- Whether the resolver validated the answer and set the authenticated-data (AD) flag.
Reading a result
DNSSEC adds signatures to a zone's records so that a validating resolver can tell a genuine answer from a forged or altered one. Trust runs down from the root: each parent zone vouches for its child with a DS record, a digest of one of the child's keys. Without a DS record at the parent, resolvers treat the zone as unsigned, even if it has keys.
A pass means the parent publishes a DS record for the zone, so DNSSEC is switched on. A finding means no DS record was found, so resolvers cannot validate answers for the zone.
Many domains run without DNSSEC, which is why the finding is a low-severity hardening recommendation rather than an issue. DNSSEC protects against forged answers; it does not encrypt DNS or hide which names are looked up.
What it does not do
- It does not fetch DNSKEY records or verify signatures itself. A DS record shows DNSSEC was switched on at the parent, not that every signature behind it is currently valid.
- The validation flag is what one public resolver reported for the answer; it does not test how other resolvers behave.
- It checks the zone, not each name in it, and does not look at zones delegated below it.
What happens to the domain you enter
The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.
Guides
A few things worth knowing
- What is a DS record?
- A Delegation Signer record: a digest of one of your zone's DNSSEC keys, usually the key-signing key, published in the parent zone through your registrar. It links the parent's signatures to yours, so resolvers can follow the chain of trust down to your records.
- Can turning on DNSSEC break my domain?
- Yes, if the steps happen out of order. A DS record that does not match the keys your zone is signed with makes validating resolvers reject your answers, and the domain stops resolving for their users. Sign the zone first, then add the DS record. Before moving to another DNS provider, follow its steps for DNSSEC, or remove the DS record and let it expire first.
- Is DNSSEC required for Cyber Essentials or ISO 27001?
- No. Neither names DNSSEC. It is a hardening measure an organisation can choose, and where it does, this check is evidence that it is switched on.
- Does DNSSEC encrypt DNS?
- No. It signs answers so they can be checked, but queries and answers still travel unencrypted. Encrypting DNS traffic is separate, done with DNS over HTTPS or DNS over TLS.

