Reads the IP address, location, ISP, and proxy status of your current network connection. The check contacts only this site's GeoIP API and shows a failure status if the API is unavailable.
These results show which network exit your current browser request is using. They are useful for comparing before and after connecting, but they do not by themselves represent the speed, stability, or privacy of the full connection.
Websites will typically see the address shown here. After connecting through an international route, run the check again and compare the address and location. If nothing changes, first confirm the client connection status, then check whether the browser is using a different network path.
The location comes from GeoIP data and reflects the registered or inferred location of the address range, not the device's precise location. Databases may update with a delay, so the city or region may differ from the route label. Consider it together with the public IP.
The ISP field identifies the network organization associated with the current address range. Before connecting, it usually shows the local access network; afterward, it may show the data center or network operator used by the route's exit.
Proxy detection is a reference result provided by the GeoIP API based on address attributes. “Not detected” does not prove that no intermediary is present, while “Detected” does not mean the connection is malfunctioning. To verify that a route is active, first compare the public IP with the expected region.
A changed public IP does not mean that DNS queries use the same path. If DNS requests are still handled by the original access network, another resolver may receive the domain information for the sites you visit.
This page's GeoIP API returns network exit information only; it does not pretend to be a DNS test. A complete self-check requires reviewing the client settings, system DNS configuration, and the resolver actually handling requests.
Open the network or DNS settings in your client and confirm that domain resolution follows the current route instead of continuing to use the default configuration of the original access network.
After switching routes, the browser and system may continue using cached results. Close related pages, clear the DNS cache, and start the request again.
Check the DNS service's network ownership in your system network information or a trusted resolution diagnostic tool. If it still points to the original access network, return to the client and review its DNS control settings.
Disconnect the current route, reconnect through another available route, and compare whether the public IP and DNS resolver location change consistently.