DNSSEC visualizer
Draw a domain's chain of trust as a graph of zones, keys and signatures, with the broken link marked.
Results for www.visualstudio.github.com
DNSSEC: Insecure
www.visualstudio.github.com isn't signed with DNSSEC. That is a choice, not a fault.
Anyone can still look it up. DNSSEC would let resolvers prove the answers weren't altered.
None set the AD bit, which is normal for an unsigned name
Chain of trust, 4 steps
- Root.Trust anchor
- KSK 20326 · RSA/SHA-256
- KSK 38696 · RSA/SHA-256
- ZSK 8763 · RSA/SHA-256
Two root KSKs are published during the planned root key rollover. That is normal.
ZSK 8763 signs the DS for com.
Valid for 13 days in total, 12 days left HoldsDS 19718 · ECDSA P-256 · SHA-256 · matches KSK 19718
Top-level domaincomPass- KSK 19718 · ECDSA P-256
- ZSK 65344 · ECDSA P-256
No DScom has no DS for github.com, and proves it with NSEC3 (opt-out, 0 iterations)
Your zonegithub.comNot signed- AnswerSOA www.visualstudio.github.comNot signed
What public resolvers say
| Resolver | Answer | Validated (AD) | Their reason |
|---|---|---|---|
| Cloudflare 1.1.1.1 | NXDOMAIN | No | |
| Google 8.8.8.8 | NXDOMAIN | No | |
| Quad9 9.9.9.9 | NOERROR | No |
Structured result (JSON) · 5.7 KB
{
"name": "www.visualstudio.github.com",
"zone": "github.com",
"type": "SOA",
"mode": "live",
"verdict": "insecure",
"state": "unsigned",
"verdictText": "www.visualstudio.github.com isn't signed with DNSSEC. That is a choice, not a fault.",
"explain": "Anyone can still look it up. DNSSEC would let resolvers prove the answers weren't altered.",
"anchor": {
"kind": "iana-root",
"keyTag": 20326,
"algorithm": 8
},
"chain": [
{
"zone": ".",
"role": "root",
"status": "ok",
"keys": [
{
"tag": 20326,
"flags": 257,
"role": "ksk",
"algorithm": 8,
"bits": 2048,
"anchor": true
},
{
"tag": 38696,
"flags": 257,
"role": "ksk",
"algorithm": 8,
"bits": 2048,
"anchor": true
},
{
"tag": 8763,
"flags": 256,
"role": "zsk",
"algorithm": 8,
"bits": 2048
}
],
"dnskeySig": {
"by": 38696,
"valid": true,
"expires": "2026-12-01T00:00Z",
"lifetimeDays": 21,
"lifetimeHours": 504,
"leftHours": 337.9
},
"link": null,
"servers": []
},
{
"zone": "com",
"role": "tld",
"status": "ok",
"keys": [
{
"tag": 19718,
"flags": 257,
"role": "ksk",
"algorithm": 13,
"bits": 256,
"anchor": true
},
{
"tag": 65344,
"flags": 256,
"role": "zsk",
"algorithm": 13,
"bits": 256
}
],
"dnskeySig": {
"by": 19718,
"valid": true,
"expires": "2026-11-28T15:02Z",
"lifetimeDays": 15,
"lifetimeHours": 360,
"leftHours": 280.9
},
"link": {
"status": "ok",
"word": "Holds",
"text": "DS 19718 · ECDSA P-256 · SHA-256 · matches KSK 19718",
"ds": [
{
"tag": 19718,
"algorithm": 13,
"digestType": 2,
"matches": 19718
}
],
"signedBy": 8763,
"expires": "2026-11-29T17:00Z",
"lifetimeHours": 313,
"leftHours": 306.9
},
"servers": []
},
{
"zone": "github.com",
"role": "zone",
"status": "unsigned",
"keys": [],
"dnskeySig": null,
"link": {
"status": "unsigned",
"word": "No DS",
"text": "com has no DS for github.com, and proves it with NSEC3 (opt-out, 0 iterations)",
"ds": []
},
"servers": []
}
],
"denial": {
"kind": "nsec3",
"proves": "no DS for github.com (opt-out)"
},
"issues": [],
"extras": {
"cds": false,
"cdnskey": false,
"nsec3param": null,
"walkable": false,
"suggestedDs": null
},
"rdap": {
"dsData": [],
"matchesZone": true
},
"resolvers": [
{
"name": "Cloudflare 1.1.1.1",
"ip": "1.1.1.1",
"ad": false,
"rcode": "NXDOMAIN",
"ede": null
},
{
"name": "Google 8.8.8.8",
"ip": "8.8.8.8",
"ad": false,
"rcode": "NXDOMAIN",
"ede": null
},
{
"name": "Quad9 9.9.9.9",
"ip": "9.9.9.9",
"ad": false,
"rcode": "NOERROR",
"ede": null
}
],
"graph": {
"nodes": [
{
"id": "z0-ksk-20326",
"kind": "ksk",
"zone": ".",
"label": "KSK 20326",
"tag": 20326,
"status": "ok",
"row": 0,
"zoneIndex": 0
},
{
"id": "z0-ksk-38696",
"kind": "ksk",
"zone": ".",
"label": "KSK 38696",
"tag": 38696,
"status": "ok",
"row": 1,
"zoneIndex": 0
},
{
"id": "z0-zsk-8763",
"kind": "zsk",
"zone": ".",
"label": "ZSK 8763",
"tag": 8763,
"status": "ok",
"row": 2,
"zoneIndex": 0
},
{
"id": "z1-ds-19718",
"kind": "ds",
"zone": "com",
"label": "DS 19718",
"tag": 19718,
"status": "ok",
"row": 0,
"zoneIndex": 1
},
{
"id": "z1-ksk-19718",
"kind": "ksk",
"zone": "com",
"label": "KSK 19718",
"tag": 19718,
"status": "ok",
"row": 1,
"zoneIndex": 1
},
{
"id": "z1-zsk-65344",
"kind": "zsk",
"zone": "com",
"label": "ZSK 65344",
"tag": 65344,
"status": "ok",
"row": 2,
"zoneIndex": 1
},
{
"id": "z2-ds-none",
"kind": "ds",
"zone": "github.com",
"label": "No DS",
"status": "unsigned",
"row": 0,
"zoneIndex": 2
},
{
"id": "z2-rr-SOA",
"kind": "rr",
"zone": "github.com",
"label": "SOA",
"status": "skipped",
"row": 1,
"zoneIndex": 2
}
],
"edges": [
{
"from": "z0-ksk-20326",
"to": "z0-zsk-8763",
"kind": "signs",
"status": "ok"
},
{
"from": "z1-ds-19718",
"to": "z1-ksk-19718",
"kind": "digest",
"status": "ok"
},
{
"from": "z1-ksk-19718",
"to": "z1-zsk-65344",
"kind": "signs",
"status": "ok"
},
{
"from": "z0-zsk-8763",
"to": "z1-ds-19718",
"kind": "delegates",
"status": "ok"
},
{
"from": "z1-zsk-65344",
"to": "z2-ds-none",
"kind": "delegates",
"status": "unsigned"
},
{
"from": "z2-ds-none",
"to": "z2-rr-SOA",
"kind": "signs",
"status": "skipped"
}
],
"folded": 0
}
}More in DNS · Health checks
Next step
- DNS traceFollow the lookup from the root to see where it breaksCheck www.visualstudio.github.com in DNS trace
- DNS health checkAre the name servers and records healthy?Check www.visualstudio.github.com in DNS health check
- DNS lookupRead the raw DS and DNSKEY recordsCheck www.visualstudio.github.com in DNS lookup
How to read the graph
Each column is a zone, from the root on the left to the name you typed on the right. On a narrow screen the zones run top to bottom instead. Keys sit inside their zone, a DS record joins a parent to its child and a line means a signature or a digest that was checked.
- Thick outline: a key signing key (KSK), the key a DS record points at.
- Rounded pill: a DS record, held by the parent zone.
- Dashed outline: something that is unsigned or was not checked because the chain broke above it.
- Warning colour with a cross: the link that fails, labelled with what is wrong.
The graph never relies on colour alone. Every node carries its key tag, and every line has the same meaning as its dash pattern.
The same check in words
The graph is a picture of the same data the DNSSEC checker uses, so a result here and on the checker always agree. Under the graph the chain of trust is listed step by step: the zone, its keys, the DS that joins it to its parent, the signature windows and the servers asked. That list is what a screen reader reads, and it works without JavaScript.
With JavaScript on, hovering or focusing a step in the list highlights its keys in the graph and says what they do. Tapping a key in the graph does the same on a phone.
Long chains and many keys
A name such as a.b.example.co.uk crosses five zones, and a zone in the middle of a key rollover publishes two key signing keys and two DS records. The graph keeps the keys on the path to the answer and folds the rest into a "more keys" node once there are more than 40 nodes. The step list is never folded.
The layout is fixed so the graph reads the same every time. There is no pan or zoom to learn. To work with the data yourself, copy the graph as JSON from the links under the result, or ask for it from the DNSSEC checker API or MCP tool.
If the domain is not signed
An unsigned domain draws a short graph: the root, the top-level domain and a zone with no DS record. That is a choice and not a fault. To turn DNSSEC on, ask your DNS provider to sign the zone, then add the DS record it gives you at your registrar.
Afterwards, draw the graph again. A signed zone with a DS that matches a key shows solid lines from the root down to the answer. For a closer look at the servers, see the DNS trace.
Questions people ask
Is the graph different from the checker?
No. It is the same data drawn another way, so a result here and on the checker always agree. The checker leads with the verdict and the steps, and this page leads with the picture.
Can I move or zoom the graph?
No. The layout is fixed so it reads the same every time and works without a pointer or JavaScript. The step list under it carries every detail as text.
What do the dashed nodes mean?
Dashed means unsigned, or not checked because a link above it failed. A dashed node is never a pass, and every dashed node has a word for it in the step list.
Why is there a node that says "more keys"?
Past 40 nodes the graph keeps the keys on the path to the answer and folds the others into one node so it stays readable. The step list shows every key.
Can I download the graph?
You can copy the nodes and edges as JSON. The same structure comes back from the API and from the MCP tool, so a script or an assistant can draw it too.
Does it work on a phone?
Yes. On a narrow screen the zones run from top to bottom, and tapping a key shows what it does. The step list works the same as on a wide screen.
Use it from AI, the API or the command line
Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is dnssec_check. Please be kind to the rate limits.
curl "https://lookupowl.com/api/v1/tools/dnssec-check?q=cloudflare.com"claude mcp add --transport http lookupowl https://lookupowl.com/mcp