Reads the exit information shown by the current network request to verify whether a route switch took effect, whether the region matches expectations, and how the ISP is identified.
The public IP is the network address a website sees when it receives a request. Check it before and after connecting a route. If the address or mapped region changes, the request is usually being sent through the new exit. If nothing changes, first confirm the client connection, then check whether the system proxy or global routing is enabled.
The country or region is mapped from an IP address database and is useful for estimating the exit location. Address reassignments, ISP updates, or changes to data-center registration can make the displayed result differ from the server’s actual location. If the region is unexpected, reconnect through another route in the same region and check again.
The ISP field typically identifies the carrier network, cloud network, or data-center organization associated with the address range. It helps identify the exit source, but does not indicate route quality, bandwidth, or access capability. If the field is unavailable, this page shows “Temporarily unavailable” rather than filling in a guess.
“Proxy detected” comes from the identification field returned by the GeoIP API. “Detected” means the database has classified the current exit as a related network type; “Not detected” only means this response contained no matching indicator. If the API does not provide the field, this page keeps the status unknown instead of inferring an answer.
This page checks the public IP and does not directly enumerate the DNS resolvers in use on the device. Follow the steps below to check whether the resolution path matches the selected route.
Before connecting to an accelerated route, review the DNS addresses configured on the operating system or router and record the public IP. This baseline supports later comparison and prevents existing network settings from being mistaken for route configuration.
After connecting, return to this page and run the check again to confirm that the exit country or region matches the selected route. If the exit is unchanged, resolve the routing handoff issue before checking DNS; otherwise, the two issues can be confused.
Review the system network settings, browser secure DNS settings, and router configuration to see whether they specify different resolution services. When several settings apply, use the one with the effective priority, then reconnect the route after making changes.
If the resolution region remains inconsistent with the exit, disconnect and switch to another route, then clear the system DNS cache or restart the network connection. On the next check, verify the public IP, mapped region, and local DNS settings together.
VzVPN does not record the results from this page. Detection requests are sent only to the same-site GeoIP API to return the current public IP, mapped region, ISP, and available proxy indicators. This page does not forward lookups to third-party public IP services or keep the results stored in the browser long term.