Connection Test
First, read the address and location details currently visible to the public network, then check whether the route matches your expectations. Results show the exit point seen by this site's API at that moment; they do not guarantee that another app uses the same network path.
After the page loads, this site uses its own API to read your current public IP details.
The results are useful for an initial check after connecting, but each field has clear limits.
This is the public address received by this site's API when it handled the request. If the address changes after connecting, the exit path used by the browser has changed. If it does not, check the client mode, routing rules, and connections already open in the browser.
Location details come from IP address mapping and are mainly useful for checking whether the exit region matches your selection. Database records may differ from the device's actual location or lag after an address is reassigned, so confirm with the target app's actual access results.
The ISP field identifies the network organization associated with this public address in registration records. It can help show which network handled the request, but cannot by itself confirm the route type, bandwidth, or access conditions for a target service.
Proxy detection is based on signals evaluated by the API. “No proxy detected” is not a privacy or security finding, and “Proxy detected” does not necessarily indicate a connection problem. The target website may use different databases and detection rules.
After the exit region matches your expectations, verify access in the app you actually plan to use. Network reachability, account region, and the target service's terms are separate conditions and should be checked independently.
This page does not run an external DNS probe. The key check is whether domain lookups follow the expected route, not simply whether the client shows as connected.
Keep the client connected and run the check above again. If the public IP does not match the expected region, fix the route selection or split-routing settings before checking DNS.
Open the detailed settings for the device's currently active network and check whether DNS is assigned automatically, set manually, or controlled by the client. If it still uses the resolver addresses provided by the original network, review the client's DNS mode and the system network settings.
Connections already established in the browser or the system DNS cache may continue using an old path. Close and reopen the target app, switch networks once if needed, then compare the public IP details with the actual access result.
If the issue occurs only in a particular browser, app, or network environment, record the selected route, client mode, and reproduction steps. Once the conditions are clear, adjust routing or DNS settings rather than changing several configurations at once.
For further help tracing the connection path, read the Guides; to review available regions, see the Node Index.
Results are displayed only on this page. VPNLZ does not log lookups or save results in browser storage. The browser requests only this site's same-origin GeoIP API; if it is unavailable, the page shows “Temporarily unavailable” instead of switching to a third-party public lookup service.