What is my DNS? DNS Lookup

What Is My DNS Lookup

What this DNS lookup shows

This page reports the DNS resolver that the Newisty server used when it made the request. It shows the resolver IP, its approximate location, the network or organization behind it, and a map. It also lists flags such as mobile, proxy, VPN and hosting when the geolocation provider returns them. It is a diagnostic view of the server's DNS path, not a scan of your device or your home router.

It is not your visitor DNS resolver

A browser does not normally tell a website which DNS resolver the visitor used. This page therefore cannot show the resolver on your laptop, phone or office network. The lookup runs from the server, so the result describes the server's environment. That distinction matters when you are troubleshooting a local DNS problem. Use a command-line lookup on the affected machine if you need that machine's resolver.

How the lookup works

On page load, and when you press the refresh button, the server asks a public DNS echo service for the resolver IP. It then geolocates that IP through a provider with fallbacks. The result is cached for about an hour to avoid repeated external requests. If a provider is unavailable, the page may show a partial result or an error. The page does not accept a domain name or an arbitrary IP address.

What a DNS resolver is

A resolver is the service that turns a domain name into an IP address. Your device may use a router, an ISP resolver, a public resolver or a company DNS server. Different resolvers can return different answers because of caching, filtering or geo-routing. The resolver shown here is simply the one the server used for its own lookup; it is not a recommendation or a security rating.

Location and network fields

The page may show a country, region, city, ISP, organization and timezone for the resolver IP. These values are approximate. A resolver can be registered in one place and serve traffic in another, and geolocation databases are not always current. Treat the map as a rough indication, not a precise address. The coordinates are for the network, not for a person.

Flags and their limits

Mobile, proxy, VPN and hosting flags come from the geolocation provider. A hosting flag often means the IP belongs to a data center, which is common for public resolvers. A VPN flag does not prove that a person is using a VPN, and the absence of a flag does not prove they are not. These fields are informational and should not be used as a security decision on their own.

The map

The map is a visual aid based on the resolver coordinates. It is not a live network map and it does not show the route between the server and the resolver. If the coordinates are missing or inaccurate, the map may be blank or point to a generic location. Use the textual fields as the primary result and the map as context.

Caching and freshness

Results are cached for roughly an hour, so a refresh may return the same data even if the server's resolver changes. The cache reduces load on the external providers but means the page is not a real-time monitor. If you need a fresh lookup, wait for the cache to expire or use a local DNS tool. The page also depends on the external provider's availability.

Accuracy and limitations

The page displays an accuracy field, but the current implementation does not supply a meaningful value. The resolver IP is the most reliable part of the result. The location, ISP, organization and flags are estimates from a third-party database. The page does not perform a reverse DNS lookup, does not test DNS filtering and does not measure resolution speed. It is a lightweight diagnostic, not a full DNS analysis suite.

Privacy and server requests

The lookup happens on the server, so your browser does not contact the resolver directly. The server contacts a public echo service and a geolocation provider. The page does not ask for your IP address or a domain name. Standard server logs may still record the request. Do not treat the page as anonymous network testing.

Common problems

If the page shows an error, an external provider may be unavailable or rate-limiting the server. If the location looks wrong, the geolocation database may be outdated or the resolver may be registered elsewhere. If the flags are missing, the provider did not return them. If the map is blank, coordinates may be absent. Try the refresh button after a few minutes.

When to use it

Use it to see which resolver the server environment uses, to sanity-check a hosting or data-center network, or to learn how resolver geolocation looks. It is also a simple demonstration of how a DNS echo service works. For troubleshooting a visitor's DNS, use a tool that runs on the visitor's device or a command such as dig or nslookup on the affected machine.

What not to do

Do not describe the result as the visitor's DNS resolver. Do not use the location as proof of a person's whereabouts. Do not treat a VPN or hosting flag as a security verdict. Do not rely on the page for real-time DNS monitoring. Do not enter a domain name; the page does not resolve arbitrary domains.

Resolver versus authoritative DNS

The resolver is the service that looks up an answer on your behalf. The authoritative nameserver is the source that holds the zone data. This page reports the resolver, not the domain's authoritative server. It does not show A, AAAA, MX or TXT records. Use a DNS record lookup for those. Keeping the two concepts separate avoids blaming the wrong part of the DNS chain.

Frequently Asked Questions