DNS health checker
Run a full DNS health report for a domain and get a plain list of what to change, worst problem first.
More in DNS · Health checks
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.
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 |
| 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. For SPF, DKIM and DMARC in detail use the 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
- 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.
- Open the rowEach 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.
- Change it at the right placeName 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.
- Run it againResolvers 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. To see whether a change has reached resolvers around the world, use the DNS propagation checker.
Questions people ask
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.
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 dns_health. Please be kind to the rate limits.
curl "https://lookupowl.com/api/v1/tools/dns-health?q=lookupowl.com"claude mcp add --transport http lookupowl https://lookupowl.com/mcp