Free Nameserver Lookup
Enter a domain to list its nameservers, ask each one directly whether it answers for the zone, and see whether that list matches the delegation held at the registry.
Asking the nameservers...
Could not check
- Answers for the zone No answer Not queried
No NS records came back for this domain.
The registry read returned no nameservers for this domain, so this comparison was skipped.
What a Nameserver Lookup Tells You
A nameserver lookup finds the servers that hold a domain's DNS records. Every other record, from the website address to the mail route, is answered by those servers, so they are the first thing to confirm when a domain moves host or stops resolving.
A plain list only tells you what a resolver has cached. This nameserver checker goes further: it reads the NS records through a public resolver, then asks up to four of those servers directly for the zone's NS set, and compares the result with the nameservers in the registry record. For every other record type, run a full DNS lookup.
- Enter the domain. A subdomain is checked at its registered domain, which is where delegation lives.
- We read the NS records through a public resolver, then query the servers directly.
- We read the nameservers the registry holds for the domain.
- Read the verdict, then the server list and the registry list beneath it.
What this check settles
- Who runs the DNS: the hostnames show which provider answers for the domain, whatever the registrar is.
- Whether the servers respond: a listed server that stays silent slows lookups and removes your redundancy.
- Whether a change has landed: the registry and the zone should name the same servers once a move is complete.
Nameserver Check Results Explained
Three views of the same delegation are compared. Here is what the main outcomes mean.
| Result | What we saw | What it means | Action |
|---|---|---|---|
| Consistent | All three views match | The registry, the resolver and the servers name the same set. The delegation is settled. | None |
| One nameserver | A single NS record | There is no second server to answer if this one fails, so the whole domain depends on it. | Add one |
| Server not answering | A listed server is quiet | A delegated server gave no answer for the zone. It may be down, firewalled, or no longer hosting the zone. | Investigate |
| Registry mismatch | Registry and DNS differ | The registry names different servers from the ones resolvers return. Expected in the middle of a move, and worth explaining at any other time. | Verify |
How to Read the Result
The verdict comes first, then each server and the registry's list.
The verdict
The headlineA single reading of the delegation: whether the views agree, and if they do not, which comparison failed first.
Nameservers from the resolver
The listThe NS records as a public recursive resolver returns them, which may be cached. Beside each one is what happened when we asked that server directly. Up to four are queried per lookup.
Operator type
The providerA broad category read from the hostnames: cloud DNS, registrar DNS, a parking service, or a web host. It is a pattern match, not a statement of who owns the account.
Nameservers at the registry
The sourceThe delegation as the registry reports it over RDAP or WHOIS. This is the list you change at your registrar, and the one the rest of the internet is ultimately sent to.
What Nameservers Do
Nameservers are the authoritative servers for a domain. When a resolver needs an address, the registry for the TLD points it to the domain's nameservers, and those servers give the final answer.
That makes delegation a chain with two ends: the registry holds the list of servers, set through your registrar, and the zone on those servers holds its own NS records. The two are maintained separately, so they can drift apart.
How to Change Nameservers Safely
A nameserver change moves every record at once, so the new zone must be complete before you switch.
The usual sequence:
- Copy every record to the new provider, including mail and verification records.
- Check the new servers answer correctly for the zone before changing anything.
- Update the nameservers at your registrar.
- Watch propagation, and keep the old zone live until the NS TTL has passed.
Where Nameserver Setups Go Wrong
Most delegation faults stay hidden until the one server still working fails. The common ones:
- A server left on the list after a provider change. It answers nothing, and lookups quietly wait on it before trying the next one.
- Updating the NS records in the zone and assuming that moved the domain. Delegation only changes at the registrar.
- Two nameservers that share one network or one host, which pass a count check and fail together.
- Cancelling the old DNS plan on the day of the move, while resolvers still hold the previous delegation in cache.
Why Nameserver Checks Matter
Spot a hijack early
Changing a domain's nameservers hands over its website and mail in one step. A list you do not recognise is the first sign.
Avoid a full outage
When every nameserver stops answering, the site, email and APIs all fail together, even though each service is healthy.
See who runs the DNS
The registrar and the DNS provider are often different companies. The nameservers show where records really need to be edited.
Confirm a migration finished
Matching lists at the registry and in DNS mean a move is complete, and the old provider can safely be retired.
Who Checks Nameservers
The same lookup answers a different question depending on who runs it.
IT & DNS Admins
Confirm each server answers for the zone before and after a provider change.
For DNS monitoringSecurity Teams
Verify that delegation still points where it should, across every domain you are responsible for.
For IT & MSPsSEO & Site Owners
Find out who actually hosts the DNS before a site migration puts rankings at risk.
For publishersRelated DNS & Registry Tools
Nameservers tell you who answers. These tell you what they say.
Read the registry record
See the registrar, the status codes and the dates alongside the delegation.
WHOIS lookupCheck propagation
Just moved provider? Compare what four public resolvers see now.
Check propagationMonitor the delegation
Get an alert when a domain's nameservers change, instead of finding out from an outage.
DNS monitoringFrequently Asked Questions
Common questions about nameservers and how to check them.
How do I find a domain's nameservers?
Enter the domain in the lookup above. It lists the NS records from a public resolver, tests each server directly, and shows the nameservers the registry holds. You can also run dig NS example.com from a terminal.
What is a nameserver?
A server that holds a domain's DNS records and gives the authoritative answer for them. Hostnames such as ns1.example-host.com are the servers themselves. The NS records name which ones a domain uses.
What is the difference between a nameserver lookup and a DNS lookup?
A nameserver lookup is about delegation: which servers answer for the domain and whether they agree. A DNS lookup reads the records those servers publish, such as A, MX and TXT.
How many nameservers should a domain have?
At least two, which is what the DNS standard asks for, and many registries require it. They should sit on separate networks, so one failure cannot take out both.
Why do the registry and DNS show different nameservers?
Usually because a change is in progress and resolvers still hold the old list in cache. If the lists stay different after the NS TTL has passed, the zone's own NS records may not have been updated, or one side was changed without the other.
How long does a nameserver change take?
The registry usually publishes a change within minutes to hours. Resolvers that cached the old delegation keep using it until its TTL runs out, which is commonly up to 24 to 48 hours.
Why does a nameserver show as not answering?
It gave no NS answer for the zone when we asked it directly. It may be offline, blocking our query, or no longer configured for this domain. Run the check again before acting on a single result.
Can I look up the nameservers of a subdomain?
This tool checks the registered domain, because that is where the registry's delegation applies. A subdomain delegated to other servers can be read with a DNS lookup of its NS records.
Who can change my nameservers?
Anyone with access to the domain at its registrar. That is why a registrar account breach is so serious, and why a registry lock and change monitoring are worth having on important domains.
Start Monitoring & Catching Domains Today
Join founders, agencies, and domainers already protecting their portfolio. Your first 5 domains are free.
No credit card required • Cancel anytime
Guides for domain operators
Deep dives on domain names, DNS, SSL, acquisitions and portfolio management.
All guides →
4 Letter Domains: The Complete LLLL Investing Playbook
4 letter domain names represent one of the most liquid segments of the domain aftermarket. All 456,976 possible .com combinations are registered.
.SI Domain: Slovenia's 30-Year-Old ccTLD Is Suddenly Super Intelligence
What is the .SI domain? Learn how Slovenia's country-code TLD went from 10 registrations in 1992 to a 2,199% surge in September 2026, and why 'super intelligence' made .SI the new .AI.
Infringing Domains: Detecting, Monitoring, and Recovering
Your domain is your storefront. Every day, someone registers a lookalike of it, to skim your traffic, phish your customers, or hold it for ransom. This guide covers what infringing domains are, how to find them before they hurt you, and exactly what to do when you do.