NS Record Lookup: Free Nameserver Checker

An NS record lookup shows which authoritative nameservers are responsible for a domain's DNS. Enter a domain name and this free tool returns every nameserver, its IP address, the DNS provider when it is recognized, and the TTL. Use it to verify nameserver changes, find out who hosts your DNS, or troubleshoot a domain that stopped resolving.

What Is an NS Record in DNS?

An NS (name server) record is a DNS record that names a server authorized to answer queries for a domain. Most domains have two to four of them, and together they tell the internet where the domain's other records (A, MX, TXT and so on) are stored.

The delegation works in layers. The registry for the extension, such as .com, points to your nameservers, and your DNS provider's zone lists the same servers. You change nameservers at your registrar, not by editing records inside the zone, which is why people often ask why NS records "are not editable" in their DNS dashboard.

How is an NS record different from an A record or CNAME?

An NS record hands a zone to a nameserver, an A record maps a name to an IPv4 address, and a CNAME makes one name an alias of another. An NS target must be a hostname, never an IP address. If you need the address a hostname points to, run the A record lookup, and for aliases use the CNAME record lookup.

What is the relationship between NS and SOA records?

NS records list which servers are authoritative, while the SOA record stores zone details such as the primary server and a serial number. Every properly configured zone has both. This tool focuses on the NS side of that pair.

How to Use the NS Record Lookup

You need only a domain name and one click. Follow these steps:

1. Find the Domain Name field, which shows the placeholder example.com.
2. Type the domain you want to check, for example mybakery.com. If you paste a full address that starts with http or https, the tool keeps only the host name and ignores any path or query string.
3. Click Lookup NS Records. The button changes to "Looking up..." while the request runs.
4. Read the summary line, which says how many nameservers were found for your domain.
5. Review the table with the columns Nameserver, IP, Provider and TTL.
6. Compare the nameservers with what your registrar or DNS host says they should be.

The domain must contain at least one dot and use letters, numbers, hyphens or underscores. A single word such as "localhost" returns the message "Please enter a valid domain name."

Worked Example: Checking a Domain After a Move

Say you moved mybakery.com to a new DNS host last night and want to confirm the switch. You enter mybakery.com and click the button. The tool reports "2 Nameserver(s) found for mybakery.com" and lists two rows, such as aria.ns.cloudflare.com and bob.ns.cloudflare.com. Each row shows an IP address, the provider "Cloudflare", and a TTL such as 86400s. These values are an illustration, not live data.

What this means: both nameservers belong to the new host, so the change is visible. If the table still showed your old host's names, the switch has not reached the answer you are seeing. You would then check that you saved the new nameservers at the registrar, wait, and look up the domain again. For a side-by-side view of how different resolvers answer, use the DNS propagation checker.

How Do You Read the Results?

The results table has four columns, and each answers a different question.

Nameserver

This is the hostname of an authoritative server, for example ns1.example-host.com. A healthy domain normally lists at least two, ideally on different networks, so one failure does not take your site offline. A single nameserver is a risk worth fixing.

IP

This is the address the nameserver hostname points to. If it shows a dash, the tool could not find an address for that hostname. That may be a temporary gap, so retry before treating it as a fault.

Provider

The tool labels nameservers from a set of well-known providers: Cloudflare, Amazon Route 53, Google Cloud DNS, Azure DNS, GoDaddy, Namecheap, DNSimple and NS1. A dash does not mean something is wrong. It means the nameserver name did not match any of those, which is common with hosting companies and custom setups. Read the hostname itself, since it usually contains the company's domain.

TTL

TTL is the number of seconds a resolver may cache the answer. Values such as 3600 (one hour) or 86400 (one day) are common for NS records, and delegation values at the registry level are often even longer. A long TTL explains why an old nameserver can still appear for a while after you switch.

Messages you may see

• No NS records found for this domain: the name exists but has no NS answer. This is typical for a subdomain that is not delegated separately. Look up the parent domain instead.
• NXDOMAIN: the DNS name does not exist. Check spelling or whether the domain is registered.
• DNS lookup unavailable: the check could not be completed. Wait a moment and run it again.

What Are NS Records in Route 53 and Azure?

In both Amazon Route 53 and Azure DNS, the NS records are the set of four nameservers assigned to your hosted zone. After you create the zone, the platform shows these servers and you copy them into your registrar's nameserver settings. The lookup then confirms the world sees them.

Route 53 nameserver names contain "awsdns" and Azure names contain "azure-dns", so the Provider column labels them as Amazon Route 53 or Azure DNS. If you see a mismatch, for example Route 53 servers in the zone but different servers in the lookup, the registrar still holds the old values. Note that the four servers in a zone are assigned to that zone, so copying nameservers from a different zone with the same name will not work.

How Do You Check NS Records from the Command Line?

You can run dig NS example.com or nslookup -type=ns example.com in a terminal, and both return the same kind of answer. The online lookup is quicker when you are on a phone, working with a client, or do not want to install anything. It also adds each nameserver's IP, a recognized provider name and the TTL in one table. For other record types in one place, try the DNS lookup tool.

When Should You Run an NS Record Lookup?

• After changing DNS hosts: confirm the new nameservers are live before you shut down the old account.
• Before editing records: make sure you are editing in the DNS dashboard that is actually authoritative. Records added at a provider that is not listed will have no effect.
• Troubleshooting a site or email outage: a wrong or missing nameserver breaks websites and mail together. Follow up with the MX record lookup if mail is the problem.
• Auditing client domains: identify which provider each client uses before you take over a project.
• Checking an expired or parked domain: registrar default nameservers often point to a parking page.
• Security review: unexpected nameservers can signal a hijacked domain. If DNSSEC is in use, a mismatch can also cause validation failures, so verify with the DNSSEC validator.

Best Practices and Troubleshooting Tips

Look up the right name

Query the registered domain (example.com), not www.example.com. A www hostname is usually a CNAME or A record and has no NS records of its own, so you would see an empty result.

Do not edit NS records inside the zone to move providers

To change DNS hosts, first recreate all your records at the new provider, then update the nameservers at your registrar. Switching before the new zone is complete causes downtime for any record you forgot, especially MX and TXT records.

Expect a delay

After a change, caches may keep the old answer until the TTL expires. Wait, then look up the domain again. Many changes appear within hours, though a day or two is normal when the old TTL was long.

Use two or more nameservers

Redundancy is the whole point of having several. Providers that give you four servers are doing it for a reason, so enter all of them at the registrar.

Check for typos

A single wrong character in a nameserver name at the registrar can make the domain stop resolving. Compare each hostname exactly against your provider's instructions.

Limitations to Keep in Mind

The tool shows the NS answer at the moment you run it, and a cached answer can differ from what another network sees. It reports what is published, not whether each nameserver is healthy or serving the correct records. The provider label depends on the nameserver name, so a company that resells another provider's DNS may appear as blank. Check your registrar's dashboard when you need the final word on what is saved.

Enter a domain in the field above and click Lookup NS Records to see its nameservers, IPs, provider and TTL in seconds. If you manage several domains, the Network and IP tools collection has the related checks you will likely need next.