What these results mean
Public IP: the address websites see
The public IP shown is the address our lookup API detected when it received your request. It is not your device's local network address. Your browser's public IP may change when you connect through a route. Check it before connecting, then connect to your chosen route and check again. If the address hasn't changed, check whether your client rules are routing the browser request.
With split tunneling, different websites may use different routes. A change in the IP shown here confirms only the path taken by this request; it doesn't prove that other websites or apps use the same route.
Location and ISP: labels from IP databases
Country and region information comes from IP databases and may not match your actual connection location because of update delays, IP address transfers, or network deployment. It does not precisely locate your device. The ISP usually identifies the network provider or hosting network associated with the address. A data center or cloud network name does not necessarily mean there's a problem with your client connection.
Proxy detection: a useful clue, not a verdict
“Proxy detected” means the lookup API identified this IP as a proxy. “No proxy detected” means only that the API did not apply that label. Database coverage and detection methods have limits, so this result can't tell you whether your connection is encrypted or anonymous, or whether a route is suitable for a particular service. If the API returns no clear status, this page shows “Temporarily unavailable.”
DNS Leak Check
DNS translates domain names into network addresses. A changed public IP doesn't mean DNS requests are taking the expected route. This page checks your public IP only; it does not run a separate DNS leak test or treat a successful lookup as a passing DNS check.
- Check your client's DNS settings. See whether the client has a DNS interception feature enabled, and review how your current routing mode handles DNS requests. Setting names vary by client.
- Check your browser's secure DNS settings. The DNS service selected in your browser may use a different route from your system. Check the browser, system, and client settings together rather than changing just one.
- Check for other network tools. Other proxies, browser extensions, or DNS tools may affect how DNS requests are handled. Check them one at a time. After changing settings, reconnect and revisit the website you want to test.
- Review your DNS resolver details. If you use a separate DNS testing tool, check its privacy policy first. Then compare the resolver, its location, and your client's expected settings. A resolver in a different region alone does not prove there's a leak.
Lookups & Privacy
We don't log lookups. Requests are sent only to a same-origin API on this site; we don't fall back to third-party public lookup APIs. The copy button copies only the IP address shown, not the other results.
If the API is unavailable, the network is interrupted, or the response is missing required data, the page shows “Temporarily unavailable” instead of a sample address. Try again later, or select and copy the address manually if the copy button fails. Check screenshots for your public IP and network details before sharing them.
Read our Privacy Policy for information about how we handle data.