Read the IP, country and ISP shown to websites by your current connection to confirm whether a route change has taken effect. Proxy detection is based on network ownership data and is provided for troubleshooting only.
Reading information through this site's network interface.
The results show the network exit point visible to websites. They do not equal the device's actual location and cannot, by themselves, prove that all traffic uses the same path.
Your public IP is the address shown to the internet when this browser makes requests. If the result changes after connecting to a route, browser requests are usually leaving through the new network exit. If the original address still appears, disconnect and reconnect, close pages that may be keeping old connections open, and run the lookup again.
The country or region is inferred from IP ownership databases and is useful for confirming the exit area's approximate location. Some data-center addresses may have different registration, operating and actual access locations. Judge the result together with the route name selected in the client, and do not treat city-level results as precise positioning.
The ISP field shows the operator, network organization or autonomous system associated with the address. Residential broadband usually shows the access provider, while data-center routes may show a facility or network provider. Use this field to help identify the exit type; it does not indicate the operator of the subscription service.
Proxy detection is an ownership-data assessment of the current address type. A data-center exit may be flagged as a proxy without indicating a connection problem; no detection does not provide extra privacy assurance. If a platform behaves unexpectedly, check the exit region, route type and the platform account's region together.
An IP lookup can confirm only the exit used for web requests. DNS queries may be handled by the system, browser, client or custom resolver settings, so they require a separate check.
First check whether the current connection configuration routes DNS through the encrypted route. If the client offers system proxy, global or rule-based modes, confirm that the active choice matches your expectations. This helps prevent web traffic from using the route while DNS requests continue over the original network.
System network settings, secure DNS in the browser and client configuration may all specify how DNS is resolved. When multiple settings override one another, the result may differ from expectations. During troubleshooting, keep one clear configuration, reconnect, and test access again.
After switching routes, open web connections and the local DNS cache may temporarily retain old results. Close the relevant pages, reconnect and refresh this page, then compare the public IP with the region reported by the target website.
Rule-based mode may send different websites through different exits; this is expected behavior and is not necessarily a leak. To verify a service's path, check the split-routing rule matched by its domain and review the actual exit in the client's connection log.
This page reads only the exit information for the current web request through this site's GeoIP interface. It does not call external DNS probes or invent DNS conclusions from the IP result. The country and ISP shown here can verify the exit, but cannot replace the client's DNS diagnostic logs.
This site does not record the IP lookup results shown on this page. The interface response is used only for display on the current page; page scripts do not write the result to local storage or send it to a third-party public lookup service. After the page is refreshed or closed, this tool does not retain the displayed content.