DNS health checker
Run a full DNS health report for a domain and get a plain list of what to change, worst problem first.
Results for staging-d.blogger.corp.google.com
- staging-d.blogger.corp.google.com is not a zone of its own, so we checked google.com, the zone that holds it.
DNS health: Good, with things to fix
4 warnings. The most important: SOA serials differ between servers.
1023587894 on ns2.google.com, 1022693303 on ns1.google.com, 1022693303 on ns3.google.com, 1023587894 on ns4.google.com. A server with a lower serial may have stopped copying the zone.
- DelegationPass9 pass
- NameserversPass6 pass, 1 info
- SOAWarning4 warnings, 3 pass
- DNSSECInfoNot signed
- MailPass10 pass, 1 info
- Web and IPv6Pass5 pass
- SecurityPass3 pass
The level is the worst section result. Not signed and no CAA are choices, so they never lower it. A check we couldn't run is never counted as a pass.
Fix first
- SOA serials differ between serversCheck zone transfers (or your provider's sync) to the servers with the lower serial.See the row
- The SOA refresh is out of the usual rangeUse a refresh between 20 minutes and a day, for example 7200.See the row
- The SOA retry is out of the usual rangeUse a retry between 2 minutes and 4 hours, and lower than the refresh.See the row
SOA4 warnings, 3 pass
WarningSOA serials differ between servers
soa-serial-syncRFC 1912 2.21023587894 on ns2.google.com, 1022693303 on ns1.google.com, 1022693303 on ns3.google.com, 1023587894 on ns4.google.com. A server with a lower serial may have stopped copying the zone.
About: ns1.google.com, ns3.google.com
What to do: Check zone transfers (or your provider's sync) to the servers with the lower serial.
WarningThe SOA refresh is out of the usual range
soa-refreshRFC 1912 2.2Refresh is 900 seconds. The usual range is 1200 to 86400 seconds.
What to do: Use a refresh between 20 minutes and a day, for example 7200.
WarningThe SOA retry is out of the usual range
soa-retryRFC 1912 2.2Retry is 900 seconds, not lower than the refresh of 900. A retry should be shorter than a refresh.
What to do: Use a retry between 2 minutes and 4 hours, and lower than the refresh.
WarningThe SOA expire is out of the usual range
soa-expireRFC 1912 2.2Expire is 1800 seconds. The usual range is 604800 to 6048000 seconds.
What to do: Use an expire between one and ten weeks, for example 1209600.
Pass3 checks passedShow
- The zone has an SOA record
soa-presentRFC 1035 3.3.13 - The SOA contact looks like an address
soa-rname-validRFC 1035 3.3.13 - The SOA negative TTL (minimum) is in range
soa-minimumRFC 2308 5
Delegation9 pass
Pass9 checks passedShow
- The parent zone answers with a delegation
parent-answersRFC 1034 4.2.2 - At least one name server answers for the zone
ns-any-answersRFC 1034 4.2.1 - There are at least two name servers
ns-redundancyRFC 2182 5 - The parent and the zone list the same name servers
ns-parent-child-matchRFC 1034 4.2.2 - Every name server lists the same NS records
ns-child-consistentRFC 1034 4.2.2 - Glue is published for the name servers inside the zone
glue-completeRFC 9471 - Every name server name has an address
ns-resolveRFC 1034 3.6 - No name server name is an alias
ns-no-cnameRFC 2181 10.3 - No CNAME at the apex
apex-no-cnameRFC 1034 3.6.2
Walk the delegation step by step (delegation check for google.com)
Nameservers6 pass, 1 info
InfoName servers are in one network
ns-network-diversityRFC 2182 3.1All 4 name servers belong to AS15169. That is common and usually fine; a second provider protects against an outage at one.
What to do: Add a name server at another provider if you want to survive an outage at this one.
Pass6 checks passedShow
- Every name server answers as an authority
lame-delegationRFC 1912 2.8 - Every name server replies
ns-unreachableRFC 2182 3.1 - Every name server has an IPv4 address
ns-has-ipv4RFC 3901 3 - Every name server address is public
ns-address-publicRFC 6890 - Every name server supports EDNS
ns-edns-supportRFC 6891 - Name servers answer quickly
ns-latencyRFC 1035 7
| Server | Addresses | Authoritative | SOA serial | TCP 53 | EDNS | Time |
|---|---|---|---|---|---|---|
| ns1.google.com |
| Yes | 1022693303 Different | Yes | Yes | 12 ms |
| ns3.google.com |
| Yes | 1022693303 Different | Yes | Yes | 11 ms |
| ns2.google.com |
| Yes | 1023587894 | Yes | Yes | 25 ms |
| ns4.google.com |
| Yes | 1023587894 | Yes | Yes | 5 ms |
DNSSECNot signed
InfoNot signed with DNSSEC
dnssec-signedRFC 4033 2google.com has no DS record at its parent. A choice, not a fault: it is never counted against the level.
What to do: If you want it, turn on DNSSEC at your DNS provider and then add the DS record it gives you at your registrar.
Dig into the DNSSEC section (DNSSEC check)
Mail10 pass, 1 info
InfoThere is a single mail server
mx-redundancyRFC 5321 5.1Only smtp.google.com is listed. Many providers publish several names behind one service, so this may be fine.
What to do: Add a second MX host if your provider offers one.
Pass10 checks passedShow
- The domain has 1 MX record
mx-presentRFC 5321 5.1 - No MX host is an alias
mx-not-cnameRFC 2181 10.3 - Every MX host has an address
mx-has-addressRFC 5321 5.1 - No MX host is an IP address
mx-not-ipRFC 5321 5.1 - A mail server has an IPv6 address
mx-ipv6RFC 3596 - The domain publishes one SPF record
spf-presentRFC 7208 3 - The SPF record parses
spf-validRFC 7208 4.6 - The SPF record ends with a policy
spf-policyRFC 7208 5.1 - The domain publishes a DMARC record
dmarc-presentRFC 7489 6.1 - DMARC enforces a policy
dmarc-policyRFC 7489 6.3
Check SPF, DKIM and DMARC for google.com (Email health check)
Web and IPv65 pass
Pass5 checks passedShow
- The apex has an address
apex-addressRFC 1034 3.6 - The apex has an IPv6 address
apex-ipv6RFC 3596 - www resolves
www-resolvesRFC 1034 3.6 - Every name server has an IPv6 address
ns-has-aaaaRFC 3901 - Name servers answer over IPv6
ns-answers-v6RFC 3901
Check IPv6 readiness for google.com (IPv6 readiness)
Security3 pass
Pass3 checks passedShow
- The domain has a CAA record
caa-presentRFC 8659 - No name server is an open resolver
open-recursionRFC 5358 - TCP port 53 is open
tcp-53RFC 7766
- Copy reportPlain text, problems first, for a ticket.
- Copy summary for an AIOne paragraph with the check ids.
Structured result (JSON) · 18 KB
{
"domain": "staging-d.blogger.corp.google.com",
"zone": "google.com",
"outcome": "report",
"depth": "standard",
"checkedAt": "2026-11-17T23:41:26.519Z",
"unfinished": [],
"level": "good-with-fixes",
"counts": {
"pass": 36,
"info": 3,
"warn": 4,
"fail": 0,
"skipped": 0,
"unknown": 0,
"total": 43
},
"summary": "google.com (the zone that holds staging-d.blogger.corp.google.com) has 4 warnings. The most important: SOA serials differ between servers. 1023587894 on ns2.google.com, 1022693303 on ns1.google.com, 1022693303 on ns3.google.com, 1023587894 on ns4.google.com. A server with a lower serial may have stopped copying the zone.",
"topFixes": [
{
"checkId": "soa-serial-sync",
"title": "SOA serials differ between servers",
"text": "Check zone transfers (or your provider's sync) to the servers with the lower serial."
},
{
"checkId": "soa-refresh",
"title": "The SOA refresh is out of the usual range",
"text": "Use a refresh between 20 minutes and a day, for example 7200."
},
{
"checkId": "soa-retry",
"title": "The SOA retry is out of the usual range",
"text": "Use a retry between 2 minutes and 4 hours, and lower than the refresh."
}
],
"sections": [
{
"id": "delegation",
"title": "Delegation",
"counts": {
"pass": 9,
"info": 0,
"warn": 0,
"fail": 0,
"skipped": 0,
"unknown": 0
},
"checks": [
{
"id": "parent-answers",
"level": "pass",
"title": "The parent zone answers with a delegation",
"evidence": "com answered from l.gtld-servers.net with 4 name servers: ns2.google.com, ns1.google.com, ns3.google.com, ns4.google.com.",
"rfc": "RFC 1034 4.2.2",
"fix": null,
"servers": null
},
{
"id": "ns-any-answers",
"level": "pass",
"title": "At least one name server answers for the zone",
"evidence": "4 name servers answered as an authority.",
"rfc": "RFC 1034 4.2.1",
"fix": null,
"servers": null
},
{
"id": "ns-redundancy",
"level": "pass",
"title": "There are at least two name servers",
"evidence": "4 name servers are listed: ns2.google.com, ns1.google.com, ns3.google.com, ns4.google.com.",
"rfc": "RFC 2182 5",
"fix": null,
"servers": null
},
{
"id": "ns-parent-child-match",
"level": "pass",
"title": "The parent and the zone list the same name servers",
"evidence": "com lists ns2.google.com, ns1.google.com, ns3.google.com, ns4.google.com. The zone lists the same.",
"rfc": "RFC 1034 4.2.2",
"fix": null,
"servers": null
},
{
"id": "ns-child-consistent",
"level": "pass",
"title": "Every name server lists the same NS records",
"evidence": "4 servers agree.",
"rfc": "RFC 1034 4.2.2",
"fix": null,
"servers": null
},
{
"id": "glue-complete",
"level": "pass",
"title": "Glue is published for the name servers inside the zone",
"evidence": "ns2.google.com, ns1.google.com, ns3.google.com, ns4.google.com are inside google.com and the registry sends addresses for them.",
"rfc": "RFC 9471",
"fix": null,
"servers": null
},
{
"id": "ns-resolve",
"level": "pass",
"title": "Every name server name has an address",
"evidence": "4 names resolved to at least one address.",
"rfc": "RFC 1034 3.6",
"fix": null,
"servers": null
},
{
"id": "ns-no-cname",
"level": "pass",
"title": "No name server name is an alias",
"evidence": "Every name server name points straight at addresses.",
"rfc": "RFC 2181 10.3",
"fix": null,
"servers": null
},
{
"id": "apex-no-cname",
"level": "pass",
"title": "No CNAME at the apex",
"evidence": "google.com has ordinary records at its top, not an alias.",
"rfc": "RFC 1034 3.6.2",
"fix": null,
"servers": null
}
]
},
{
"id": "nameservers",
"title": "Nameservers",
"counts": {
"pass": 6,
"info": 1,
"warn": 0,
"fail": 0,
"skipped": 0,
"unknown": 0
},
"checks": [
{
"id": "lame-delegation",
"level": "pass",
"title": "Every name server answers as an authority",
"evidence": "4 name servers answered for google.com with the authoritative flag set.",
"rfc": "RFC 1912 2.8",
"fix": null,
"servers": null
},
{
"id": "ns-unreachable",
"level": "pass",
"title": "Every name server replies",
"evidence": "No server stayed silent.",
"rfc": "RFC 2182 3.1",
"fix": null,
"servers": null
},
{
"id": "ns-network-diversity",
"level": "info",
"title": "Name servers are in one network",
"evidence": "All 4 name servers belong to AS15169. That is common and usually fine; a second provider protects against an outage at one.",
"rfc": "RFC 2182 3.1",
"fix": {
"text": "Add a name server at another provider if you want to survive an outage at this one.",
"snippet": null
},
"servers": null
},
{
"id": "ns-has-ipv4",
"level": "pass",
"title": "Every name server has an IPv4 address",
"evidence": "Resolvers on IPv4-only networks can reach all of them.",
"rfc": "RFC 3901 3",
"fix": null,
"servers": null
},
{
"id": "ns-address-public",
"level": "pass",
"title": "Every name server address is public",
"evidence": "No private or reserved address is listed.",
"rfc": "RFC 6890",
"fix": null,
"servers": null
},
{
"id": "ns-edns-support",
"level": "pass",
"title": "Every name server supports EDNS",
"evidence": "Each reply carried an EDNS record.",
"rfc": "RFC 6891",
"fix": null,
"servers": null
},
{
"id": "ns-latency",
"level": "pass",
"title": "Name servers answer quickly",
"evidence": "Fastest 5 ms, slowest 25 ms, from our server.",
"rfc": "RFC 1035 7",
"fix": null,
"servers": null
}
]
},
{
"id": "soa",
"title": "SOA",
"counts": {
"pass": 3,
"info": 0,
"warn": 4,
"fail": 0,
"skipped": 0,
"unknown": 0
},
"checks": [
{
"id": "soa-present",
"level": "pass",
"title": "The zone has an SOA record",
"evidence": "Primary ns1.google.com, serial 1023587894, from 4 servers.",
"rfc": "RFC 1035 3.3.13",
"fix": null,
"servers": null
},
{
"id": "soa-serial-sync",
"level": "warn",
"title": "SOA serials differ between servers",
"evidence": "1023587894 on ns2.google.com, 1022693303 on ns1.google.com, 1022693303 on ns3.google.com, 1023587894 on ns4.google.com. A server with a lower serial may have stopped copying the zone.",
"rfc": "RFC 1912 2.2",
"fix": {
"text": "Check zone transfers (or your provider's sync) to the servers with the lower serial.",
"snippet": null
},
"servers": [
"ns1.google.com",
"ns3.google.com"
]
},
{
"id": "soa-rname-valid",
"level": "pass",
"title": "The SOA contact looks like an address",
"evidence": "The contact is [email protected].",
"rfc": "RFC 1035 3.3.13",
"fix": null,
"servers": null
},
{
"id": "soa-refresh",
"level": "warn",
"title": "The SOA refresh is out of the usual range",
"evidence": "Refresh is 900 seconds. The usual range is 1200 to 86400 seconds.",
"rfc": "RFC 1912 2.2",
"fix": {
"text": "Use a refresh between 20 minutes and a day, for example 7200.",
"snippet": null
},
"servers": null
},
{
"id": "soa-retry",
"level": "warn",
"title": "The SOA retry is out of the usual range",
"evidence": "Retry is 900 seconds, not lower than the refresh of 900. A retry should be shorter than a refresh.",
"rfc": "RFC 1912 2.2",
"fix": {
"text": "Use a retry between 2 minutes and 4 hours, and lower than the refresh.",
"snippet": null
},
"servers": null
},
{
"id": "soa-expire",
"level": "warn",
"title": "The SOA expire is out of the usual range",
"evidence": "Expire is 1800 seconds. The usual range is 604800 to 6048000 seconds.",
"rfc": "RFC 1912 2.2",
"fix": {
"text": "Use an expire between one and ten weeks, for example 1209600.",
"snippet": null
},
"servers": null
},
{
"id": "soa-minimum",
"level": "pass",
"title": "The SOA negative TTL (minimum) is in range",
"evidence": "Negative TTL (minimum) is 60 seconds (1 minute).",
"rfc": "RFC 2308 5",
"fix": null,
"servers": null
}
]
},
{
"id": "dnssec",
"title": "DNSSEC",
"counts": {
"pass": 0,
"info": 1,
"warn": 0,
"fail": 0,
"skipped": 0,
"unknown": 0
},
"checks": [
{
"id": "dnssec-signed",
"level": "info",
"title": "Not signed with DNSSEC",
"evidence": "google.com has no DS record at its parent. A choice, not a fault: it is never counted against the level.",
"rfc": "RFC 4033 2",
"fix": {
"text": "If you want it, turn on DNSSEC at your DNS provider and then add the DS record it gives you at your registrar.",
"snippet": null
},
"servers": null
}
]
},
{
"id": "mail",
"title": "Mail",
"counts": {
"pass": 10,
"info": 1,
"warn": 0,
"fail": 0,
"skipped": 0,
"unknown": 0
},
"checks": [
{
"id": "mx-present",
"level": "pass",
"title": "The domain has 1 MX record",
"evidence": "10 smtp.google.com.",
"rfc": "RFC 5321 5.1",
"fix": null,
"servers": null
},
{
"id": "mx-not-cname",
"level": "pass",
"title": "No MX host is an alias",
"evidence": "Every MX host has addresses of its own.",
"rfc": "RFC 2181 10.3",
"fix": null,
"servers": null
},
{
"id": "mx-has-address",
"level": "pass",
"title": "Every MX host has an address",
"evidence": "1 MX host resolves to at least one address.",
"rfc": "RFC 5321 5.1",
"fix": null,
"servers": null
},
{
"id": "mx-not-ip",
"level": "pass",
"title": "No MX host is an IP address",
"evidence": "Every MX holds a host name.",
"rfc": "RFC 5321 5.1",
"fix": null,
"servers": null
},
{
"id": "mx-redundancy",
"level": "info",
"title": "There is a single mail server",
"evidence": "Only smtp.google.com is listed. Many providers publish several names behind one service, so this may be fine.",
"rfc": "RFC 5321 5.1",
"fix": {
"text": "Add a second MX host if your provider offers one.",
"snippet": null
},
"servers": null
},
{
"id": "mx-ipv6",
"level": "pass",
"title": "A mail server has an IPv6 address",
"evidence": "At least one MX host can be reached over IPv6.",
"rfc": "RFC 3596",
"fix": null,
"servers": null
},
{
"id": "spf-present",
"level": "pass",
"title": "The domain publishes one SPF record",
"evidence": "v=spf1 include:_spf.google.com ~all",
"rfc": "RFC 7208 3",
"fix": null,
"servers": null
},
{
"id": "spf-valid",
"level": "pass",
"title": "The SPF record parses",
"evidence": "No syntax errors.",
"rfc": "RFC 7208 4.6",
"fix": null,
"servers": null
},
{
"id": "spf-policy",
"level": "pass",
"title": "The SPF record ends with a policy",
"evidence": "It ends with ~all.",
"rfc": "RFC 7208 5.1",
"fix": null,
"servers": null
},
{
"id": "dmarc-present",
"level": "pass",
"title": "The domain publishes a DMARC record",
"evidence": "v=DMARC1; p=reject; rua=mailto:[email protected]",
"rfc": "RFC 7489 6.1",
"fix": null,
"servers": null
},
{
"id": "dmarc-policy",
"level": "pass",
"title": "DMARC enforces a policy",
"evidence": "The policy is p=reject.",
"rfc": "RFC 7489 6.3",
"fix": null,
"servers": null
}
]
},
{
"id": "web",
"title": "Web and IPv6",
"counts": {
"pass": 5,
"info": 0,
"warn": 0,
"fail": 0,
"skipped": 0,
"unknown": 0
},
"checks": [
{
"id": "apex-address",
"level": "pass",
"title": "The apex has an address",
"evidence": "google.com: 142.251.39.206, 2a00:1450:4007:810::200e.",
"rfc": "RFC 1034 3.6",
"fix": null,
"servers": null
},
{
"id": "apex-ipv6",
"level": "pass",
"title": "The apex has an IPv6 address",
"evidence": "google.com answers on IPv6 too: 2a00:1450:4007:810::200e.",
"rfc": "RFC 3596",
"fix": null,
"servers": null
},
{
"id": "www-resolves",
"level": "pass",
"title": "www resolves",
"evidence": "www.google.com and has 142.251.156.119, 142.251.150.119, 142.251.155.119 and 13 more.",
"rfc": "RFC 1034 3.6",
"fix": null,
"servers": null
},
{
"id": "ns-has-aaaa",
"level": "pass",
"title": "Every name server has an IPv6 address",
"evidence": "4 name servers can be reached over IPv6.",
"rfc": "RFC 3901",
"fix": null,
"servers": null
},
{
"id": "ns-answers-v6",
"level": "pass",
"title": "Name servers answer over IPv6",
"evidence": "4 name servers answered on their IPv6 addresses.",
"rfc": "RFC 3901",
"fix": null,
"servers": null
}
]
},
{
"id": "security",
"title": "Security",
"counts": {
"pass": 3,
"info": 0,
"warn": 0,
"fail": 0,
"skipped": 0,
"unknown": 0
},
"checks": [
{
"id": "caa-present",
"level": "pass",
"title": "The domain has a CAA record",
"evidence": "Only pki.goog may issue certificates.",
"rfc": "RFC 8659",
"fix": null,
"servers": null
},
{
"id": "open-recursion",
"level": "pass",
"title": "No name server is an open resolver",
"evidence": "We asked 4 servers for a name outside the zone and none resolved it for us.",
"rfc": "RFC 5358",
"fix": null,
"servers": null
},
{
"id": "tcp-53",
"level": "pass",
"title": "TCP port 53 is open",
"evidence": "4 servers answered over TCP.",
"rfc": "RFC 7766",
"fix": null,
"servers": null
}
]
}
],
"nameservers": [
{
"host": "ns2.google.com",
"v4": [
"216.239.34.10"
],
"v6": [
"2001:4860:4802:34::a"
],
"status": "ok",
"authoritative": true,
"soaSerial": 1023587894,
"tcp": true,
"edns": true,
"recursion": false,
"ms": 25
},
{
"host": "ns1.google.com",
"v4": [
"216.239.32.10"
],
"v6": [
"2001:4860:4802:32::a"
],
"status": "ok",
"authoritative": true,
"soaSerial": 1022693303,
"tcp": true,
"edns": true,
"recursion": false,
"ms": 12
},
{
"host": "ns3.google.com",
"v4": [
"216.239.36.10"
],
"v6": [
"2001:4860:4802:36::a"
],
"status": "ok",
"authoritative": true,
"soaSerial": 1022693303,
"tcp": true,
"edns": true,
"recursion": false,
"ms": 11
},
{
"host": "ns4.google.com",
"v4": [
"216.239.38.10"
],
"v6": [
"2001:4860:4802:38::a"
],
"status": "ok",
"authoritative": true,
"soaSerial": 1023587894,
"tcp": true,
"edns": true,
"recursion": false,
"ms": 5
}
],
"dnssec": {
"verdict": "insecure",
"link": "/dnssec-check?name=google.com"
},
"mail": {
"mx": 1,
"spf": "found",
"dmarc": "found",
"link": "/email-health-check?domain=google.com"
},
"previous": null
}More in DNS · Health checks
Next step
- DNSSEC checkIs the zone signed, and does the chain hold?Open in DNSSEC check
- Email health checkNow the mail recordsOpen in Email health check
- DNS traceSee the delegation from the rootOpen in DNS trace
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