DDDevDomeTrack. Protect. Grow.

Nameserver Lookup

See the NS records resolvers return and the delegation the registry has on file over RDAP, side by side, with single-point-of-failure warnings. All from your browser.

Your browser queries these services directly, so the name you look up and your IP address are visible to them: Cloudflare DNS and Google Public DNS (both public recursive resolvers) for records and comparison, and rdap.org, a redirector that forwards to the registry's RDAP server, for registration data. DevDome does not proxy, see or store these lookups. Privacy policy.

Run a lookup to get an evidence-based summary: web resolution, delegation, DNSSEC, email records, CAA and expiration, each with the observation behind it.
Enter a name above to query common DNS records (A, AAAA, CNAME, MX, TXT, NS, SOA, CAA) from a public recursive resolver, or pick a specific type including DS, DNSKEY, SRV, TLSA, SVCB and HTTPS.
Registration data appears here via RDAP: registrar, creation and expiration dates, EPP status codes, nameservers and DNSSEC delegation state.
SPF and DMARC analysis appears here: record syntax, the 10-DNS-lookup limit, policy strength and common misconfigurations, with the exact records as evidence.
Compares one record type between Cloudflare and Google. These are observations from two public recursive resolvers, not proof of global propagation. Add an expected value above to check whether your change is visible to each.

Delegation is the root of every DNS problem

When something is wrong with a domain and no individual record explains it, look at the delegation. The zone's NS records and the registry's delegation must point at the same working servers; a half-finished migration, a decommissioned DNS provider, or a registrar that silently reset nameservers can leave the two out of sync, and the symptoms are maddeningly intermittent because different resolvers notice at different times.

This lookup puts both views one tab apart: the resolver's NS answer and the registry's RDAP nameserver list. The Summary tab adds the resilience basics: how many nameservers answered, and whether the domain is one server away from a total outage.

Get alerted when your DNS delegation changes →

Nameserver FAQ

What do NS records actually control?

Everything. NS records delegate the zone: they name the servers that hold the authoritative copy of every other record for the domain. Change your nameservers and you change which company answers DNS for you; break them and nothing else about your DNS matters. That is why nameserver changes deserve more caution than any record edit.

Why does this tool show nameservers in two places?

Because there are two sources that must agree. The DNS records tab shows the NS set a recursive resolver returns, which reflects the zone itself. The Registration tab shows the nameservers the registry has on file via RDAP, which is what the parent zone delegates to. After a nameserver migration these can disagree for a while, and a persistent disagreement means the migration was never completed on one side.

How many nameservers should a domain have?

At least two, on separate infrastructure, which is a registry requirement for most TLDs and basic resilience: if a single nameserver goes down and it is the only one, your entire domain goes down with it. Managed DNS providers typically assign two to four names spread across independent networks. The Summary tab flags a single-nameserver answer as a single point of failure.

I changed nameservers. How do I verify the change took?

Check the Registration tab first: RDAP shows what the registry has on file, and that is what actually changed when you edited nameservers at your registrar. Then compare the NS answers in the DNS tab and the Resolver comparison tab: recursive caches can serve the old delegation until their TTL expires, commonly up to 48 hours for NS records. If RDAP shows the new names, the change is in; caches just need to age out.

Can I see which nameserver answered my query?

Not from a browser. This tool queries public recursive resolvers, which pick authoritative servers internally and do not expose which one they asked. Verifying that each individual authoritative nameserver returns the same zone data requires querying each of them directly, which browser tools cannot do; the answers here are the resolver’s merged cache view, and the page says so rather than pretending otherwise.

More free tools: DNS & WHOIS Lookup · MX Lookup · Reverse DNS · SSL Checker