Public IP Check

What this information means

Public IP and location

Your public IP is the address our site sees for your request, not your device’s address on the local network. Location data comes from an IP database, so it may differ from the region shown for a route or your device’s actual location. It can’t pinpoint your exact location.

First, note the results before connecting. Then connect to the route you want to check and run the test again. If your IP hasn’t changed, check that your client’s system proxy is enabled and that its current rules send requests to this site through that route. In rule mode, different sites may use different exit IPs; this result doesn’t verify the connection in another app.

ISP and proxy detection

ISP usually refers to the network provider associated with the exit IP. The result may show a data center or upstream network rather than your current internet provider. Proxy detection also relies on database records and flags supplied by the API.

“No proxy detected” means only that this API didn’t flag the exit IP in this check. Other platforms may reach a different conclusion. “Temporarily unavailable” means the API didn’t return usable fields; it isn’t a negative result and doesn’t indicate whether your connection is secure.

How to check for DNS leaks

DNS translates domain names into network addresses. Routing web traffic through a proxy doesn’t automatically route DNS queries the same way. This page checks the exit IP for HTTP requests only; it doesn’t run a DNS leak test or mark any result as “DNS test passed.”

1. Check your client’s DNS settings.Open the client’s connection settings and check whether it handles DNS, and how DNS queries are routed in rule mode. Don’t assume DNS follows the expected route just because the client shows as connected.
2. Check your browser’s Secure DNS settings.Your browser may use encrypted DNS settings separately from your operating system. Check your client’s documentation to see how the two work together. Encrypted DNS and whether queries follow the expected route are separate issues.
3. Compare DNS resolvers before and after connecting.If you use a test tool that shows the DNS resolvers actually handling your queries, note the results before and after connecting. Check whether the resolvers’ networks match your configuration. A difference between the resolver’s location and your exit location doesn’t, by itself, prove a leak.
4. Check again in the app you’re using.An app may resolve domain names on its own or reuse existing connections and cached data. After changing settings, restart the app and test again so you don’t mistake an old session for the result of your current configuration.

For further troubleshooting, start with the Quick Start Guide and FAQ. When submitting a support ticket, include your platform, connection mode, route name and a description of the issue. Don’t attach your full subscription link or account credentials.