NS Record Lookup
Check NS records (authoritative nameservers) for any domain across 12 global resolvers. Free real-time DNS propagation checker.
What is an NS record?
An NS record ("name server") tells the world which DNS servers are authoritative for a domain. When you change DNS providers — moving from your registrar's nameservers to Cloudflare, AWS Route 53, etc. — you're updating the NS records at the registrar level. The new nameservers must be live before traffic shifts.
When to check NS records
- You just changed DNS providers and need to confirm the new nameservers are live
- You suspect a domain has been hijacked (stolen via NS change at the registrar)
- You're auditing which DNS provider a domain uses
- A DNS change you just made isn't taking effect — first thing to check is whether you're editing the right zone
FAQ
Why do NS changes take so long to propagate?
NS records at the registrar level (the "delegation" from the TLD) often have TTLs of 24–48 hours. That's why moving DNS providers commonly takes a day or two before every resolver in the world sees the new nameservers.
Should all NS records agree?
Yes. The NS records published by the parent (registrar) and the NS records published by the zone itself should match. Mismatches ("lame delegation") cause intermittent resolution failures.
All record-type lookups
WhereIsDNS has dedicated pages for each common DNS record type. Each one defaults the tool to that record type and includes background on what the record means and what to look for.
- A Record Lookup — IPv4 addresses for a hostname
- AAAA Record Lookup — IPv6 addresses for a hostname
- CNAME Lookup — Aliases pointing one hostname to another
- MX Record Lookup — Mail servers for a domain (with priorities)
- TXT Record Lookup — SPF, DKIM, DMARC, and other text records
- SOA Record Lookup — Authority metadata for a DNS zone
- CAA Record Lookup — Which CAs may issue certs for the domain
- PTR (Reverse DNS) Lookup — Reverse DNS — IP back to a hostname
- Home (defaults to A records)