DNS Delegation Check
Validation Error
Delegation Chain
Nameserver Comparison
| Source | Nameservers | Count |
|---|---|---|
| WHOIS/RDAP | No WHOIS data available | |
| Parent (TLD) | ||
| Child (Domain) |
DNSSEC Security
Enabled (Signed) Disabled (Unsigned)Delegation Signer (DS) records found at the parent registry:
| Key Tag | Algorithm | Digest Type | Digest |
|---|---|---|---|
|
No DNSSEC DS records detected at the parent TLD server. The delegation chain is not signed.
SOA Synchronization
Checking Synced Out of SyncNameserver Status
DNS delegation is one of those things that works silently until it doesn't. A parent zone, say the .com registry, hands off authority for your domain to a set of nameservers. If the nameservers listed at that parent level don't match what your domain is actually using, you get intermittent, hard-to-diagnose resolution failures.
DNS delegation check tool traces that full chain, from root servers down through your domain's authoritative nameservers, and flags where it breaks.
Traces the full DNS delegation path from root servers through TLD nameservers down to your domain's authoritative nameservers.
Compares parent-zone NS records with child-zone authoritative NS records to detect lame delegations and misconfigurations.
Cross-references live DNS against RDAP/WHOIS-registered nameservers to verify your domain is properly configured.
What this tool actually checks
- The full delegation path from root to TLD to your domain's nameservers
- Whether parent-zone NS records match your domain's own authoritative NS records
- Whether any listed nameserver is "lame", meaning it doesn't actually hold authority for your zone
- Cross-referencing live DNS against your WHOIS-registered nameservers to catch outdated or mismatched entries
Why this catches problems other tools miss
A standard DNS Lookup shows you what your nameservers say. It won't tell you if the registry's records disagree with them. That mismatch, a parent-child conflict, is exactly what causes DNS that works for some visitors and fails silently for others.
If you've just made a change, a DNS Propagation Check is worth running alongside this one, since a delegation issue can look identical to a propagation delay at first glance.
FAQS
What is DNS delegation?
DNS delegation is the process where a parent zone (like the .com TLD) delegates authority for a domain to its nameservers. The delegation must be consistent across all levels for DNS to work correctly.
What is a lame delegation?
A lame delegation occurs when a parent zone lists nameservers that are not authoritative for the child domain. This can cause intermittent resolution failures and should be fixed by updating the NS records at your registrar.
What does parent vs child mismatch mean?
Parent NS records come from the TLD nameservers (set at your domain registrar). Child NS records come from the domain's own authoritative nameservers. If these differ, some resolvers may fail to locate your domain.
Why cross-check with WHOIS?
WHOIS shows the officially registered nameservers. Comparing WHOIS against live DNS helps detect outdated records, transfer issues, or registrar-level misconfigurations before they cause DNS outages.