DNSSEC Checker
Check whether a domain is signed with DNSSEC and whether the chain of trust holds. The tool reads the DNSKEY and DS records of the domain and its parent zones, computes each key tag and DS digest to see that the parent's DS matches a key, checks signature expiry dates and asks a validating resolver whether answers for the name are authenticated or fail validation.
Frequently asked questions
What do secure, insecure and bogus mean?
Secure means a validating resolver could follow signatures from the root down to the name and set the authenticated data flag. Insecure means the name is not signed or a parent has no DS record for it, so answers are not protected but still resolve. Bogus means the domain is signed but validation fails, so validating resolvers refuse to answer and the domain is unreachable for their users.
How does the tool check the DS record?
For each zone it computes the key tag of every DNSKEY and the SHA-1, SHA-256 or SHA-384 digest of the owner name and key as defined in RFC 4034. A DS record matches when its tag, algorithm and digest equal one computed from a published key. A DS with no matching key breaks the chain.
Does the tool verify every signature itself?
No. It checks the key and DS relationship and the signature dates itself, and relies on the validating resolvers of Google Public DNS or Cloudflare for the cryptographic verification of signatures, which it reads from their authenticated data flag and from the SERVFAIL answer they give for a bogus name.
What is the difference between a KSK and a ZSK?
The key signing key, with the flags value 257, signs the DNSKEY set and is the key the parent's DS record points to. The zone signing key, with 256, signs the other records. Many zones use one combined key, which then has the KSK flag.
Why is an algorithm marked as weak?
RFC 8624 recommends against signing with RSA and SHA-1 (algorithms 5 and 7) and forbids older ones such as RSAMD5, DSA and GOST. Current zones should use ECDSAP256SHA256 (13), RSASHA256 (8) or ED25519 (15). DS records with a SHA-1 digest are flagged for the same reason.
What should I do when the result is bogus?
The most common causes are a DS record at the registrar that still points to an old key after a key rollover or provider change, and expired signatures. Remove or update the DS record at your registrar, or re-sign the zone, then check again after the DS TTL has passed.