← All Docs

DNSSEC Toolkit

Check if a domain is signed with DNSSEC: see DS and DNSKEY records, AD and CD flags, signature expiry, and a DS digest recomputed right in your browser.

Try DNSSEC Toolkit →

What Does the DNSSEC Checker Do?

The DNSSEC Toolkit tells you whether a domain is protected by DNSSEC and shows the records that make it work. It asks a public DNS-over-HTTPS resolver (Google or Cloudflare) for the zone's DS, DNSKEY and SOA records with the DNSSEC OK bit set, then reads the resolver's flags. The result is one of: signed and validated, signed but not validated, bogus (broken), island of security, or unsigned.

Two checks are computed in your browser rather than taken on trust: the key tag of every DNSKEY (RFC 4034 Appendix B) and the DS digest, recomputed from the owner name and the key with Web Crypto and compared with the DS record the parent zone publishes.

How Do I Check a Domain?

  1. Open DNS Tools > DNSSEC Toolkit from the top menu.
  2. Type a domain or zone name, for example cloudflare.com or a TLD such as com.
  3. Pick the resolver: Google Public DNS or Cloudflare 1.1.1.1. The query goes from your browser straight to that resolver.
  4. Click Check or press Enter.
  5. Read the status card, then the response flags table (AD, CD, RD, RA, TC) for each query.
  6. Review the DS and DNSKEY tables and the list that matches each DS record to a DNSKEY by key tag and recomputed digest.
  7. Check the RRSIG table for signature expiry dates, then use Copy report or Download .txt.

How Does the DNSSEC Chain of Trust Work?

A validating resolver trusts one key out of the box: the root zone's key-signing key. The root publishes a DS record for each signed top-level domain, such as com. The TLD publishes a DS record for each signed domain under it. Each DS is a hash of the child's key-signing key (DNSKEY flags 257). The child's DNSKEY set is signed by that key, and its other records are signed by the zone-signing key (flags 256) with RRSIG records.

If every link checks out, the resolver sets the AD (Authenticated Data) flag. If a link is missing, for example a zone publishes DNSKEY records but the parent has no DS, the zone is an island of security and is treated as unsigned. If a link is wrong, the resolver refuses to answer and returns SERVFAIL.

What Do the AD, CD and DO Flags Mean?

  • DO (DNSSEC OK): set by the tool on every query, so the resolver returns RRSIG signatures with the answer.
  • AD (Authenticated Data): the resolver validated the answer all the way from the root.
  • CD (Checking Disabled): asks the resolver to skip validation. The tool repeats the SOA query with CD=1. A SERVFAIL without CD but a normal answer with CD is the classic sign of broken DNSSEC.

What Can a Browser Not Verify?

The tool does not validate RRSIG signatures itself. That needs the full chain of keys from the root and every signature algorithm, so for the full chain verdict the page relies on the resolver's AD flag and says so. Answers come from one resolver's cache, and your ISP or office resolver may validate differently or not at all. DNS-over-HTTPS JSON also hides some wire-format details, such as the DO bit in replies. The key tags and DS digests shown as matching are computed locally and are exact.

Use Cases

  • After enabling DNSSEC: confirm the registrar submitted the DS record and it matches your published key.
  • Key rollovers: see which DS and DNSKEY key tags are live, and spot a stale DS before it breaks resolution.
  • Outage triage: tell a DNSSEC failure (bogus) apart from a missing record when a domain stops resolving.
  • Audits: check algorithms against RFC 8624 guidance and watch signature expiry dates.

Frequently Asked Questions

How do I know if my domain has DNSSEC enabled?

Enter the domain in the DNSSEC Toolkit and click Check. If the parent zone publishes a DS record and the resolver sets the AD flag, the domain is signed and validates. If there is no DS record, DNSSEC is not enabled at the registry, even if the zone itself is signed.

What does a bogus DNSSEC result mean?

The resolver returned SERVFAIL for a normal query but answered when checking was disabled with CD=1. That means the data exists but the signatures or keys do not match the DS record, so every validating resolver will refuse the name until the chain is fixed.

What is the difference between a KSK and a ZSK?

The key-signing key (DNSKEY flags 257, the SEP bit) signs only the DNSKEY set and is the key the parent DS record points to. The zone-signing key (flags 256) signs all the other records. Splitting them lets operators roll the zone-signing key without touching the parent.

Does the DNSSEC checker validate signatures in my browser?

It recomputes DNSKEY key tags and DS digests locally, but it does not verify RRSIG signatures. For the full chain verdict it reports the resolver AD flag, and the page lists exactly what is and is not checked.

Who sees the domains I check?

Only the DNS-over-HTTPS resolver you pick, Google Public DNS or Cloudflare, because your browser sends the queries to it directly. 2network does not receive or store the names, and no analytics are recorded for what you type.