NS Record Lookup

Inspect authoritative Name Server (NS) records for a domain.

Resolved Target:

-

TypeHost / NameTarget / ValueTTL
No records loaded.

How to use this tool

Displays only NS records. A hostname without NS records may inherit its DNS service from a parent zone.

Enter the target, complete any relevant options and choose Check. Review the requested records, query outcomes and diagnostic findings. Copy Report saves the visible report.

Reading the results

No matching records and an unavailable query are different outcomes. TTLs are displayed in seconds; zero is a valid TTL. A completed request does not mean a domain passed its health checks. Only the submitted DNS owner and explicitly listed checks are inspected.

Frequently Asked Questions

Why do the returned nameservers differ from my hosting account?

Hosting and DNS can be managed by different providers. The lookup reports the NS records visible in public DNS, not the names listed only inside a hosting dashboard.

Why are both old and new nameservers appearing?

Resolver caches may retain the earlier NS set during a delegation change. An authoritative zone can also contain both sets if old records were not removed.

How many NS records should a domain have?

Domains commonly publish at least two nameservers for resilience. The exact number depends on the DNS provider and registry configuration.

Does an NS result confirm that the nameservers answer correctly?

No. It confirms the published NS hostnames. It does not test whether each authoritative server returns the complete zone.

Why does the lookup show no nameserver records for a subdomain?

A subdomain only has NS records when it is delegated as its own DNS zone. Otherwise, the parent domain's nameservers remain authoritative.

What should I do if one nameserver is unexpected?

Compare the full returned set with the registrar and DNS provider settings. Remove stale delegation entries at the system that controls the domain's nameservers.