Read the address, location, and ISP information exposed by your current network request to confirm that the public exit matches your expectations. Results come from this site’s same-domain lookup interface and are not routed through a third-party public service.
NETWORK OBSERVATION
Once the lookup is complete, you can copy the current public IP.
This page works in modern browsers on Windows / macOS / iOS / Android / Linux and displays the public network details used by the browser’s current request.
READOUT GUIDE
Each result answers one specific question. To assess the connection, compare the public IP, location, ISP, and the target service’s actual behavior together.
This is the public address seen by websites. Run the check again after switching routes. If the address changes with the route, the browser request is using a new network exit. If it stays the same, first check the client connection status, per-app rules, and browser proxy settings.
The location comes from an IP geolocation database and is an inference based on address registration and network position, not the device’s precise location. Databases may update at different times, so city or region results can be inaccurate; use the target service’s result as the reference.
The ISP field usually identifies the network operator or autonomous system organization associated with the public address. It helps distinguish a local network exit from a route exit, but the name may appear as an English abbreviation, a corporate group, or a data center registration name.
The proxy field is an identification signal returned by the interface based on address attributes and should be treated only as a supporting reference. A result showing no proxy does not mean every website will reach the same conclusion; services may use different address databases, risk rules, and update schedules.
DNS ROUTE CHECK
DNS converts domain names into network addresses. Even when the public IP changes, DNS requests may still use the local network or the browser’s own resolution path, so the result above alone cannot confirm whether DNS traffic is following the expected route.
During a self-test, check the DNS resolvers shown in your system, browser, or client network diagnostics and record the results before and after connecting. If the resolver does not change afterward, or still clearly points to the original network provider, review the client’s DNS takeover option, the browser’s Secure DNS setting, and per-app rules.
Before enabling the accelerated connection, record the current DNS resolver and public IP in your operating system or browser network diagnostics as a baseline.
After connecting, refresh this page and confirm that the public IP and country or region have changed, then check the DNS resolver information again.
If the public IP changed but DNS still follows the original network path, check the client DNS settings, the browser’s independent resolution settings, and whether the current app is excluded by routing rules.