Public IP lookup
See the address your browser is currently using online. After connecting or switching routes, run the lookup again and compare results. This shows the exit IP for this request, not the route used by every app.
Current exit details
Waiting for lookup- Public IP
Temporarily unavailable- Country / Region
- Temporarily unavailable
- Network provider / ISP
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
Enable JavaScript to look up your current exit details.
Location and proxy detection rely on IP databases, which may be out of date or inaccurate. This page does not automatically check for DNS leaks.
What this information means
Public IP and reported location
Your public IP is the address used when this request reaches the lookup service. It may belong to your local network or the route you selected. It is not your device’s address on your local network.
The country or region is a database estimate for that address, not your device’s precise location. If the reported location doesn’t match the route name, first check your client’s selected route, then confirm your browser is using the expected rules. Don’t judge whether the connection is working based on the location label alone.
ISP and proxy detection
ISP refers to the internet service provider or network organization associated with an address. When using an international route, this may show the network organization of the exit data center rather than your local broadband provider.
“Proxy detected” is a detection result, not a connection quality score. “No proxy detected” doesn’t prove your traffic isn’t using a proxy. If the API can’t provide a clear result, this page shows “Temporarily unavailable” rather than treating an unknown result as a negative.
To verify a connection, save the results from before connecting, then connect to a route and run the lookup again. A changed address can help confirm that your browser’s exit has changed, but you should also check the apps you actually use to verify how their traffic is routed.Read the connection check guide →
How to check for DNS leaks
DNS translates domain names into network addresses. A change in your public IP doesn’t mean DNS queries are using the same route. If your client is supposed to handle DNS but queries are still going to your local network’s resolver, investigate further.
- Check what you expect first. Review your client’s DNS, routing, and system proxy settings. Determine whether it only proxies browser requests or handles traffic for the whole device. Depending on the mode, local DNS resolution may be part of the intended setup.
- Then check actual DNS resolution. If you need to test, choose a trusted DNS testing tool and compare the resolver and its reported location before and after connecting. The tool will receive test requests, so review its privacy policy before use. This page does not automatically send requests to external testing services.
- Review your browser settings too. Secure DNS, custom resolvers, and other network extensions can affect the results. Follow your client’s documentation to resolve conflicting settings, reconnect, and test again. Don’t draw conclusions based only on a reported location.
- Check each app separately. Browsers and other apps may use different DNS resolution methods. If only one app has an issue, check its proxy rules, cache, and connection status individually.
This page’s GeoIP lookup only returns information related to your public IP. It doesn’t provide DNS test results, so it can’t confirm that you’ve passed a DNS leak test.
Read the connection and troubleshooting FAQ →