How to use Nameserver Lookup
- Enter the domain nameType the domain, for example example.com, into Domain name, without https:// or a path.
- Run the lookupPress Run Nameserver Lookup. The tool reads the domain’s NS, A and AAAA records and looks up the reverse DNS name of each address.
- Read the resultsNameserver rows show who runs the DNS. IP address and Reverse DNS rows show where the domain points, and Likely host appears when a reverse DNS name belongs to a known provider.
Common uses
- Finding out which DNS provider manages a domain
- Checking that a nameserver change at the registrar is visible
- Getting a domain’s IP address to research where a site is hosted
Frequently asked questions
How do I use Nameserver Lookup?
1. Enter the domain name: Type the domain, for example example.com, into Domain name, without https:// or a path. 2. Run the lookup: Press Run Nameserver Lookup. The tool reads the domain’s NS, A and AAAA records and looks up the reverse DNS name of each address. 3. Read the results: Nameserver rows show who runs the DNS. IP address and Reverse DNS rows show where the domain points, and Likely host appears when a reverse DNS name belongs to a known provider.
Does this tool tell me who hosts a website?
Often, but not always. The tool lists the nameservers, the addresses the domain points to and their reverse DNS names, and names a likely host when a reverse DNS name belongs to a known provider such as Amazon Web Services or Hetzner. It does not look up IP ownership or ASN.
How can I get closer to the actual host?
If no likely host is shown, look up the owner of the IP address with a WHOIS or IP lookup service. If the site sits behind a CDN or proxy, the address belongs to the CDN, not to the origin server.
Why do the nameservers differ from what my registrar shows?
The tool shows what DNS currently answers through the GigaTools server’s resolver. After a nameserver change, cached answers take time to expire, so old values can still appear for a while.
Is the lookup stored or limited?
The domain is sent to the GigaTools server, which runs the DNS queries and returns the records without saving them. Because the work happens on the server, runs pass an automatic bot check and count toward a daily per-IP limit.