Public IP Lookup

What This Information Means

Public IP: The Address Websites See

The public IP is the address our API identifies from this request, not your device’s address on the local network. First, check and note the result without a route connected. Then connect to a route in your target region, return to this page, and check again to see whether the address and location have changed.

A changed address can help confirm that the browser request is using a different exit, but an unchanged address alone doesn’t mean the connection failed. Split tunneling may send requests to this site over your local network, and apps may use different proxy settings. Check the client’s mode and whether the target app can connect as expected.

Country / Region and ISP: Clues About the Exit

Country and region data comes from IP geolocation databases and may differ from the actual location or route name. Database updates can lag, so results aren’t suitable for precise location tracking. ISP identifies the provider or address operator associated with the database entry; it may not be the provider currently serving your connection.

A matching location doesn’t guarantee that streaming services or AI tools will work. Platforms may also consider account region, payment details, and their own methods for identifying IP addresses.

Proxy Status: An Indicator, Not a Security Verdict

This page displays a proxy status only when the API explicitly returns one. “No proxy detected” doesn’t mean you aren’t using a proxy or that your connection is anonymous. “Proxy detected” doesn’t indicate whether the route is secure. If the API doesn’t provide this field, the page shows “Temporarily unavailable” rather than making an assumption.

Check for DNS Leaks

DNS translates domain names into addresses that devices can connect to. Routing web traffic through your selected route doesn’t necessarily send DNS requests the same way. That’s why checking your public IP and testing for DNS leaks are different checks. This page’s API can’t identify the DNS resolvers actually in use.

1. Check which traffic the client handles. See whether you’re using system proxy, split tunneling, or tunnel mode, and check whether the client handles DNS settings. If you only change your browser’s proxy, other apps may continue using their existing DNS path.
2. Check your browser’s DNS settings. The browser’s secure DNS settings may differ from your system or client configuration. Compare them with the client’s documentation to confirm the expected path. A different provider name alone doesn’t prove a leak, and you shouldn’t disable secure settings without a clear reason.
3. Use actual DNS evidence. If your client provides DNS logs or diagnostic tools, check the lookup records for the target domain, resolver source, and routing rules. Don’t treat the ISP field on this page as your DNS provider, or cached records as new requests.
4. Check each app separately. Verify the proxy settings for your browser and target app. If you’re still unsure, describe your system, client mode, and reproducible symptoms in a support ticket in the dashboard. Include diagnostic details with sensitive information redacted.

Whether a leak exists depends on the expected DNS path. This page doesn’t run a separate DNS probe or report a result such as “Test passed.”