NET-CHECK · Public IP Detection
Reads the IP, location, ISP, and proxy detection fields visible to the outside world for the current request. Results come from an OvVPN same-origin endpoint, not a third-party public lookup service.
SHEET-01 · Lookup Results
A same-origin lookup starts automatically when the page loads. After reconnecting to a route, select “Run Check Again” to retrieve updated public network details.
CHECK / CURRENT ROUTE
Reading current public network details
Data channel: OvVPN same-origin GeoIP endpoint
SHEET-02 · Field Guide
The results describe the network exit presented by this web request, not the device’s local network address.
FIELD · IP
This is the public address seen by the website server when it receives the request. After switching routes and running the check again, a changed exit will usually show a new address here. If the result stays the same, first confirm the connection, then check whether the browser is still using the original network.
FIELD · GEO
The location comes from an IP address database and describes the region where that address is generally registered or assigned. It does not indicate the device’s precise location and may be inaccurate because of ISP address allocation, database update timing, or exits serving multiple regions.
FIELD · ISP
The ISP field identifies the network organization associated with the public address. Some results may show a carrier, data center, or autonomous system name. If the endpoint returns no identifiable field, this page will clearly show “Temporarily unavailable.”
FIELD · PROXY
This field displays only the identification returned by the detection endpoint. Databases may classify shared exits, data center networks, and proxy characteristics differently, so use the result as a troubleshooting clue rather than as the sole basis for judging connection quality or account region.
SHEET-03 · DNS Check
Your public IP and DNS requests are two separate paths to observe. This page’s GeoIP result can confirm only the exit used by the web request; it cannot by itself prove that DNS requests use the same route.
In a trusted local network testing environment, record the current DNS resolver and its region as a baseline for comparison. Do not paste account credentials, subscription details, or other sensitive information into unfamiliar testing pages.
After the connection is established, refresh this page and confirm that the public IP matches the target region; then check the DNS results again. Compare the resolver, region, and whether records from the original network still appear.
Disconnect the current connection first, then select and connect to a route again. Close pages that may retain old DNS state and reopen the browser for another check. You can also review custom DNS settings, browser Secure DNS, and local network configuration.