Nameserver Checker

Why nameservers matter more than any other record

Nameservers decide which company's servers are allowed to answer questions about your domain. Change them and every other record — website, email, verification strings — moves with them. Get them wrong and the domain goes dark even though the registration is perfectly valid.

This checker asks the live DNS system which nameservers are authoritative for a domain, then shows the SOA record and mail servers alongside them so you can see the whole delegation in one screen.

Who is hosting this domain's DNS?

Nameserver hostnames are a strong clue about the provider behind a site. Names ending in cloudflare.com mean Cloudflare is answering queries; awsdns names mean Amazon Route 53; domaincontrol.com is GoDaddy; registrar-servers.com is Namecheap. The tool recognises the common ones and names them for you.

That is useful when you inherit a site with no documentation, when you are auditing a client's setup before a migration, or when you want to know how a competitor's infrastructure is arranged.

What a healthy delegation looks like

Most domains list two to four nameservers, usually on separate networks so a single outage cannot take the zone offline. All listed nameservers should be from the same provider unless you are deliberately running a split setup, and every one of them should answer with the same records.

A single nameserver is a fragile setup. Nameservers from two different providers that hold different records is worse: resolvers pick one at random, so the site works for some visitors and breaks for others, seemingly at random.

The most common nameserver mistakes

Updating DNS records at the old host after pointing the domain at a new one is the classic error. The edits are real, but nobody is reading that zone any more. Always confirm which nameservers are live before editing records.

Another is changing nameservers without first copying the existing records. The new provider starts with an empty zone, so email stops the moment the delegation switches even though the website may look fine. Export MX, TXT and any subdomain records first, then switch.

Checking after a migration

Registrar-level nameserver changes go through the TLD's registry and typically appear within minutes to a few hours, though some resolvers hold the old delegation for up to 48 hours because parent-zone records carry long TTLs.

Run this check the moment you make the change, then again a few hours later. When the new nameservers are the only ones returned, and the MX and SOA lines match what the new provider shows in its dashboard, the migration is complete.

Privacy and scope

Queries go to a public DNS-over-HTTPS resolver from your browser; no lookups are logged here and no sign-up is required.

This tool reports delegation as DNS sees it. It does not display registrar contact data or expiry dates — for those you need a WHOIS or RDAP record from the registry itself.

How delegation actually works, step by step

When a browser looks up your domain, the query starts at the DNS root servers, which point to the servers for your extension (.com, .dev and so on). Those registry servers answer with exactly one thing: the nameserver records your registrar submitted for your domain. The resolver then asks one of those nameservers for the real record — the website address, the mail servers, a verification string — and that answer is what reaches the visitor.

This is why the nameserver line sits above everything else in importance. A perfectly configured A record at your web host is invisible if the registry is still pointing the domain at your old provider's nameservers. The record that counts is always the one served by the currently delegated nameservers.

It also explains why changes can feel inconsistent during a switch. Different resolvers around the world refresh the delegation at different times, so for a day or two some visitors may reach the old zone and some the new. That window is normal and is why migrations should be planned so both zones serve correct answers at the same time.

Nameservers versus DNS records: the distinction that trips people up

Nameservers are set at your registrar — the company where you bought the domain. Individual DNS records (A, MX, TXT and the rest) are set at your DNS provider — the company whose nameservers the domain points to. These are often the same company, which is why the distinction gets blurred, but they are two separate control panels with two separate jobs.

If you buy a domain at one registrar and want a different company to run the DNS, you change the nameserver records at the registrar to the values the DNS provider gives you, and from then on all record editing happens at the DNS provider. Editing records at the registrar after that point has no effect at all, because the world is no longer asking the registrar's servers for answers.

When to check a domain's nameservers

Run a check before buying a used or expiring domain to see whose infrastructure it sits on, before a website migration to confirm the delegation you expect, after switching DNS providers to confirm the change has taken effect, and any time email or the website breaks in a way that suggests DNS — which is most mysterious breakages.

It is also a sensible first step in any security review. An unexpected nameserver provider can mean the domain was pointed elsewhere without the owner's knowledge. If the nameservers you see are not ones you recognise, that deserves immediate attention at the registrar.