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
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.
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.