# DNS Health Checker

Check the health of a domain's DNS and say what to change. Runs a catalog of checks in seven sections (delegation, name servers, SOA, DNSSEC, mail, web and IPv6, security), each with a stable id, a level (pass, info, warn, fail or skipped), evidence, an RFC reference and a fix. Returns a level word (healthy, good-with-fixes, needs-attention, not-working), the counts, up to 3 fixes to make first, the name servers with their addresses and serials, and a summary paragraph. depth quick is about 30 checks, standard about 45, deep adds a plain query per server and the zone transfer test. No letter grade. Public domains only.

**Not for:** Reading one record (use dns_lookup) or the DNSSEC chain alone (use dnssec_check).

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

## Input

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `domain` | string | yes |  | A domain name such as example.com. An email address is reduced to its domain. Health checks are for domains, not for a top-level domain. min length 1, max length 320 |
| `depth` | "quick" \| "standard" \| "deep" | no | `"standard"` | quick: about 30 checks in a few seconds. standard: about 45 checks in up to 10 seconds, with the DNSSEC verdict and the security probes. deep: adds a plain query to each name server and the zone transfer test (one request, closed after the first message); slower and limited to 2 a minute. |

## Output

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

| Field | Type | Description |
|---|---|---|
| `domain` | string |  |
| `zone` | string | The zone that was checked. Differs from domain when the name sits inside a parent zone (www.example.com is checked as example.com). |
| `outcome` | "report" \| "not-delegated" \| "no-nameservers" \| "silent" | report: the checks ran. not-delegated: the parent zone says the name does not exist. no-nameservers: no usable name server address. silent: every listed name server stayed silent. |
| `depth` | "quick" \| "standard" \| "deep" |  |
| `checkedAt` | string |  |
| `incomplete` | boolean | True when a section hit the time limit: the level is then marked "not complete" and unfinished lists the checks. |
| `unfinished` | string[] | Ids of the checks that did not finish in time (level unknown). |
| `level` | "healthy" \| "good-with-fixes" \| "needs-attention" \| "not-working" |  |
| `counts` | object |  |
| `summary` | string | One paragraph for people and agents. |
| `topFixes` | object[] | max 3 items |
| `sections` | object[] |  |
| `nameservers` | object[] |  |
| `dnssec` | object |  |
| `mail` | object |  |
| `previous` | object | Always null for now: results are not stored as history. |

## Examples

### A healthy zone at one provider

```json
{"domain":"lookupowl.com","depth":"standard"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/dns-health?depth=standard&domain=lookupowl.com'
```

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

### Eight name servers, unsigned, no AAAA on the apex

```json
{"domain":"github.com","depth":"standard"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/dns-health?depth=standard&domain=github.com'
```

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

### Name servers inside the zone (glue required)

```json
{"domain":"cloudflare.com","depth":"standard"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/dns-health?depth=standard&domain=cloudflare.com'
```

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

### A quick lint of lookupowl.com

```json
{"domain":"lookupowl.com","depth":"quick"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/dns-health?depth=quick&domain=lookupowl.com'
```

Web page: https://lookupowl.com/dns-validation?q=lookupowl.com

### A quick lint of github.com

```json
{"domain":"github.com","depth":"quick"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/dns-health?depth=quick&domain=github.com'
```

Web page: https://lookupowl.com/dns-validation?q=github.com

## Web pages

- https://lookupowl.com/dns-health-check
- https://lookupowl.com/dns-validation

## Limits and caching

- Cost: from 1 unit up, depending on the input (a registry lookup counts every upstream request); 1 unit for a cached result. Budgets are per network and published in the `RateLimit` response headers.
- Cache: results are kept for 600 s. 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: 30 s.

## Related tools

- [DNSSEC Checker and Chain Visualizer](https://lookupowl.com/tools/dnssec-check.md): Check the DNSSEC chain of trust from the root to a name, link by link, and see which link is broken and how to fix it.
- [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 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 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.
- [IPv6 Readiness Checker](https://lookupowl.com/tools/ipv6-readiness.md): Check whether a domain's website, name servers and mail servers can be reached over IPv6, with the fix for each gap.
- [Email Health Checker and Spoofing Test](https://lookupowl.com/tools/email-health.md): Check a domain's whole mail setup in one report: mail servers, SPF, DKIM, DMARC, BIMI, MTA-STS, TLS-RPT and blocklists, with the fixes to make first.
- [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: DNS health checker

Run a full DNS health report for a domain and get a plain list of what to change, worst problem first.

### What the health report covers

Type a domain and the report asks the questions an experienced administrator would ask, all at once. Is the domain delegated to the name servers its owner thinks it is? Do those servers answer, and do they agree with each other? Is the zone's SOA record sane? Is DNSSEC signed and does the chain hold? Do the mail and web records make sense?

A standard report runs about 45 checks in seven sections. Every check has a stable id you can quote in a ticket, such as `lame-delegation` or `soa-serial-sync`, the evidence we saw, the RFC it comes from and, when there is a fix, the sentence or the exact record to use.

> **No grade, on purpose** The result is a level word and counts, never a letter or a score. A letter invites comparing a small blog with a bank, and it would punish choices that are fine, such as an unsigned zone or a single DNS provider.

### How to read the level

The top of the report says one of four things. The level is the worst section result, and a check we could not run is never counted as a pass.

| Level | What it means |
|---|---|
| Healthy | No problem and no warning. Information lines may remain; they are never faults. |
| Good, with things to fix | Nothing is broken, but at least one warning is worth your time. |
| Needs attention | At least one real problem, such as a name server that refuses to answer. |
| Not working | We could not reach any of the name servers, so the rest was skipped. |

Under the level, seven cells show where the problems are. Each cell jumps to its section. Problems open by default, and passing checks fold into one line such as "9 checks passed" so a long green list does not hide the one red row.

### What each section looks at

| Section | What we look at | A problem it finds |
|---|---|---|
| Delegation | The parent zone, the NS records, glue, and aliases | The registry and the zone list different name servers |
| Nameservers | Every address of every name server | One server answers REFUSED for the zone |
| SOA | Serials on every server, the contact and the timers | Two servers hold different zone versions |
| DNSSEC | DS at the parent, keys, signatures | The chain of trust is broken |
| Mail | MX hosts, SPF and DMARC records | An MX points at a CNAME |
| Web and IPv6 | Apex and www addresses, IPv6 on the name servers | No IPv6 address on the apex |
| Security | CAA, open recursion, TCP port 53 | A name server answers recursive questions for anyone |

The DNSSEC and mail sections give a one-line verdict and a link, not a copy of the full tools. For the whole chain use the [DNSSEC checker](https://lookupowl.com/dnssec-check). For SPF, DKIM and DMARC in detail use the [email health check](https://lookupowl.com/email-health-check).

### How the checks run

We start at the root and follow the delegation down to your zone, then ask every listed name server directly, with no cache in between. That is why the report can tell a server that is down from a resolver that is still holding an old answer. The mail and web records come from a public resolver.

- **Standard** takes up to 10 seconds. The page waits for every check and then shows the whole report.
- **Deep** adds a plain query without EDNS to each server and, when TCP works, one zone transfer request that we close after its first message and never store. It is slower and limited to 2 a minute.
- A check that did not finish in time is shown as unknown with the words "Some checks didn't finish", and the level is marked not complete. It is never shown as a pass.
- We only ask the name servers your zone lists, and never more than a few questions a minute of any one server.

### Fixing what the report finds

1. **Start with "Fix first"**: The report lists up to three fixes, failures before warnings and delegation before everything else, because a broken delegation makes the later checks moot.
2. **Open the row**: Each row says what we saw, the RFC behind it and what to do. Where the fix is a record, the record is there to copy.
3. **Change it at the right place**: Name server lists and glue live at your registrar. Everything else lives in your DNS provider. A delegation problem is fixed at the registrar even though the symptom shows in the zone.
4. **Run it again**: Resolvers may keep the old answer until its TTL runs out. The report asks the servers themselves, so it shows the new state straight away.

To see the delegation step by step, use the [DNS trace](https://lookupowl.com/dns-trace). To see whether a change has reached resolvers around the world, use the [DNS propagation checker](https://lookupowl.com/dns-propagation-checker).

### Frequently asked questions

**How long does the report take?**

Up to 10 seconds at standard depth and a few seconds for the quick version. The page says so before the button and waits for every check before it shows the report.

**Why is there no grade or score?**

A letter invites comparison between domains that do different jobs, and it would mark down choices that are fine. The level word and the counts tell you what to fix without that.

**Is an unsigned domain a problem?**

No. DNSSEC is shown as information when it is off and never lowers the level. If it is on and broken, that is a failure, because validating resolvers then refuse to answer for the domain.

**What is a lame delegation?**

A name server that the registry lists for your domain but that does not answer for it as an authority. Resolvers that ask it wait, then try another server, so lookups get slower and sometimes fail.

**Can I type an email address?**

Yes. We use only the part after the @ and do not keep the rest. A name such as www.example.com is checked as the zone that holds it, and an international name is checked in its xn-- form.

**Does the deep check change anything?**

No. It only asks more questions. The zone transfer test sends one request, closes the connection after the first reply and stores nothing from it.

**Can an AI assistant run this?**

Yes. The tool is called dns_health in the MCP server. It returns the level, the counts, up to three fixes, the name servers and a one-paragraph summary, with the same check ids you see here.
