DNS
NS Record Lookup
Look up a domain's nameservers
Tool features
4 checks
Name Server Lookup
Find all authoritative name servers for a domain
Provider Detection
Identify DNS hosting providers and service types
NS Validation
Validate nameserver format and detect configuration issues
Fast Resolution
Quick DNS resolution with multiple resolver options
What is an NS record & how it works
NS (Nameserver) records declare which servers are authoritative for a domain's DNS zone — the servers that answer all other record queries (A, MX, TXT and so on). They are published in the parent zone as part of the domain's delegation.
This lookup reads the delegation from the parent zone, lists every authoritative nameserver, and checks that the zone's own NS records agree with what the parent publishes — a common source of resolution problems.
NS Record
Names an authoritative nameserver for the domain’s DNS zone.
Delegation
The parent zone points a domain at its nameservers, handing off authority.
Glue Record
The nameserver’s IP, published at the parent so resolvers can reach it.
How to use this tool
1
Enter a domain
Type a domain or URL, e.g.
example.com — we clean it to the registrable domain automatically.2
Pick a resolver (optional)
Open Advanced Settings to query a specific public resolver such as Google (8.8.8.8) or Cloudflare (1.1.1.1).
3
Run the lookup
Click Check NS Records to read the delegation from the parent zone and the domain’s own nameservers.
4
Review the results
Confirm the authoritative nameservers, spot parent/zone mismatches, and read the diagnostics and recommendations.
Related tools
4 tools
DNS Lookup
Perform DNS queries for A, AAAA, MX, TXT, CNAME, and other DNS record types
SOA Lookup
Check Start of Authority (SOA) records for domain authority and DNS zone information
DNS Servers
Find and test DNS servers for a domain or IP address with performance metrics
Public DNS Speed Test
Compare response times across popular public DNS resolvers like Google, Cloudflare, and Quad9
Frequently asked questions
5 Q&A
At least two, on separate networks, for redundancy. Most registrars provide two to four nameservers by default.
When a nameserver is inside the domain it serves (e.g.
ns1.example.com for example.com), the parent zone must publish its IP as a glue record so resolvers can reach it.The parent zone delegates to a set of nameservers; those servers should publish the same NS set. A mismatch can cause inconsistent or failed resolution.
Delegation changes are governed by the TTL at the parent (often 24–48 hours), so allow up to two days for a nameserver change to fully propagate.