How to fix: All Nameservers Concentrated at a Single Provider
Every authoritative NS record for this domain shares the same registrable domain (eTLD+1), for example all ns*.example-dns.com. Even though multiple NS records exist, they all depend on one DNS provider's infrastructure.
Why it matters
An outage, misconfiguration, or targeted attack against that single DNS provider can take every nameserver for this domain offline at once, the same single point of failure the 'at least two NS records' rule exists to prevent, just one layer up the stack.
This is a simple heuristic, not a definitive infrastructure map: it compares the registrable domain of each NS hostname and flags when every one matches. Real-world AWS Route 53 delegations, for example, deliberately spread across awsdns-*.com/.net/.org/.co.uk, different eTLD+1s each, so that pattern does not trigger this check. A large, geographically distributed provider can still offer real redundancy behind a single brand's domain; this only flags shared-domain concentration, not shared-provider risk in general.
How to fix it
- 1Add at least one nameserver from a second, independent DNS provider (a different eTLD+1) alongside the existing ones, for example pairing Cloudflare with Route 53 or NS1 as a secondary.
- 2If relying on one large, distributed provider intentionally, confirm their SLA covers your redundancy requirements; this finding does not necessarily mean action is needed.
- 3Verify with: dig +short NS example.com
Code examples
Check NS records
dig +short NS example.comReferences
Detected automatically by VulnRadar. The check id is dns-ns-single-provider-concentration, stable across every scan so you can filter or diff on it.
More dns checks
Questions
- How severe is All Nameservers Concentrated at a Single Provider?
- VulnRadar rates this info severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id dns-ns-single-provider-concentration, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.