Check the public address, location, and ISP used by the current request. Run the check again after connecting to a route to confirm that traffic is leaving through the expected endpoint.
A single result describes only the network exit used when the current request reached the lookup endpoint. When verifying a connection, compare the fields for consistency rather than relying on just one.
Your public IP is the address that target websites can typically see. Run a check before and after enabling a route; if the address changes, the page request may have switched to a new network exit. When per-app rules are enabled, verify the result separately in the relevant app.
Location data comes from network registration records in IP address databases and can help show whether the exit region broadly matches the selected route. Databases may update slowly, and city-level results can point to an ISP data center, so treat them as a route-checking reference rather than precise location data.
The ISP field identifies the network organization or provider associated with the exit address. After switching routes, the ISP and IP usually change together. If the IP has changed but app access still behaves unexpectedly, check split-routing rules, the scope of the system proxy, and the DNS resolution path.
Proxy detection is a classification returned by the GeoIP endpoint and reflects only how the address database labels the current exit. Different services may use different databases and update schedules, so this result does not replace a target service’s own regional assessment.
A correct public IP does not guarantee that DNS queries use the same path. A DNS self-check should compare the resolution results with the current route, system settings, and per-app rules.
First, save the IP, country or region, and ISP shown on this page. Use them as reference points when checking the resolution path later.
Record the result once with the route disabled, then enable the target route and run the check again. Confirm that the exit details have changed before opening the app or website you want to verify.
Review the system DNS, the browser’s secure DNS, and the client’s DNS takeover settings. When several layers are configured, avoid overlapping rules and re-establish the connection after making changes.
Per-app mode may send the browser, command line, and other applications through different exits. Repeat the test target in each app you actually use instead of judging all traffic from the browser result alone.