Public IP and location

What these results mean

Public IP: the address websites see

Your public IP is the address shown to websites for this check, not your device’s address on the local network. After switching routes, check again. If the address changes, this browser request is using a different public IP. If it doesn’t, check the proxy mode, routing rules, and whether the browser is reusing an existing connection. This result alone can’t tell you whether the entire client is working.

Location and ISP: address records, not precise location

The country or region is usually based on IP address databases and may not match your device’s actual location. The ISP field may show the provider, data center, or organization associated with the public IP rather than the network you’re currently connected to. Data sources and update schedules vary, so different platforms may identify different locations.

Proxy detection: an indicator, not proof of routing

This page shows a proxy status only when the API explicitly returns one. If no detection data is available, the result will say “Unable to check right now” rather than treating it as “No proxy detected.” Even a “No proxy detected” result doesn’t prove that your traffic isn’t using a proxy or that another platform will reach the same conclusion.

Verify a connection by checking both changes to your public IP and how the target app behaves. A single IP address or detection label can’t prove that all traffic uses the same route.

DNS leak checks

DNS translates domain names into addresses that devices can connect to. Browser traffic and DNS requests can take different routes, so a public IP check alone can’t determine whether DNS is leaking. This page doesn’t run a dedicated DNS leak test and won’t show an unverified “passed” result.

Check the DNS resolution path

1. Review your client’s DNS and routing settings. Confirm that the client handles DNS resolution as intended, rather than relying only on a browser proxy.
2. Check your system’s DNS configuration and your browser’s Secure DNS settings. The browser may resolve domains differently from the system or client.
3. After connecting, use a trusted DNS test to see which resolvers are handling your requests, then compare the results with your client settings. The test sends requests to the testing service, so review its privacy policy first.
4. If the resolvers aren’t what you expect, resolve conflicting settings, clear the DNS cache, and test again. A resolver appearing in a different region doesn’t by itself prove a leak; consider how the DNS service is deployed.

If your browser works but other apps don’t, check those apps’ routing rules. Command-line tools, IDEs, and system services may not use the browser’s proxy settings. See how to check your public IP, DNS, and per-app connections, then troubleshoot each request path.