Nameserver & DNS Delegation Audit
Your name servers decide where your domain points — and a broken or inconsistent setup is a hijacking opportunity. This audits a domain's delegation, flags stale or mismatched name servers, sizes how much each provider actually handles, and surfaces registry facts — so you can catch delegation weakness before it's exploited.
How it uses the graph
Traverses the DNS layer of the graph, in 6 steps:
How it walks the graph6 steps
01Nameservers
Listing the nameservers and checking each resolves…
DNS
02Delegation summary
Counting the delegated nameservers…
DNS
03Nameserver network placement
Nameserver network placement…
DNS
04Estate size & exclusivity per nameserver
Estate size & exclusivity per nameserver…
DNS
05Estate exclusivity verdict
Estate exclusivity verdict…
DNS
06TLD registry operator
TLD registry operator…
DNS
Why each step runs
- 01Nameservers. A 'lame' nameserver (no resolution) is a delegation gap and hijack vector.
- 02Delegation summary. An unusually small NS set (0-1) is fragile and suspicious.
- 03Nameserver network placement. Shows which networks the domain's nameservers actually sit on, so a nameserver hosted on an unexpected ASN stands out as a hijack or misdelegation signal.
- 04Estate size & exclusivity per nameserver. For each nameserver, counts how many other domains it serves and lists sample siblings, so you can tell a dedicated/boutique nameserver from a mass-hosting commodity one and pivot to co-hosted domains.
- 05Estate exclusivity verdict. Collapses the whole nameserver estate to one verdict: if the most exclusive nameserver serves only a handful of domains the shared-nameserver pivot is attribution-grade, if every nameserver is commodity the pivot is noise.
- 06TLD registry operator. Names the registry operator that runs the domain's top-level domain (returns nothing for gTLDs like .com that have no dedicated operator node).