DNSSEC chain check: root to answer
Type a name. The chain draws below: every zone from the root (or your own anchor) to the answer, and the first link that breaks.
1. a domain name
try: example.com · an island · a broken island, from its key · expired signatures · a DS that matches nothing
Walk the DNSSEC chain
Follows the DNSSEC chain from the root down to one answer and shows the first link that breaks, if one does.
from where
The isitdns edge, read through a public resolver over DoH with checking disabled.
what it does not read
- Signature bytes: a clean walk does not prove the answer validates.
- What a validating resolver decided: that is dig with dnssec on.
inputs
| input | type | default | what it is |
|---|---|---|---|
name required | string | The name, e.g. www.example.com. Also as "domain"; a URL is read as its host. | |
type | string | "A" | The record type to check at the end of the chain |
anchor | string | A trust anchor: "DS <key tag> <algorithm> <digest type> <digest>" or "DNSKEY <flags> <protocol> <algorithm> <key>", optionally led by its owner name | |
anchor_zone | string | The zone the anchor belongs to: the name or a parent of it. Optional when the anchor record leads with its owner |
the call
{"name":"dnssec_chain","arguments":{"name":"example.com"}}Over MCP at https://isitdns.net/mcp: connect a client.
how to read it, an example, and the commands
The word at the top of the drawn chain, and the tag on each card. The same walk as text: dnssec_chain over MCP, or the text link under the chain.
- GO the word reads
No structural break foundand every cardOK: each DS matches a key in the zone below, each key set is signed by a matched key inside its window, and the answer is signed by a key in its zone. Signature bytes are not verified;delvbelow is the check that verifies them. - NO GO a card reads
BREAK, with the reason in pink: a DS with no matching DNSKEY, or a signature outside its window -> zone operator: publish the DS that matches the KSK in use (RFC 4034 section 5), or re-sign before the window ends (RFC 4034 section 3.1.5). - INCONCLUSIVE
INSECURE: no DS at that zone's parent, so a validator treats everything below as unsigned and validates nothing there (RFC 4035 section 5.2). Not a break. - INCONCLUSIVE
ISLAND: an insecure zone that serves a DNSKEY set with an RRSIG by a key in that set. A validator reaches it only from an anchor for that zone (RFC 4033 section 2); walk it from one of its keys, pasted as step 2, your own trust anchor. - NOT RUN
NOT CHECKED: the walk could not decide that card (a digest type not computed here, two resolvers that disagreed, a record that did not read); the reason is listed under the chain. Not a GO. - With your own anchor, the first card is your anchor's zone, nothing above it is read, and its line says
matches tag N,matches no usable key(a BREAK: check it againstdig @1.1.1.1 <zone> DNSKEY) ormatch not decided.
Saved example. example.com A, read 2026-10-18T22:02:07Z:
isitdns · dnssec chain · example.com A
;; read through cloudflare-dns.com over DoH with RD=1, DO=1 and CD=1 (RFC 4035 section 3.2.2), 2026-10-18T22:02:07.257Z, from the Cloudflare edge · checked: key tags, signers, windows · sigs: not verified
No structural break found; signature bytes not verified.
. (root)
DNSKEY: tag 8763 alg 8 ZSK; tag 20326 alg 8 KSK; tag 38696 alg 8 KSK
DNSKEY set signed: tag 38696 alg 8 by ., inside (20261011000000 to 20261101000000)
com
DS at the parent: 1 (19718 13 2 8ACBB0CD28F41250A80A491389424D341522D946B0DA0C0291F2D3D771D7805A); signed tag 8763 alg 8 by ., inside (20261018160000 to 20261031170000)
DNSKEY: tag 41446 alg 13 ZSK; tag 65344 alg 13 ZSK; tag 19718 alg 13 KSK
DS matches: tag 19718
DNSKEY set signed: tag 19718 alg 13 by com, inside (20261014135735 to 20261029140235)
example.com
DS at the parent: 1 (2371 13 2 C988EC423E3880EB8DD8A46FE06CA230EE23F35B578D64E78B29C3E1C83D245A); signed tag 65344 alg 13 by com, inside (20261017002323 to 20261024013323)
DNSKEY: tag 36315 alg 13 ZSK; tag 9776 alg 13 ZSK; tag 34505 alg 13 ZSK; tag 2371 alg 13 KSK
DS matches: tag 2371
DNSKEY set signed: tag 2371 alg 13 by example.com, inside (20260925174647 to 20261125174647)
answer: NOERROR, 2 A records (A 172.66.147.243; A 104.20.23.154); signed tag 34505 alg 13 by example.com, inside (20261017205919 to 20261019225919)
api: https://isitdns.net/api/dnssec-chain?name=example.com&type=Adelv @1.1.1.1 example.com A
dig +dnssec @1.1.1.1 example.com DS
delv validates every link against its own root key and prints one verdict; dig DS reads the one record the parent holds for the child.
- The DNSSEC chain, walked live: what the drawing shows and what it does not verify
- DNSSEC: how the chain works
- RFC 4033: introduction and requirements · RFC 4034: the DS, DNSKEY and RRSIG records · RFC 4035: validation