Public IP
Target websites will typically see this address. Run the lookup again after switching routes; if the address and ownership details change, the current request is using a different network exit.
Reads the IP address, country or region, ISP, and proxy detection result shown for the current connection. Data is returned only through this site's same-origin endpoint; no external public service is used if the endpoint is unavailable.
The lookup runs automatically when the page opens. After switching routes or networks, run it again to compare the public connection details.
The result shows the network exit presented by the current request. It can help verify whether a route switch took effect, but it does not by itself indicate connection quality or privacy status.
Target websites will typically see this address. Run the lookup again after switching routes; if the address and ownership details change, the current request is using a different network exit.
The location comes from an IP address database and is not the device's precise location. Data-center exits, the ISP's registered location, and the actual access point may differ; rely on the target service's own identification.
The ISP field identifies the network organization associated with the address range. It can help determine whether the exit belongs to a local access network, a cloud network, or another network operator.
This field shows only the classification returned by the endpoint. Network databases may be updated with a delay, so use it as a troubleshooting clue rather than the sole basis for judging connection status.
Even when the public IP changes, domain lookups may still follow a different network path. Assess the public IP and DNS results together.
Run the lookup on your original network and note the IP ownership details as a baseline for comparison.
Confirm that the public IP and country or region match the selected route, then continue checking the domain lookup path.
Review the DNS settings in your operating system or browser's network diagnostics. If the resolver still points to the original access network, check the client's global connection, DNS handling, and per-app rules.
After changing the configuration, disconnect and reconnect to the route, then compare the public IP and DNS details again. Refresh the browser's existing DNS cache before checking once more.