NS Record Lookup

NS (Nameserver) records identify the authoritative DNS servers responsible for answering all queries about a domain. When a recursive resolver needs to look up any DNS record — an A address, an MX mail server, a TXT policy record — it first finds the NS records for the domain to know which servers are the official source of truth. The AT USE NS lookup tool queries live DNS via DNS-over-HTTPS and returns every authoritative nameserver currently published for the domain you enter. Use it to verify a DNS provider migration completed at the registrar, to confirm delegation matches the intended hosting setup, or to diagnose intermittent resolution failures caused by inconsistent nameserver configuration. No account required, no rate limits for normal use.

How to look up NS records

1. Enter the domain you want to inspect in the input field — for example, example.com. Enter only the apex domain; NS records live at the zone root, not at subdomains.
2. Click Lookup. The tool queries a public DNS-over-HTTPS resolver and returns all NS records currently published for that domain.
3. Review the list of nameserver hostnames returned. A typical result shows 2 to 4 nameservers from the same provider — for example, Cloudflare domains return a pair like aria.ns.cloudflare.com and rick.ns.cloudflare.com; AWS Route 53 domains return four nameservers in the awsdns-*.com/.net/.org/.co.uk pattern.
4. Compare the result against your registrar's nameserver configuration. If the registrar and this lookup agree, delegation is correct and all further DNS queries for this domain route through the right servers. If they disagree, a change you made at the registrar has not propagated yet.

Results come from an external public resolver rather than your local network, so they show the public view — the same result an external user or service would get when resolving this domain.

How DNS delegation works

The Domain Name System is a hierarchy. At the top are the root servers. Below them are the TLD servers (one set for .com, another for .net, and so on). When you register a domain and set nameservers at your registrar, the registrar instructs the TLD servers to publish a delegation: "for example.com, ask these nameservers." Every recursive resolver in the world follows this chain — root → TLD → authoritative nameservers — each time it resolves a name it has not recently cached.

Your registrar's nameserver configuration is therefore the authoritative source of what NS records the world sees. Your DNS provider (Cloudflare, Route 53, Google Cloud DNS, Namecheap, etc.) hosts the zone data, but none of it matters unless the registrar delegates correctly. This is why NS mismatches — where the registrar has old nameservers and your DNS provider's zone contains updated records — cause intermittent or complete resolution failures.

Nameserver changes propagate based on the TTL of the NS records in the parent zone (the TLD zone), which is controlled by the TLD registry. For .com and .net, this is typically 172,800 seconds (48 hours). In practice most resolvers see nameserver changes within a few hours once the registrar submits the update, but full propagation can take up to 48 hours.