This page reads publicly visible connection details from an endpoint on this site. Run the check before and after connecting to an international route to confirm whether your public location has changed.
We couldn't retrieve your current network information. Check your connection and try again. This page does not connect to third-party public lookup services.
Result guide
GeoIP results can indicate the approximate location and network ownership of a public exit, but they are not precise location data and cannot independently confirm the privacy of the entire connection path.
This is the public network address that websites typically see. Without an accelerated route, it is generally assigned by your current access network; after connecting to a route, it usually becomes that route's exit address. Different results before and after the check indicate that the public exit has changed.
The location comes from an IP address database and represents an inferred registration location for the network resource. It may correspond to a data center, an ISP's registered address, or the region where an exit node is located, not the precise location of your device. Database updates can lag, so newly assigned ranges may temporarily show an older region.
The ISP field indicates what type of network organization provides the exit range. After connecting to a route, it may show a data center, backbone network, or another network organization. It helps assess the exit's source, but organization names may vary between databases.
This field only displays the detection result returned by this site's GeoIP endpoint. Detection generally relies on range attributes and database labels, which may be missing or updated late. Therefore, “not detected” is not a complete privacy assessment, and “detected” does not mean the connection is malfunctioning.
DNS check
When you visit a website, its domain must first be resolved to a reachable address. If web traffic passes through the selected route while domain lookups are still handled by the resolver on your original access network, the exit location and DNS resolution path may not match.
This page's GeoIP endpoint checks only the public exit and does not actively run multiple DNS probes, so a single IP lookup is not presented as a complete DNS test. For a self-check, review the client configuration, system resolver settings, and actual changes before and after connecting.
Check whether the current configuration routes domain resolution through the selected route, and make sure split-routing rules do not send related lookups back to the original access network.
If you use a trusted DNS testing tool, compare which resolver handles requests before and after connecting to the route rather than looking only for a particular region name.
Some browsers can use their own secure DNS configuration. This may bypass the system's default resolution path, so check it together with the client's split-routing behavior.
If old results still appear after changing routes, reconnect first, then clear the DNS cache retained by the system or browser and check again.
Privacy note
This site does not record the results of queries made on this page. Your browser requests current network information only from the same-domain GeoIP endpoint; the result is used for display and copying on this page. If the endpoint is unavailable, the page shows “Unable to retrieve information” directly and does not switch to a third-party public lookup service.