Skip to the content

NS Lookup

Find the name servers that are in charge of a domain, and with them the company where its DNS is managed.

The name you look up is sent to Cloudflare's public DNS resolver, or to Google's if Cloudflare cannot be reached. Nothing else is sent.

Record types
Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What the name servers tell you

The NS records of a domain list the servers that hold all its other DNS records. Every answer, from the web address to the mail servers, comes from them. That makes this the lookup to start with when a change "does not work": it shows where the records really have to be edited.

The names usually give the company away:

Name servers end inDNS is managed at
ns.cloudflare.comCloudflare
awsdns- and a number, under .com, .net, .org or .co.ukAmazon Route 53
domaincontrol.comGoDaddy
registrar-servers.comNamecheap
googledomains.comGoogle Cloud DNS
azure-dns.com, .net, .org or .infoMicrosoft Azure DNS
digitalocean.comDigitalOcean

A domain should have at least two name servers on different networks, so that it stays reachable when one of them fails.

Common misunderstandings

  • Editing records at the wrong company. After a move to other name servers, the old provider's control panel still shows the records and still lets you change them. Nothing reads them any more.
  • Expecting a quick switch. The list of name servers is also kept by the registry of the top-level domain, with a long TTL: two days for .com. A change of name servers can take that long to reach everyone.
  • Looking at a subdomain. www.example.com normally has no NS records of its own and gives an empty answer. They sit at the top of the zone, on example.com.

The command-line program nslookup is named after name servers, but it looks up any record type. This page looks up the NS records themselves.

The DNS lookup page asks for all record types of a name at once, and explains TTLs, DNSSEC and which resolver gives the answers.