Delegation checker
Test whether a domain is delegated correctly, and whether new name servers will work before you switch to them.
Results for lookupowl.com
Delegation
The delegation of lookupowl.com is correct.
The registry, the zone and the registration data agree, glue matches, and all 2 servers answer with the same serial (2418599054).
Who lists which name servers
Registry (what com lists)
erin.ns.cloudflare.comsimon.ns.cloudflare.com
The zone (its own NS records)
erin.ns.cloudflare.comsimon.ns.cloudflare.com
Registration data (RDAP)
erin.ns.cloudflare.comsimon.ns.cloudflare.com
Findings
InfoMore glue than needed
glue-extraRFC 9471The registry sends glue for erin.ns.cloudflare.com and simon.ns.cloudflare.com too, though they are not needed. Harmless.
InfoThe servers share a network
ns-diversityRFC 2182All 2 servers are on one network. 1 network, 2 subnets.
Pass8 checks passedShow
Each server
| Server | Addresses | Authoritative | SOA serial | TCP 53 | EDNS | Time |
|---|---|---|---|---|---|---|
| erin.ns.cloudflare.com |
| Yes | 2418599054 | Yes | Yes | 21 ms |
| simon.ns.cloudflare.com |
| Yes | 2418599054 | Yes | Yes | 16 ms |
- Copy findings for my DNS providerPlain text with the server names and the fixes.
- Change name servers at your registrarWHOIS shows who your registrar is.WHOIS
Structured result (JSON) · 4.2 KB
{
"name": "lookupowl.com",
"mode": "delegation",
"type": "NS",
"family": "any",
"qmin": false,
"delegation": {
"state": "ok",
"zone": "lookupowl.com",
"parent": {
"zone": "com",
"server": "c.gtld-servers.net",
"ns": [
"erin.ns.cloudflare.com",
"simon.ns.cloudflare.com"
],
"ttl": 172800,
"glue": {
"erin.ns.cloudflare.com": [
"108.162.192.113",
"172.64.32.113",
"173.245.58.113",
"2606:4700:50::adf5:3a71",
"2803:f800:50::6ca2:c071",
"2a06:98c1:50::ac40:2071"
],
"simon.ns.cloudflare.com": [
"108.162.193.232",
"172.64.33.232",
"173.245.59.232",
"2606:4700:58::adf5:3be8",
"2803:f800:50::6ca2:c1e8",
"2a06:98c1:50::ac40:21e8"
]
}
},
"child": {
"ns": [
"erin.ns.cloudflare.com",
"simon.ns.cloudflare.com"
],
"ttl": 86400
},
"rdap": {
"ns": [
"erin.ns.cloudflare.com",
"simon.ns.cloudflare.com"
]
},
"servers": [
{
"host": "erin.ns.cloudflare.com",
"ip": "108.162.192.113",
"ips": [
"108.162.192.113",
"172.64.32.113",
"173.245.58.113",
"2606:4700:50::adf5:3a71",
"2803:f800:50::6ca2:c071",
"2a06:98c1:50::ac40:2071"
],
"authoritative": true,
"soaSerial": 2418599054,
"tcp": true,
"edns": true,
"ms": 21,
"glueMatches": null
},
{
"host": "simon.ns.cloudflare.com",
"ip": "108.162.193.232",
"ips": [
"108.162.193.232",
"172.64.33.232",
"173.245.59.232",
"2606:4700:58::adf5:3be8",
"2803:f800:50::6ca2:c1e8",
"2a06:98c1:50::ac40:21e8"
],
"authoritative": true,
"soaSerial": 2418599054,
"tcp": true,
"edns": true,
"ms": 16,
"glueMatches": null
}
],
"findings": [
{
"id": "ns-count",
"level": "pass",
"evidence": "2 name servers are listed.",
"rfc": "RFC 2182",
"fix": null
},
{
"id": "ns-sets-match",
"level": "pass",
"evidence": "The registry and the zone list the same name servers.",
"rfc": "RFC 1034",
"fix": null
},
{
"id": "rdap-match",
"level": "pass",
"evidence": "The registration data lists the same name servers as the registry.",
"rfc": null,
"fix": null
},
{
"id": "glue-complete",
"level": "pass",
"evidence": "No name server sits inside lookupowl.com, so glue is not needed.",
"rfc": "RFC 9471",
"fix": null
},
{
"id": "glue-extra",
"level": "info",
"evidence": "The registry sends glue for erin.ns.cloudflare.com and simon.ns.cloudflare.com too, though they are not needed. Harmless.",
"rfc": "RFC 9471",
"fix": null
},
{
"id": "lame-delegation",
"level": "pass",
"evidence": "Every server we could reach answers for the zone.",
"rfc": "RFC 1912",
"fix": null
},
{
"id": "soa-serial-sync",
"level": "pass",
"evidence": "Every server serves the same serial (2418599054).",
"rfc": "RFC 1982",
"fix": null
},
{
"id": "ns-tcp",
"level": "pass",
"evidence": "Every server we reached answers over TCP.",
"rfc": "RFC 7766",
"fix": null
},
{
"id": "ns-edns",
"level": "pass",
"evidence": "Every server we reached supports EDNS.",
"rfc": "RFC 6891",
"fix": null
},
{
"id": "ns-diversity",
"level": "info",
"evidence": "All 2 servers are on one network. 1 network, 2 subnets.",
"rfc": "RFC 2182",
"fix": null
}
],
"diversity": {
"networks": 1,
"asns": [],
"prefixes": 2
},
"undelegated": null
},
"summary": "The delegation of lookupowl.com is correct: 2 name servers, the registry and the zone agree."
}More in DNS · Look up and trace
Next step
- DNSSEC checkDoes the chain of trust hold along this path?Check lookupowl.com in DNSSEC check
- DNS propagationHas the answer reached resolvers worldwide?Check lookupowl.com in DNS propagation
- DNS health checkCheck the name servers it foundCheck lookupowl.com in DNS health check
What the delegation check compares
A domain's name servers are written down in more than one place. The registry's servers for the top-level domain hold a list, which is what the rest of the world is sent to. The zone holds its own list in its NS records. And the registration data your registrar publishes holds a third copy. They are supposed to say the same thing. When they do not, some visitors are sent to a server that no longer answers, or that serves old records.
This page reads all three lists and sets them side by side, then asks every listed server directly: does it answer for the zone, which SOA serial does it serve, does it answer over TCP, does it support EDNS. A name server inside its own zone needs glue, its address stored at the registry, because there is no other way to find it. The check looks at that too.
The findings, in plain words
- Registry and zone differ. A server at the registry that the zone does not list is the serious case: the zone no longer uses it. A server only in the zone is a warning.
- Glue missing or out of date. A name server such as
ns1.example.comforexample.comhas no address at the registry, or an old one. Resolvers cannot find it. The fix is made at your registrar. - Lame delegation. A listed server answers REFUSED or is not authoritative. Resolvers waste time on it, and some give up.
- SOA serial out of sync. One server serves an older copy of the zone. If the serials look like dates, the page says how many days behind it is.
- No TCP or no EDNS. Large answers, such as DNSSEC records and long TXT records, need TCP. A server that does not answer over TCP fails for them.
- One name server, or all in one subnet. One server is a single point of failure. Servers in one subnet fail together.
Findings are sorted worst first, and the ones that pass are folded into a single line. Each finding names the RFC it comes from and says how to fix it, and the page can copy all of them as plain text for your DNS provider.
Test new name servers before you switch
Moving DNS to a new provider is safe only if the new servers already hold your zone. Switching first and finding out later means mail and websites fail for everyone whose resolver asks the new server. Open More options and enter the host names or IP addresses of the new name servers, one per line, up to eight. Nothing changes anywhere. We ask each new server directly for your zone's records and compare them with what resolvers see now.
- Create the zone at the new providerCopy your records across first. Most providers also give you the names of the servers to use.
- Enter the new servers hereWe check that each one is reachable, that it answers for your zone, and that the A, AAAA, MX, TXT and CAA records match what is live today.
- Fix what the table showsA missing MX record is the one that hurts most. A different value is marked with the value the new server gave.
- Switch at your registrarWhen the page says ready, replace the name servers at your registrar and keep the old provider running for two days, because resolvers keep the old list that long.
What this does not do
The check asks questions and reads answers. It never changes a record, never contacts your registrar and never sends mail. Only public names and public addresses are asked; a private or reserved address in the new servers box is refused with the line number. Some registries do not publish name servers over RDAP. When that is so, the third column says so and the comparison is skipped, not failed.
For a wider health report with mail, DNSSEC and IPv6 checks, use the DNS health check. To read how the lookup travels from the root to your servers, use the DNS trace. AI assistants can run the same check as the dns_trace tool with the mode set to delegation.
Questions people ask
What is a lame delegation?
A name server is listed for a domain but does not answer for it: it refuses, or it is not authoritative. Resolvers waste time on it and the domain gets slower, or fails for people who happen to pick that server.
What is glue, and when do I need it?
Glue is a name server's address stored at the registry. You need it when the name server lives inside the domain it serves, such as ns1.example.com for example.com, because resolvers could not find it otherwise. Name servers in another domain, such as ns1.provider.net, do not need it.
Why do the registry and the zone list different servers?
The list at the registrar and the NS records inside the zone are changed in two different places. A move to a new provider often updates one and forgets the other. Make the registrar list match the zone.
Does testing new name servers change anything?
No. We ask the new servers ordinary questions and compare their answers with what resolvers see now. No record, no registrar setting and no mail is touched.
Why is my registry data skipped?
Some registries do not publish name servers over RDAP, or did not answer in time. The comparison is skipped, not failed, and the other two lists are still compared.
How long after switching do I keep the old servers?
Two days is the safe answer. Resolvers keep the old list of name servers for as long as the registry told them to, often 48 hours, so some visitors still reach the old servers after the switch.
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_trace. Please be kind to the rate limits.
curl "https://lookupowl.com/api/v1/tools/dns-trace?q=cloudflare.com"claude mcp add --transport http lookupowl https://lookupowl.com/mcp