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 vpn-ca.iad.github.com
- vpn-ca.iad.github.com is not a zone of its own, so we checked iad.github.com, the zone that holds it.
DNS health: Good, with things to fix
3 warnings. The most important: no MX record and no address.
iad.github.com has no MX record and no A or AAAA record, so mail to it bounces.
- DelegationPass9 pass
- NameserversPass7 pass
- SOAPass6 pass, 1 info
- DNSSECInfoNot signed
- MailWarning3 warnings
- Web and IPv6Pass2 pass, 2 info
- SecurityPass2 pass, 1 info
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
- No MX record and no addressIf the domain should get mail, add an MX record. If it should not, publish a null MX.See the row
- No SPF recordPublish one TXT record that starts with v=spf1 and lists your senders.See the row
- No DMARC recordPublish a DMARC record, starting with a monitoring policy.See the row
Mail3 warnings
WarningNo MX record and no address
mx-presentRFC 5321 5.1iad.github.com has no MX record and no A or AAAA record, so mail to it bounces.
What to do: If the domain should get mail, add an MX record. If it should not, publish a null MX.
iad.github.com. 3600 IN MX 0 .WarningNo SPF record
spf-presentRFC 7208 3iad.github.com publishes no SPF record, so receivers cannot tell which servers may send its mail.
What to do: Publish one TXT record that starts with v=spf1 and lists your senders.
iad.github.com. 3600 IN TXT "v=spf1 -all"WarningNo DMARC record
dmarc-presentRFC 7489 6.1iad.github.com has no DMARC record. Big mailbox providers now expect one from anyone who sends a lot of mail.
What to do: Publish a DMARC record, starting with a monitoring policy.
_dmarc.iad.github.com. 3600 IN TXT "v=DMARC1; p=none; rua=mailto:[email protected]"Check SPF, DKIM and DMARC for iad.github.com (Email health check)
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 - No glue is needed
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 iad.github.com)
Nameservers7 pass
Pass7 checks passedShow
- Every name server answers as an authority
lame-delegationRFC 1912 2.8 - Every name server replies
ns-unreachableRFC 2182 3.1 - Name servers are spread over more than one network
ns-network-diversityRFC 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 |
|---|---|---|---|---|---|---|
| ns-1114.awsdns-11.org |
| Yes | 1 Different | Yes | Yes | 5 ms |
| ns-1852.awsdns-39.co.uk |
| Yes | 1 Different | Yes | Yes | 11 ms |
| ns-218.awsdns-27.com |
| Yes | 1 Different | Yes | Yes | 9 ms |
| ns-597.awsdns-10.net |
| Yes | 1 Different | Yes | Yes | 4 ms |
| dns1.p01.nsone.net |
| Yes | 1591828468 | Yes | Yes | 5 ms |
| dns2.p01.nsone.net |
| Yes | 1591828468 | Yes | Yes | 6 ms |
| dns3.p01.nsone.net |
| Yes | 1591828468 | Yes | Yes | 7 ms |
| dns4.p01.nsone.net |
| Yes | 1591828468 | Yes | Yes | 6 ms |
SOA6 pass, 1 info
InfoSerials differ between providers
soa-serial-syncRFC 1912 2.21591828468 at nsone, 1 at awsdns, 1 at co. Each provider keeps its own serial, which is normal when a zone is split over more than one provider.
Pass6 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 refresh is in range
soa-refreshRFC 1912 2.2 - The SOA retry is in range
soa-retryRFC 1912 2.2 - The SOA expire is in range
soa-expireRFC 1912 2.2 - The SOA negative TTL (minimum) is in range
soa-minimumRFC 2308 5
DNSSECNot signed
InfoThe parent zone is not signed
dnssec-signedRFC 4035 5github.com is not signed, so iad.github.com cannot be validated whether or not it is signed itself.
Dig into the DNSSEC section (DNSSEC check)
Web and IPv62 pass, 2 info
InfoThe apex has no address
apex-addressRFC 1034 3.6iad.github.com has no A or AAAA record. That is fine for a domain used only for mail; visitors who type it get no website.
Infowww does not resolve
www-resolvesRFC 1034 3.6www.iad.github.com has no address. Visitors who type www in front get an error.
What to do: Add a CNAME for www that points at the apex or your host.
www.iad.github.com. 3600 IN CNAME iad.github.com.Pass2 checks passedShow
- Every name server has an IPv6 address
ns-has-aaaaRFC 3901 - Name servers answer over IPv6
ns-answers-v6RFC 3901
Check IPv6 readiness for iad.github.com (IPv6 readiness)
Security2 pass, 1 info
InfoNo CAA record
caa-presentRFC 8659Any certificate authority may issue for this name. A recommendation, not a fault.
What to do: Add a CAA record for the authority you use.
iad.github.com. 3600 IN CAA 0 issue "letsencrypt.org"Pass2 checks passedShow
- 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) · 17 KB
{
"domain": "vpn-ca.iad.github.com",
"zone": "iad.github.com",
"outcome": "report",
"depth": "standard",
"checkedAt": "2026-11-17T23:29:44.749Z",
"unfinished": [],
"level": "good-with-fixes",
"counts": {
"pass": 26,
"info": 5,
"warn": 3,
"fail": 0,
"skipped": 0,
"unknown": 0,
"total": 34
},
"summary": "iad.github.com (the zone that holds vpn-ca.iad.github.com) has 3 warnings. The most important: no MX record and no address. iad.github.com has no MX record and no A or AAAA record, so mail to it bounces.",
"topFixes": [
{
"checkId": "mx-present",
"title": "No MX record and no address",
"text": "If the domain should get mail, add an MX record. If it should not, publish a null MX."
},
{
"checkId": "spf-present",
"title": "No SPF record",
"text": "Publish one TXT record that starts with v=spf1 and lists your senders."
},
{
"checkId": "dmarc-present",
"title": "No DMARC record",
"text": "Publish a DMARC record, starting with a monitoring policy."
}
],
"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": "github.com answered from ns-1283.awsdns-32.org with 8 name servers: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net, ns-1114.awsdns-11.org, ns-1852.awsdns-39.co.uk and 2 more.",
"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": "8 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": "8 name servers are listed: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net, ns-1114.awsdns-11.org, ns-1852.awsdns-39.co.uk and 2 more.",
"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": "github.com lists dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net, ns-1114.awsdns-11.org, ns-1852.awsdns-39.co.uk and 2 more. 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": "8 servers agree.",
"rfc": "RFC 1034 4.2.2",
"fix": null,
"servers": null
},
{
"id": "glue-complete",
"level": "pass",
"title": "No glue is needed",
"evidence": "No name server is inside iad.github.com, so the registry does not have to publish addresses for them.",
"rfc": "RFC 9471",
"fix": null,
"servers": null
},
{
"id": "ns-resolve",
"level": "pass",
"title": "Every name server name has an address",
"evidence": "8 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": "iad.github.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": 7,
"info": 0,
"warn": 0,
"fail": 0,
"skipped": 0,
"unknown": 0
},
"checks": [
{
"id": "lame-delegation",
"level": "pass",
"title": "Every name server answers as an authority",
"evidence": "8 name servers answered for iad.github.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": "pass",
"title": "Name servers are spread over more than one network",
"evidence": "2 networks: AS62597, AS16509.",
"rfc": "RFC 2182 3.1",
"fix": 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 4 ms, slowest 11 ms, from our server.",
"rfc": "RFC 1035 7",
"fix": null,
"servers": null
}
]
},
{
"id": "soa",
"title": "SOA",
"counts": {
"pass": 6,
"info": 1,
"warn": 0,
"fail": 0,
"skipped": 0,
"unknown": 0
},
"checks": [
{
"id": "soa-present",
"level": "pass",
"title": "The zone has an SOA record",
"evidence": "Primary dns1.p01.nsone.net, serial 1591828468, from 8 servers.",
"rfc": "RFC 1035 3.3.13",
"fix": null,
"servers": null
},
{
"id": "soa-serial-sync",
"level": "info",
"title": "Serials differ between providers",
"evidence": "1591828468 at nsone, 1 at awsdns, 1 at co. Each provider keeps its own serial, which is normal when a zone is split over more than one provider.",
"rfc": "RFC 1912 2.2",
"fix": null,
"servers": null
},
{
"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": "pass",
"title": "The SOA refresh is in range",
"evidence": "Refresh is 43200 seconds (12 hours).",
"rfc": "RFC 1912 2.2",
"fix": null,
"servers": null
},
{
"id": "soa-retry",
"level": "pass",
"title": "The SOA retry is in range",
"evidence": "Retry is 7200 seconds (2 hours).",
"rfc": "RFC 1912 2.2",
"fix": null,
"servers": null
},
{
"id": "soa-expire",
"level": "pass",
"title": "The SOA expire is in range",
"evidence": "Expire is 1209600 seconds (14 days).",
"rfc": "RFC 1912 2.2",
"fix": null,
"servers": null
},
{
"id": "soa-minimum",
"level": "pass",
"title": "The SOA negative TTL (minimum) is in range",
"evidence": "Negative TTL (minimum) is 3600 seconds (1 hour).",
"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": "The parent zone is not signed",
"evidence": "github.com is not signed, so iad.github.com cannot be validated whether or not it is signed itself.",
"rfc": "RFC 4035 5",
"fix": null,
"servers": null
}
]
},
{
"id": "mail",
"title": "Mail",
"counts": {
"pass": 0,
"info": 0,
"warn": 3,
"fail": 0,
"skipped": 0,
"unknown": 0
},
"checks": [
{
"id": "mx-present",
"level": "warn",
"title": "No MX record and no address",
"evidence": "iad.github.com has no MX record and no A or AAAA record, so mail to it bounces.",
"rfc": "RFC 5321 5.1",
"fix": {
"text": "If the domain should get mail, add an MX record. If it should not, publish a null MX.",
"snippet": "iad.github.com. 3600 IN MX 0 ."
},
"servers": null
},
{
"id": "spf-present",
"level": "warn",
"title": "No SPF record",
"evidence": "iad.github.com publishes no SPF record, so receivers cannot tell which servers may send its mail.",
"rfc": "RFC 7208 3",
"fix": {
"text": "Publish one TXT record that starts with v=spf1 and lists your senders.",
"snippet": "iad.github.com. 3600 IN TXT \"v=spf1 -all\""
},
"servers": null
},
{
"id": "dmarc-present",
"level": "warn",
"title": "No DMARC record",
"evidence": "iad.github.com has no DMARC record. Big mailbox providers now expect one from anyone who sends a lot of mail.",
"rfc": "RFC 7489 6.1",
"fix": {
"text": "Publish a DMARC record, starting with a monitoring policy.",
"snippet": "_dmarc.iad.github.com. 3600 IN TXT \"v=DMARC1; p=none; rua=mailto:[email protected]\""
},
"servers": null
}
]
},
{
"id": "web",
"title": "Web and IPv6",
"counts": {
"pass": 2,
"info": 2,
"warn": 0,
"fail": 0,
"skipped": 0,
"unknown": 0
},
"checks": [
{
"id": "apex-address",
"level": "info",
"title": "The apex has no address",
"evidence": "iad.github.com has no A or AAAA record. That is fine for a domain used only for mail; visitors who type it get no website.",
"rfc": "RFC 1034 3.6",
"fix": null,
"servers": null
},
{
"id": "www-resolves",
"level": "info",
"title": "www does not resolve",
"evidence": "www.iad.github.com has no address. Visitors who type www in front get an error.",
"rfc": "RFC 1034 3.6",
"fix": {
"text": "Add a CNAME for www that points at the apex or your host.",
"snippet": "www.iad.github.com. 3600 IN CNAME iad.github.com."
},
"servers": null
},
{
"id": "ns-has-aaaa",
"level": "pass",
"title": "Every name server has an IPv6 address",
"evidence": "8 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": 2,
"info": 1,
"warn": 0,
"fail": 0,
"skipped": 0,
"unknown": 0
},
"checks": [
{
"id": "caa-present",
"level": "info",
"title": "No CAA record",
"evidence": "Any certificate authority may issue for this name. A recommendation, not a fault.",
"rfc": "RFC 8659",
"fix": {
"text": "Add a CAA record for the authority you use.",
"snippet": "iad.github.com. 3600 IN CAA 0 issue \"letsencrypt.org\""
},
"servers": null
},
{
"id": "open-recursion",
"level": "pass",
"title": "No name server is an open resolver",
"evidence": "We asked 8 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": "8 servers answered over TCP.",
"rfc": "RFC 7766",
"fix": null,
"servers": null
}
]
}
],
"nameservers": [
{
"host": "dns1.p01.nsone.net",
"v4": [
"198.51.44.1"
],
"v6": [
"2620:4d:4000:6259:7:1:0:1"
],
"status": "ok",
"authoritative": true,
"soaSerial": 1591828468,
"tcp": true,
"edns": true,
"recursion": false,
"ms": 5
},
{
"host": "dns2.p01.nsone.net",
"v4": [
"198.51.45.1"
],
"v6": [
"2a00:edc0:6259:7:1::2"
],
"status": "ok",
"authoritative": true,
"soaSerial": 1591828468,
"tcp": true,
"edns": true,
"recursion": false,
"ms": 6
},
{
"host": "dns3.p01.nsone.net",
"v4": [
"198.51.44.65"
],
"v6": [
"2620:4d:4000:6259:7:1:0:3"
],
"status": "ok",
"authoritative": true,
"soaSerial": 1591828468,
"tcp": true,
"edns": true,
"recursion": false,
"ms": 7
},
{
"host": "dns4.p01.nsone.net",
"v4": [
"198.51.45.65"
],
"v6": [
"2a00:edc0:6259:7:1::4"
],
"status": "ok",
"authoritative": true,
"soaSerial": 1591828468,
"tcp": true,
"edns": true,
"recursion": false,
"ms": 6
},
{
"host": "ns-1114.awsdns-11.org",
"v4": [
"205.251.196.90"
],
"v6": [
"2600:9000:5304:5a00::1"
],
"status": "ok",
"authoritative": true,
"soaSerial": 1,
"tcp": true,
"edns": true,
"recursion": false,
"ms": 5
},
{
"host": "ns-1852.awsdns-39.co.uk",
"v4": [
"205.251.199.60"
],
"v6": [
"2600:9000:5307:3c00::1"
],
"status": "ok",
"authoritative": true,
"soaSerial": 1,
"tcp": true,
"edns": true,
"recursion": false,
"ms": 11
},
{
"host": "ns-218.awsdns-27.com",
"v4": [
"205.251.192.218"
],
"v6": [
"2600:9000:5300:da00::1"
],
"status": "ok",
"authoritative": true,
"soaSerial": 1,
"tcp": true,
"edns": true,
"recursion": false,
"ms": 9
},
{
"host": "ns-597.awsdns-10.net",
"v4": [
"205.251.194.85"
],
"v6": [
"2600:9000:5302:5500::1"
],
"status": "ok",
"authoritative": true,
"soaSerial": 1,
"tcp": true,
"edns": true,
"recursion": false,
"ms": 4
}
],
"dnssec": {
"verdict": "insecure",
"link": "/dnssec-check?name=iad.github.com"
},
"mail": {
"mx": 0,
"spf": "missing",
"dmarc": "missing",
"link": "/email-health-check?domain=iad.github.com"
},
"previous": null
}More in DNS · Health checks
Next step
- DNSSEC checkIs the zone signed, and does the chain hold?Check vpn-ca.iad.github.com in DNSSEC check
- Email health checkNow the mail recordsCheck vpn-ca.iad.github.com in Email health check
- DNS traceSee the delegation from the rootCheck vpn-ca.iad.github.com 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