View the public IP, region, ISP, and proxy-detection result returned for your browser's current connection. Requests are sent only to this site's same-origin API.
NETWORK LOOKUP
Field Guide
These results describe the connection information visible to this site's servers after the current request leaves your local network. They can help confirm whether your public exit has changed, but they do not by themselves represent the actual path of all network traffic.
The public IP is the address visible to this site's API. Run the check again after connecting to or switching routes. If the address and region change as well, your browser is usually reaching this site through a new exit. If nothing changes, first confirm the client connection, then check whether split tunneling rules are enabled.
The location comes from a geographic database for network addresses and indicates the area where the address is typically registered or identified. It is not the device's precise location and may be inaccurate because of carrier address allocation or updated data-center registration details.
The ISP field identifies the network organization associated with the current public IP. Home connections usually show the access provider, while data-center routes may show a hosting facility or network operator. This field can help indicate whether traffic is using the expected route.
The proxy result simply repeats the detection status returned by this site's API. Databases use different criteria, so “Detected” does not necessarily indicate a connection problem, while “Not detected” should not be treated as a complete privacy or security assessment.
DNS SELF-CHECK
DNS translates domain names into addresses that devices can connect to. A changed public IP does not necessarily mean that name resolution uses the same route. This page does not present GeoIP data as DNS test results, so complete the check using your client settings and system network information.
Open the configuration for the client in use and check whether DNS is managed by the subscription profile or by the client itself. If custom system DNS, browser secure DNS, and client DNS are enabled at the same time, identify which setting takes priority to prevent overlapping rules.
Open your operating system's network details to see where the current DNS servers come from. Check again after switching routes to confirm that the system is not still fixed to a resolver setting inconsistent with the current network policy. Corporate networks and public Wi-Fi may also provide their own DNS rules.
Some browsers can bypass system settings and enable secure DNS independently. If only browser access behaves unusually while other apps work normally, review the browser's network and privacy settings. After making changes, fully close and reopen the browser.
After reviewing the settings, reconnect to the route, clear old DNS cache data, and visit the target service. If the exit region is as expected but domain resolution continues to fail, try refreshing the subscription, switching routes, or including the client platform, route name, and error message in a support ticket.