Nameserver Checker

Nameservers are the hosts listed in a domain’s NS records. They answer DNS queries for that domain. A resolved IP is the address of that host. This table shows those columns without asking DNS.

A real NS set is the delegation at the registry. It might be two hosts at your DNS company, or four. This table cannot show that, because it never asks. Use it to learn the columns, then query NS records with a resolver.

Nameserver hostname is one of the values Nameserver Checker puts on screen. An NS hostname is the server that should answer DNS for the domain. The rows are always ns1.cloudflare.com and ns2.cloudflare.com. A domain on Route 53, a host, or a registrar’s DNS still gets this pair.

Read Resolved IP on its own before you mix it with the other rows. The address of the nameserver itself, not the website’s A record. The sample uses 173.245.59.10 and 173.245.58.11. Those addresses are not looked up. Do not ping them and call the result your site.

Location answers a narrower question than the headline number. A place label for the nameserver. Both rows say United States. Anycast nameservers are not in one country. This label does not locate them.

Treat Row count as a label with a specific job. Delegations often have two or more NS hosts. The sample always has exactly two rows. A zone with four nameservers will still show two.

The Copy line is worth a full stop. Copy puts the hostname on the clipboard. The copied text is the fixture hostname. Pasting it into a registrar as a new NS would be a change you did not verify.

You can copy a hostname from a row. Copying ns1.cloudflare.com into a document does not make it the domain’s nameserver. The IP addresses 173.245.59.10 and 173.245.58.11 are part of the fixture too.

If you remember one sequence from Nameserver Checker, remember the fields in the order they change a decision. Nameserver hostname matters because An NS hostname is the server that should answer DNS for the domain. In practice, The rows are always ns1.cloudflare.com and ns2.cloudflare.com. The mistake to avoid is this: A domain on Route 53, a host, or a registrar’s DNS still gets this pair. Resolved IP matters because The address of the nameserver itself, not the website’s A record. In practice, The sample uses 173.245.59.10 and 173.245.58.11. The mistake to avoid is this: Those addresses are not looked up. Do not ping them and call the result your site. Location matters because A place label for the nameserver. In practice, Both rows say United States. The mistake to avoid is this: Anycast nameservers are not in one country. This label does not locate them. Row count matters because Delegations often have two or more NS hosts. In practice, The sample always has exactly two rows. The mistake to avoid is this: A zone with four nameservers will still show two. Copy matters because Copy puts the hostname on the clipboard. In practice, The copied text is the fixture hostname. The mistake to avoid is this: Pasting it into a registrar as a new NS would be a change you did not verify. After that, the checks are simple. You compared the rows with a domain that is not on Cloudflare. You did not change live nameservers from this table. You did not treat the IP addresses as the website origin. You ignored the single-country location for anycast planning. A DNS query is the source for the real NS set.

Keep Nameserver Checker as this step only. When the job moves on, the DNS Checker is the next page: DNS Checker takes a domain and a record type such as A, AAAA, CNAME, or TXT, then lists locations with a propagated or pending mark. The WHOIS Lookup covers a different piece of the same work: WHOIS Lookup takes a domain and shows registrar, registered date, expiry, registrant, status, and nameservers.