Nameservers: the signposts of a domain
2 min read
What the nameserver lines in whois output mean: spotting hosting/CDN from NS records, detecting migrations, and the most common NS mistakes.
Their job: pointing the domain at servers
A nameserver (NS) answers the question "who holds this domain's DNS records?". When a browser opens a site, it first learns the NS names from the registry, then asks those servers for the IP address. The NS lines in whois show where the domain is delegated — the quickest clue to where a site is hosted.
What an NS line reveals
NS names usually give away the infrastructure: ns.cloudflare.com → behind Cloudflare; awsdns → AWS Route 53; a local hosting brand → shared hosting. It is also the practical way to spot a migration: the whois "updated" date and an NS change usually move together. Our tool lists NS records as a separate card with one-click copy.
Common mistakes
The three most common NS mistakes: forgetting the old host's NS entries after a migration (the domain keeps pointing at the old server), leaving a single NS (the standard requires at least two; if the lone one fails, the site goes dark) and a mismatch between the registrar panel's NS and the DNS provider's zone. When in doubt, the whois NS list is the first place to look.
Look up your own domain
Everything in this guide, our tool shows with live data in seconds: registration and expiry dates, registrar, nameservers, age and value analysis — free, no signup.
Query with WhoisFrequently asked questions
How long does an NS change take to propagate?
The registry side updates within minutes; resolvers around the world drop the old answer per TTL — a few hours in practice, 24-48 hours at worst.
Can whois NS differ from actual DNS?
Whois shows what is written in the registry, and real resolution starts there. A difference usually means propagation is in progress or a stale entry was left at the registry.