Current Results
- Public IP
- Checking…
- Country or region
- Checking…
- ISP
- Checking…
- Proxy detected
- Checking…
View publicly available information about your current network exit to confirm whether the route is active, the exit location matches your expectations, and the identified ISP is correct.
Each field answers a different question. When troubleshooting a connection, first verify the exit address, then review the location and ISP.
This is the public address websites see; it may differ from your device's address on a local network. If the public IP changes after connecting to a route, browser traffic is usually using a new network exit. If it stays the same, check the client connection status, system proxy settings, and whether the browser is reusing an existing connection.
The reported location helps determine whether the exit position matches the selected route. Database results may be grouped by IP registration data or network operator records, so the city shown can occasionally differ from the actual data center. For confirming a route, the country or region is usually more useful than the specific city.
The ISP field identifies the network organization associated with the exit address. It may be a residential broadband provider, mobile network, cloud network, or data center. Some websites assess risk using both the network organization and access behavior, so different routes in the same region can produce different login or access results.
This result indicates whether the lookup interface identified common proxy-network characteristics. It is not a score for speed, stability, or account security, and it cannot by itself confirm that DNS is configured correctly. When troubleshooting a specific service, also check the exit location, client rules, and DNS resolution path.
The public exit IP and DNS resolution follow two different information paths. This page can read the public exit address, but the exit IP alone cannot show who ultimately handles DNS requests. For a proper check, review the exit location, DNS resolver, and client settings together.
Confirm in the client that the route is connected, then return to this page and run another check. Record the public IP, country or region, and ISP as a baseline for comparison.
Use your system or browser's built-in network diagnostics to view DNS resolution details, focusing on the resolver's network and region. Do not compare names alone; the network organization and geographic location matter too.
If the resolution path does not match expectations, check the client's DNS mode, custom system DNS, and browser Secure DNS settings. After making changes, disconnect the old connection and reconnect before comparing the results again.