A domain suddenly fails for some visitors but works for others. Support says "it resolves fine here", yet users of Google Public DNS or a corporate resolver get errors. Very often the cause is DNSSEC: a DS record at the registrar that no longer matches the zone's key after a provider change, or signatures that stopped being refreshed. These failures are invisible to anyone whose resolver does not validate.
The DNSSEC Checker validates the complete chain of trust for a domain — from the root zone, through the TLD, to the domain's own keys and signatures — and explains every problem it finds in plain language, with the evidence and the fix.
What is DNSSEC?
In simple terms
DNSSEC adds digital signatures to DNS answers. A validating resolver can then check that an answer really comes from the zone owner and was not changed on the way. Trust flows downwards: the root zone vouches for .com, .com vouches for example.com, and example.com signs its own records.
Technical background
Each signed zone publishes DNSKEY records (its public keys) and RRSIG records (signatures over each set of records). The parent zone publishes a DS record — a hash of the child's key-signing key. A validator starts from the root trust anchor, checks that the root keys match it, then follows DS → DNSKEY → RRSIG down every delegation. Negative answers ("this name does not exist") are authenticated with NSEC or NSEC3 records. If any link fails, the answer is BOGUS and validating resolvers return SERVFAIL.
Why use a DNSSEC checker?
DNSSEC problems hurt availability rather than security warnings: a broken chain makes the domain unreachable for every user behind a validating resolver, and most website monitoring does not notice. A checker shows whether DNSSEC is enabled, whether it actually works, and exactly which link is broken — before customers report it. It is especially valuable after changing DNS provider or registrar, during key rollovers, and when enabling DNSSEC for the first time.
Who should use it?
Domain owners checking that the DNSSEC switch at their registrar really took effect, system administrators and DNS operators planning key or algorithm rollovers, help desks investigating "works for me" resolution failures, security teams auditing domain portfolios, and anyone migrating a domain between DNS providers — the moment when a stale DS record most often breaks a domain.
How the DNSSEC checker works
The checker runs on a NetTools server and does not rely on a recursive resolver's cache. It starts at the root servers and follows referrals down to the domain with non-recursive queries, asking for DNSSEC records with the DO bit. At every level it verifies that the parent's DS record set is validly signed, that a DS matches a published DNSKEY, and that the DNSKEY set is signed by that key. The root keys are compared with the IANA root trust anchor (KSK-2017 and KSK-2024).
For the domain's own zone it then checks the SOA and NS signatures, asks for one random non-existent name to test the NSEC or NSEC3 proof, queries every authoritative name server separately, asks the parent's servers for the DS set, and finally compares its verdict with the Cloudflare, Google and Quad9 validating resolvers. All signatures are verified with OpenSSL; the DO bit only requests DNSSEC records and proves nothing by itself. Related tools: DNS Lookup shows individual records and DNS Propagation compares resolvers worldwide.
How to use the NetTools.tech DNSSEC Checker
- Open the DNSSEC Checker and enter a domain such as
example.com. Internationalized names are converted automatically. - Optionally choose the resolver used to look up name-server addresses. It never decides the DNSSEC verdict.
- Under Advanced options, tick Fresh analysis after a recent change so cached answers are ignored.
- Click Check DNSSEC. The progress list shows the real stage the server is working on; most checks finish in a few seconds.
- Read the overview, open the chain of trust, and use the findings for fixes. Export the result as PDF, CSV, JSON or print it.
Understanding the results
The overall status is one of five values. SECURE: every link from the root validates. INSECURE: there is no DS record in the parent — the domain is unsigned, which is a valid configuration, not an error. BOGUS: a DS exists but the keys or signatures do not validate; the domain fails for validating resolvers. WARNING: validation succeeds but something needs attention. UNKNOWN: servers did not answer, so no verdict was possible — a reachability issue, not a DNSSEC failure.
The chain of trust shows each zone with its DS (or trust anchor), DNSKEY and RRSIG state; the level where the chain breaks is highlighted. The DS table shows key tag, algorithm, digest type and whether it matches a published key. The DNSKEY table shows each key's flags, size and actual role — KSK, ZSK or a combined CSK. The RRSIG table lists every verified signature with its validity window and remaining time. Name servers compares DNSKEY sets, signatures and SOA serials per server, and Findings lists each problem by severity with evidence and remediation.
Example: a DS record that no longer matches
After moving shop.example to a new DNS provider, the provider generated new keys, but the old DS record stayed at the registrar. The checker reports BOGUS. The chain shows the root and the TLD as SECURE and breaks at shop.example.: the DS key tag 42069 matches none of the published keys (32784 and 50719). The CRITICAL finding explains that validating resolvers return SERVFAIL and gives the fix: replace the DS at the registrar with the value for the current key-signing key — or, when turning DNSSEC off, remove the DS first and wait for its TTL before unsigning.
Common use cases
- Confirming that enabling DNSSEC at the registrar and DNS provider produced a SECURE chain.
- Checking a domain before and after a DNS provider migration.
- Following a KSK rollover: both DS records present, the new key published, no stale DS left behind.
- Auditing algorithms across a domain portfolio and planning moves away from RSA/SHA-1.
- Explaining SERVFAIL reports from users of validating resolvers.
Troubleshooting
"DS record does not match any DNSKEY"
The registrar still has a DS for an old key, or the digest was copied incorrectly. Generate the DS from the current KSK at your DNS provider and replace it at the registrar.
"DNSKEY signature has expired"
The zone is no longer being re-signed. Check that DNSSEC signing is active at your provider, or check your signer's automation, keys and logs.
"Name servers return different DNSKEY sets"
Usually a secondary server has not transferred the current zone. Compare the SOA serials in the name-server table and fix zone transfers. During a rollover this can be temporary.
UNKNOWN status
Some or all authoritative servers did not answer. Check that they respond on UDP and TCP port 53, then run the check again.
Resolvers disagree with NetTools
A recent change may still be cached by resolvers. Wait for the DS and DNSKEY TTLs and re-run the check with Fresh analysis.
Common mistakes
- Removing DNSSEC at the DNS provider while the DS record is still at the registrar — this makes the domain BOGUS. Always remove the DS first.
- Copying a SHA-1 DS only; publish a SHA-256 (digest type 2) DS.
- Treating INSECURE as an error. It only means DNSSEC is not enabled.
- Assuming one working name server means all of them are correct.
- Keeping very high NSEC3 iteration counts; RFC 9276 recommends 0 iterations and no salt.
Limitations
The checker examines the zone that contains the domain and the standard apex records; it does not test every record in the zone. It validates algorithms 5, 7, 8, 10, 13, 14, 15 and 16; zones using only other algorithms are reported as unsupported, which RFC 4035 treats as insecure. IPv6-only name servers are queried only where the server has IPv6 connectivity. Results describe the moment of the check; DS and DNSKEY changes take time to propagate.
Security & privacy
Only the submitted public domain is examined. Internal and reserved TLDs are refused, and name servers that point to private, loopback or link-local addresses are never contacted. Each analysis is limited to 220 queries and 30 seconds, with per-client rate limits and one running analysis per visitor. The check performs no zone transfers or name guessing. Results are kept in memory for 15 minutes and are not stored.
Related tools
- DNS Lookup — query individual records such as NS, SOA or DS.
- DNS Propagation Checker — compare answers from resolvers around the world after a change.
- Whois Lookup — see the registrar and whether the registry reports a signed delegation.
- SSL/TLS Security Analyzer — check the HTTPS side of the same domain.
Summary
DNSSEC protects DNS answers only when every link in the chain of trust is correct. The NetTools.tech DNSSEC Checker validates that chain from the root itself, verifies signatures cryptographically, checks every name server and shows exactly what to fix — so a broken DS record or an expired signature is found before it takes your domain offline for validating resolvers.
Frequently asked questions
What is the difference between INSECURE and BOGUS?
INSECURE means the domain is not signed: there is no DS record in the parent zone, so answers are not authenticated but resolve normally. BOGUS means a DS record says the zone is signed, yet keys or signatures do not validate; validating resolvers then return SERVFAIL and the domain stops working for their users.
Where is the DS record configured?
In the parent zone, for example .com, and you set it at your registrar in the domain's DNSSEC settings. Your DNS provider shows the values to enter. The checker reads the DS from the parent's name servers; it has no access to your registrar account.
Why does my domain show WARNING although it validates?
WARNING means the chain of trust is valid but something needs attention: a deprecated algorithm such as RSA/SHA-1, a SHA-1-only DS record, signatures close to expiry, name servers that disagree, or validating resolvers that report a different result.
Is a short signature lifetime a problem?
Not on its own. Online signers such as Cloudflare create signatures valid for a day or two and refresh them continuously. The checker only warns when less than three days and less than a quarter of the signature's validity window remain.
Is NSEC a security vulnerability?
No. NSEC allows the names in a zone to be listed by walking the chain, which is a privacy consideration rather than a flaw. NSEC3 with zero extra iterations and no salt, or compact denial of existence, makes listing harder.
Does the checker rely on a public resolver's AD flag?
No. It queries the root, TLD and authoritative servers itself and verifies every signature with OpenSSL against the IANA root trust anchor. Cloudflare, Google and Quad9 are only asked afterwards as a cross-check, and any disagreement is shown.
Does the check enumerate my zone?
No. It asks for the standard records of the zone apex and for one random, non-existent name to test negative answers. It performs no zone transfers and no name guessing.