DNSSEC checker: does your domain's signature chain validate?

GitHubVersion 1.1.0

Enter a domain and record type to check whether its DNSSEC signatures validate, link by link, from the DNS root down to that answer. The result is Secure, Insecure, Bogus, or Indeterminate, with the first step that fails.

Record type Required

What do Secure, Insecure, Bogus, and Indeterminate mean?

ResultWhat it means
SecureThe answer is signed, and every link checks out to the root. This includes a signed proof that a record or name doesn't exist.
InsecureThe name isn't signed, and the chain proves that on purpose. Nothing is broken.
BogusThe name should be signed, but a link fails. Resolvers that check DNSSEC return SERVFAIL, so the name stops working for their users.
IndeterminateThe check couldn't finish. Run it again before you change anything.

DNSSEC signs each answer, not the domain as a whole. Pick the record type that's failing, or A for a general check.

dnssec-failed.org, A record

Example

The result is Bogus. The steps pass from the root through org and the DS record for dnssec-failed.org, then fail: no key in the zone matches the DS record its parent publishes. Cloudflare's resolver returns SERVFAIL for the A record, so its users can't reach the name.

Comcast runs this domain as a DNSSEC test, broken on purpose. Checked on 9 October 2026.

How does the DNSSEC chain of trust work?

Each zone vouches for the one below it. Three record types do the work:

RecordLives inWhat it does
DNSKEYThe zoneThe zone's public keys.
RRSIGThe zoneA signature over a set of records, made with one of those keys.
DSThe parent zoneA fingerprint of the child zone's key. For your domain, you set it through your registrar.

Validation starts from the root's key, which resolvers already trust. It checks that each DS matches a DNSKEY one level down, that the keys are signed, and that the answer's RRSIG is valid. RFC 4033 describes the design.

Having DS and DNSKEY records isn't enough. They have to match, and the signatures have to be valid.

How do I fix a Bogus result?

Start with the first step marked Failed:

  • If the DS link fails, the DS record at your registrar doesn't match the zone's keys. This often happens after changing DNS provider or keys. Copy the current DS value from your DNS provider to your registrar, or delete the DS to turn DNSSEC off.
  • If a DNSKEY or answer step fails, a signature is bad or has expired. Signature validity shows when each one runs out. Your DNS provider usually signs the zone, so ask them.

Is an Insecure result a problem?

No. It means DNSSEC isn't turned on for this name. Answers resolve normally, but they aren't protected against forged replies. Turning it on takes a setting at your DNS provider and a DS record at your registrar.

Where does the verdict come from?

stack127 checks the signatures itself with the Namefi DNSSEC Audit library, fetching records through Cloudflare's public resolver. The Resolver AD rows repeat the resolver's own flag for reference, and the verdict doesn't use them. That's also why the DNSSEC line in DNS lookup isn't a DNSSEC check.

The check runs from stack127's server, and stack127 doesn't keep the names you check.