# DNSSEC Checker and Chain Visualizer

Validate the DNSSEC chain of trust from the IANA root key down to a name (RFC 4035), asking each authoritative server directly. Returns a verdict (secure, insecure, bogus, indeterminate), one step per zone with keys, DS match, signature windows and servers, issues with fixes, how Cloudflare, Google and Quad9 see the name (AD bit, extended errors) and a graph of nodes and edges. An unsigned name is insecure by choice, not a fault. Optional trust anchor and up to 4 servers to test before you upload a DS. Public names only.

**Not for:** Reading a raw DS or DNSKEY record (use dns_lookup).

- Tool id: `dnssec-check`
- Category: dns
- Execution: network
- MCP tool `dnssec_check` at https://lookupowl.com/mcp
- REST `GET https://lookupowl.com/api/v1/tools/dnssec-check` (or POST a JSON body)
- OpenAPI: https://lookupowl.com/api/openapi.json

## Input

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `name` | string | yes |  | A domain name, or any name inside it, such as example.com. We find the zone for you. A TLD or the root (".") is allowed. min length 1, max length 253 |
| `type` | "SOA" \| "A" \| "AAAA" \| "MX" \| "TXT" \| "NS" \| "CNAME" \| "DNSKEY" \| "DS" \| "CAA" | no | `"SOA"` | The record type whose signed answer is checked last. The chain of trust is the same for every type. |
| `trustAnchor` | string | no |  | A DS record in presentation format to start from instead of the IANA root key. Its owner is "." or the zone of the name. max length 512 |
| `servers` | string[] | no |  | Up to 4 public IPs or host names to ask instead of the zone's own name servers. max 4 items |
| `predelegation` | boolean | no | `false` | Judge the zone on the servers given and answer "ready to add the DS", not a verdict on the live chain. Needs servers. |

## Output

Results are wrapped in an envelope: `tool`, `version`, `requestId`, `data`, `summary`, `meta` (cache status, timing), `permalink`. `data` has these fields:

| Field | Type | Description |
|---|---|---|
| `name` | string |  |
| `zone` | string |  |
| `type` | string |  |
| `mode` | "live" \| "predelegation" | predelegation: the zone was judged on the servers given, before a DS exists. |
| `verdict` | "secure" \| "insecure" \| "bogus" \| "indeterminate" |  |
| `state` | "secure" \| "one-server" \| "anchor" \| "zone-above" \| "unsigned" \| "unsigned-tld" \| "not-linked" \| "ds-no-match" \| "ds-left-behind" \| "sig-expired" \| "sig-not-yet-valid" \| "sig-invalid" \| "alg-mismatch" \| "chain-broken" \| "nxdomain-proved" \| "not-delegated" \| "could-not-tell" \| "ready" \| "not-ready" | The case behind the verdict, for wording. |
| `verdictText` | string |  |
| `explain` | string |  |
| `anchor` | object |  |
| `chain` | object[] |  |
| `denial` | object |  |
| `issues` | object[] |  |
| `extras` | object |  |
| `rdap` | object |  |
| `resolvers` | object[] |  |
| `graph` | object |  |

## Examples

### A signed zone with a valid chain

```json
{"name":"cloudflare.com","type":"SOA","predelegation":false}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/dnssec-check?name=cloudflare.com&predelegation=false&type=SOA'
```

Web page: https://lookupowl.com/dnssec-check?q=cloudflare.com

### An unsigned zone (a choice, not a fault)

```json
{"name":"github.com","type":"SOA","predelegation":false}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/dnssec-check?name=github.com&predelegation=false&type=SOA'
```

Web page: https://lookupowl.com/dnssec-check?q=github.com

### Broken on purpose: a DS that matches no key

```json
{"name":"dnssec-failed.org","type":"SOA","predelegation":false}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/dnssec-check?name=dnssec-failed.org&predelegation=false&type=SOA'
```

Web page: https://lookupowl.com/dnssec-check?q=dnssec-failed.org

### lookupowl.com

```json
{"name":"lookupowl.com","type":"SOA","predelegation":false}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/dnssec-check?name=lookupowl.com&predelegation=false&type=SOA'
```

Web page: https://lookupowl.com/dnssec-check?q=lookupowl.com

## Web pages

- https://lookupowl.com/dnssec-check
- https://lookupowl.com/dnssec-visualizer

## Limits and caching

- Cost: 6 units for a live lookup, 1 unit for a cached one. Budgets are per network and published in the `RateLimit` response headers.
- Cache: the lifetime follows the data (for DNS, the record TTL, within a few minutes). Add `fresh=true` (MCP argument or query parameter) to look again; it costs 3 units per unit and is limited to 10 per hour.
- Timeout: 20 s.

## Related tools

- [DNS Lookup](https://lookupowl.com/tools/dns-lookup.md): Look up A, AAAA, MX, NS, TXT, CNAME, SOA, CAA, DS and DNSKEY records from a public resolver or the authoritative nameserver.
- [DNS Trace and Delegation Checker](https://lookupowl.com/tools/dns-trace.md): Follow a DNS lookup from the root servers down to the answer, or check a domain's delegation, glue and new name servers before you switch.
- [DNS Health Checker](https://lookupowl.com/tools/dns-health.md): A full DNS health report for a domain: delegation, name servers, SOA, DNSSEC, mail records, IPv6 and security, with the fix for each problem.
- [DNS Propagation Checker](https://lookupowl.com/tools/dns-propagation.md): Check whether a DNS change has reached public resolvers around the world and which caches are still stale.
- [Domain Report: Registration, DNS, Web, Hosting and Email](https://lookupowl.com/tools/domain-report.md): One scored report on a domain: registration, DNS, certificate and security headers, hosting, SPF, DMARC, DKIM and blocklists.
- [WHOIS Lookup](https://lookupowl.com/tools/whois-lookup.md): Registrar, creation and expiry dates, status codes, nameservers and DNSSEC for any domain, from RDAP with WHOIS fallback.

## Guide: DNSSEC checker

See whether a domain's DNSSEC chain of trust holds from the root down, and which link breaks when it does not.

### What the DNSSEC check looks at

DNSSEC signs DNS answers so a resolver can tell they were not changed on the way. The signatures only help when every link holds: the root vouches for the top-level domain, the top-level domain vouches for your zone with a DS record, and your zone signs its own records.

This page walks that chain one zone at a time and asks each authoritative server directly. It starts from the IANA root key, checks the DS record at each parent against the keys the child publishes, checks the signature on every key set, and then checks the signature on the answer for the record type you chose.

- **Secure:** every link holds, from the root to the answer.
- **Insecure:** the parent says the zone is not signed. Most domains are in this state, and it is a choice, not a fault.
- **Broken:** a link fails, so resolvers that validate refuse the name. The page names the link and the fix.
- **Could not tell:** we could not finish, for example because no server answered or the zone uses an algorithm we cannot verify here.

### How to read the result

The chain of trust is a list of cards from the root to the answer. Each card shows the keys the zone publishes (a key signing key, KSK, and a zone signing key, ZSK), the DS record that joins it to its parent, and a bar for how long its signatures live and how much of that is left.

A signature that lives only a day or two is not a warning. Some providers sign on the fly and renew all the time. We warn only when a signature that lives a week or more has less than a fifth of its life left, or when a signature has already expired.

Below the chain, a table shows what Cloudflare, Google and Quad9 make of the name: whether they set the AD bit (authenticated data) and what error they give. Resolvers describe the same failure in different words, so our own finding comes first.

### Fixing a broken chain

The most common outage is a DS record at the registrar that no longer matches any key in the zone. It follows a move to a new DNS provider, a key rollover that went wrong, or switching signing off without removing the DS.

1. **Find the failing link**: The card marked "Broken here" shows the DS record next to the keys the zone really publishes, and says why they do not match.
2. **Choose the fix**: Replace the DS at your registrar with the one for the key the zone uses now, remove the DS if you turned DNSSEC off, or re-sign with the key the DS points to.
3. **Wait, then check again**: Resolvers keep the old DS until its time to live runs out. Run the check again, and use [DNS propagation](https://lookupowl.com/dns-propagation-checker) to see whether the change has reached everyone.

> **Test before you switch** Turn on "Before I upload a DS" in the options and list the servers of your new provider. We check that each one signs the zone and that the signatures verify, and print the DS to give your registrar. Adding a DS too early is how a working domain stops resolving.

### Turning DNSSEC on

An unsigned domain still works for everyone. Turning DNSSEC on is a decision for the owner, and it needs two parties: the DNS provider signs the zone, and the registrar publishes a DS record at the parent.

1. Switch on signing at the DNS provider that hosts the zone. Providers that sign for you give you a DS record to copy.
2. Add that DS record at your registrar, using the same values: key tag, algorithm, digest type and digest.
3. Run this check. A result of "Secure" means every link holds. Keep the DS in step with the provider whenever you change keys or move the zone.

For the records themselves, use a [DS lookup](https://lookupowl.com/ds-lookup) and a [DNSKEY lookup](https://lookupowl.com/dnskey-lookup). For the rest of a domain, see the [DNS health check](https://lookupowl.com/dns-health-check) and the [DNS trace](https://lookupowl.com/dns-trace).

### Frequently asked questions

**What does insecure mean for a domain?**

It means the domain is not signed with DNSSEC and the parent says so on purpose. Most domains are in this state and it is not an error. Anyone can still look the name up.

**Why do some resolvers fail while others work?**

Resolvers that validate DNSSEC refuse a name whose chain is broken. Resolvers that do not validate still answer, so the problem looks random. The table of public resolvers shows who refuses and why.

**Why does my domain fail on only one name server?**

A stale secondary can serve old signatures that have expired while the others are fine. People whose resolver asks that server get a failure and the rest do not. The server list on the zone card flags it.

**Can I test a new DNS provider before I upload the DS?**

Yes. Turn on "Before I upload a DS" in the options and list up to four servers. We ask only those servers, check the signatures, and print the DS record to give your registrar.

**What is a trust anchor and can I change it?**

A trust anchor is the key a check starts from. We use the IANA root key. In the options you can paste a DS record in presentation format to start from your own, which is useful for testing a zone on its own.

**Which algorithms can you verify?**

RSA with SHA-256 and SHA-512, ECDSA P-256 and P-384 and Ed25519, plus RSA with SHA-1, which we flag as outdated. A zone that uses only something else is reported as could not tell, never as broken.

**Does the check change anything at my registrar or DNS provider?**

No. It only reads public DNS data, asks three public resolvers what they see, and, for a registered domain, reads the registry record to compare its DS data.
