Public IP Checker

Public IP: where this request exits the network

Your public IP is the address our API sees. When you connect through a proxy, your browser will usually show the selected route's exit address if its requests go through that route. With split tunneling enabled, different sites may use different paths, so this result doesn't represent how every app connects.

To compare, note your address while disconnected, then connect to the route you want to check and run the test again. A changed address is a sign that your exit point has changed. If it hasn't, check whether your browser uses the proxy, whether split-tunneling rules send this site directly, and whether the client is handling network traffic.

Country, region and ISP: location data from databases

The country and region show how the IP address is listed in geolocation databases; they don't indicate your device's actual location. Databases may update at different times, so websites can show different locations. The ISP field may show a carrier, data center or network organization, and may not match the route name.

If a service still shows a different region, check your account region, previous sessions and the service's own detection rules. The location shown here alone can't tell you whether streaming services or AI tools will work.

Proxy detection: an indicator, not a security verdict

“Proxy detected” means the API marked this address as proxy-related. “No proxy detected” means only that the API returned no positive flag; it doesn't prove the request connected directly or establish your level of anonymity. If the API can't make a clear determination, this page shows “Temporarily unavailable” rather than guessing based on the ISP name.

For help troubleshooting an app connection, read Troubleshooting. To compare available regions, see the route list.

First, check how your client handles DNS

Open your client's DNS and split-tunneling settings. Check whether domain lookups for international sites are routed through the proxy as expected. A browser proxy alone may not handle DNS requests from your system or other apps. If rules send sites in mainland China directly, using local DNS may be expected and isn't necessarily a leak.

Then check your browser and system settings

Secure DNS in your browser, custom resolvers, encrypted DNS on your system and other network tools can all change the route DNS requests take. Note these settings, then check your client’s documentation for possible conflicts. Don't disable security features just to test. Save the original settings before making changes so you can restore them.

For evidence, check the resolver—not just your IP

Use your client's diagnostics to check which resolver handled a test domain and which rule matched. If you use a dedicated DNS testing tool, review its privacy policy first. The key question is whether domain requests took the expected route, not whether the resolver happens to be in the same region as your public IP.

If you still can't determine the cause, contact support through the user panel. Include your operating system, client, routing mode and what happened. Redact your account details, full subscription link and other sensitive information from screenshots.