Public IP and location lookup

What the results mean

Public IP: where your request comes from

Your public IP is the source address seen by our API. Check it once before connecting, then check again after connecting to a route and compare the results. If the IP changes, this browser request is using a different exit. If it doesn’t, first check your client’s connection status and whether your browser is covered by the current routing rules.

With split tunneling, different websites may use different routes. A direct connection to this lookup page doesn’t necessarily mean your target app is also connecting directly. Likewise, a change to the IP shown here doesn’t prove that every app is using the selected route. See the Getting Started Guide and check from the app you’re using.

Country, region, and ISP: approximate network details, not precise location

Country and region data comes from IP geolocation databases and may be inaccurate due to address allocation changes or database updates. The ISP identifies the network provider associated with the address, but may show the name of a data center or address holder instead. It may not match the route name shown in your client. Don’t rely on geolocation alone to determine a device’s location or a website’s region.

Proxy detection: what the API reports

This page shows “Proxy detected” or “No proxy detected” only when the API explicitly returns a result. If the field is missing, it shows “Temporarily unavailable” rather than treating an unknown result as negative. Proxy detection can be inaccurate. “No proxy detected” does not guarantee any particular level of privacy, nor does it indicate whether Streaming or AI Tools will work.

How to check for DNS leaks

Checking your public IP and testing DNS are two different things. This page doesn’t run a dedicated DNS test, so its results alone can’t confirm whether DNS is leaking.

DNS translates domain names into network addresses. Routing your connection through a selected route doesn’t automatically mean DNS requests take the same path. System resolver settings, browser Secure DNS, DNS handling in your client, and routing rules can all affect where DNS requests go.

Check your settings, then verify what happens

1. Open your client settings and check DNS handling and routing rules. Follow the client’s documentation; a system proxy setting does not necessarily route all traffic.
2. Check your browser’s Secure DNS settings and compare them with your client configuration. If they differ, confirm what each setting does before changing anything, so you can tell which setting is taking effect.
3. Reconnect to the route and reopen the app you’re testing. If needed, clear the DNS cache as described in your operating system’s documentation, then compare how things work before and after connecting.
4. To confirm where DNS requests are going, use a dedicated tool that reports the DNS resolvers or check your local diagnostic logs. A difference between the resolver’s region and your exit region is a clue to investigate, not proof of a leak.

If your client says it’s connected but a website still won’t load, see the Guide to Checking Your Public IP, DNS, and Per-App Routing. For help, open a ticket through the support portal and include your platform, route type, and error message. Redact account credentials and subscription details before submitting.