How this lookup works
We query the domain's NS records through public resolvers. If the name isn't the apex of a zone (for example www.example.com), we walk up to the enclosing zone. Each nameserver's IPv4 and IPv6 addresses are resolved. The DNS provider of record is identified by matching nameserver hostnames against a maintained list of DNS providers. When none matches, we look up who the nameserver's IP address is registered to, using RDAP.
How to read the results
- DNS provider of record is the company running the authoritative DNS, which is where record changes must be made. It's often different from the registrar and from the web host.
- Nameservers lists each host with its addresses. Every nameserver should resolve, and there should be at least two.
- One /24 network means every nameserver sits in a single IPv4 /24, so one routing failure could take them all down. Large managed providers use anycast and separate networks, so this is mostly a concern for self-hosted DNS.
- More than one provider is either deliberate redundancy (both serve identical zones) or a half-finished migration. Compare records at each provider.
- No IPv6 addresses means IPv6-only resolvers can't reach the zone directly. Most still work through dual-stack resolvers.
- NS TTL is how long resolvers may cache this set of nameservers. Delegation changes at the registrar are also cached at the parent zone, for two days in .com.
Common situations
"I changed records but nothing happened." Check that the provider of record is where you made the change. Domains often move DNS providers while staff keep editing the old one.
Planning a move. The nameserver migration guide covers copying the zone, DNSSEC, and how long to keep the old provider running.
Updated 26 October 2026