View the network information exposed by your current connection. Results come from a same-origin diagnostic endpoint and help verify your public IP, location, ISP, and proxy status.
Each field describes only one part of the connection. To determine whether the route changed successfully, check the public IP, location, and ISP together.
The public IP is the network address visible to the destination website. If the address changes before and after connecting to a route, the browser request may be leaving through a different exit. Shared networks, carrier networks, and proxy routes can all affect this field.
The location comes from an IP address database and does not represent the device’s precise position. After switching routes, use this field to confirm that the current exit is in the selected region. Database updates can lag, and nearby regions may be shown for border areas.
The ISP field identifies the network organization associated with the public address. It can help distinguish a local access network, a data center route, or another network exit. Organizations may be abbreviated differently across databases, so check this together with the location field.
This status indicates whether the diagnostic endpoint detected proxy characteristics. Database labels can be affected by shared exits, data center addresses, and update cycles. “Detected” and “Not detected” are reference signals only and should not be used alone to judge connection quality.
Your public IP and DNS resolution are related but separate paths. A changed public IP does not mean DNS requests are taking the same route. This page does not fabricate DNS test results or connect to third-party public lookup services.
After connecting to the selected route, refresh this page and confirm that the public IP and country or region match the expected route. If the original network information still appears, check the client connection before assessing DNS.
Check whether DNS settings in your browser, operating system, and client override one another. When a browser uses its own encrypted DNS, resolution requests may not follow the settings provided by the client.
You can temporarily disable the browser’s independent DNS, reconnect to the route, and clear the local DNS cache before checking the public exit again. If the issue continues, try another route tier or review the client configuration.