Free Nameserver Lookup — Find NS Records for Any Domain
Nameservers are the foundation of your DNS. They hold every other record — A, MX, TXT, all of them. If your nameservers are misconfigured or unreachable, your entire domain goes dark.
Check nameservers now: Our free DNS Lookup Tool shows NS records and flags domains with insufficient nameserver redundancy.
What Are NS Records?
NS (Name Server) records declare which servers are authoritative for a domain's DNS zone. These are the servers that other resolvers query when they need to look up any record for your domain.
Example:
example.com. 86400 IN NS ns1.cloudflare.com.
example.com. 86400 IN NS ns2.cloudflare.com.
NS records are typically set at two levels:
- At the registry (your registrar) — Tells the TLD (
.com,.net, etc.) where to find your DNS - In your DNS zone — Confirms the delegation
Both must match. If your registrar points to Cloudflare but your zone says Route53, you have a broken delegation.
How to Look Up Nameservers
Method 1: DNS Lookup Tool
Enter any domain in our DNS Lookup Tool. Nameservers appear in their own section with a count badge. The health grade flags domains with only one nameserver.
Method 2: Command line
# Find nameservers
dig example.com NS +short
# Output:
# ns1.cloudflare.com.
# ns2.cloudflare.com.
# Check what the registry says (query the TLD servers)
dig example.com NS @a.gtld-servers.net +short
The second command queries the .com TLD servers directly — this shows what's configured at the registrar level, bypassing any caching.
Why You Need Multiple Nameservers
If your only nameserver goes down:
- Your website stops resolving
- Email stops being delivered
- API endpoints become unreachable
- SSL certificate renewals may fail
Everything depends on DNS. Two nameservers is the minimum. Most providers give you 2-4, ideally on separate networks and in different geographic regions.
Our DNS Lookup Tool checks this automatically. A single nameserver drops your DNS health grade.
Common DNS Providers and Their Nameservers
| Provider | Nameservers |
|---|---|
| Cloudflare | *.ns.cloudflare.com (assigned per domain) |
| AWS Route53 | ns-*.awsdns-*.com/net/org/co.uk |
| Google Cloud DNS | ns-cloud-*.googledomains.com |
| DigitalOcean | ns1-3.digitalocean.com |
| GoDaddy | ns*.domaincontrol.com |
| Namecheap | dns1-2.registrar-servers.com |
Your nameservers tell you (and anyone else) which DNS provider manages the domain.
Troubleshooting NS Issues
Domain doesn't resolve at all
Check if the nameservers are reachable:
dig @ns1.cloudflare.com example.com A +short
If this fails, either the nameservers are down or they don't have your zone configured. Verify in your DNS provider's dashboard that the zone exists and has records.
Nameservers at registrar don't match DNS provider
You signed up for Cloudflare DNS but forgot to update nameservers at your registrar. The registrar still points to your old hosting provider's nameservers. Fix: update NS records at your registrar to match your DNS provider.
Lame delegation
A "lame" nameserver is one that's listed in the NS records but doesn't actually serve the zone. This happens when you migrate DNS providers and remove the old zone but leave the old NS records. Some resolvers will query the lame server, get no answer, and fail.
Slow propagation after NS change
Nameserver changes propagate through the registry, not just your DNS provider. Registry-level NS TTLs are typically 24-48 hours. There's no shortcut — you have to wait. Plan NS migrations accordingly. See our propagation guide.
Recommended Resources
- Free DNS Lookup Tool — Check nameservers and all DNS records
- DNS Record Types Explained — What every record type does
- DNS Propagation Guide — How long NS changes take
- Free Domain Expiration Checker — Check registrar and WHOIS data
- How to Check DNS Records — Three free lookup methods
Morten Pradsgaard is the founder of exit1.dev — the free uptime monitor for people who actually ship. He writes no-bullshit guides on monitoring, reliability, and building software that doesn't crumble under pressure.