What this information means
Public IP: the address websites see
Your public IP is the address shown to websites for this browser request. It may belong to your local network or to the route you selected. After switching regions, wait for your client to connect, then select “Check again.” If the address hasn’t changed, make sure the client is connected and check whether your routing mode sends this page through the proxy.
Rule-based routing assigns connection paths by website or app. So, a local IP on this page doesn’t necessarily mean other websites also use your local connection; likewise, seeing a route IP here doesn’t prove every app uses that route. Check the results on the website you’re trying to access. For setup steps, see the getting started guide.
Location and ISP: identify the network behind your IP
The country or region is an estimate of where a public IP is registered, not the physical location of your device. The ISP field may show a carrier, data center, or network organization, and may not mention VPNKQ. Database updates can lag, so the displayed location may differ from your selected route. If the mismatch persists, try another route and check again.
Proxy status: an indication, not proof
“Proxy detected” means the API has flagged this IP as proxy-related. “No proxy detected” only means the API didn’t find a matching flag; it doesn’t prove the connection isn’t using a proxy. If the API doesn’t return this field, we show “Unable to retrieve” rather than treating missing data as a negative result.
These results apply only to this browser lookup. This page can’t access your client settings, so it can’t confirm device-wide routing, encryption status, or whether other apps are connected.
Check for DNS leaks
DNS translates website domain names into network addresses. An IP lookup and a DNS check are different: your browser’s website traffic may use the selected route while domain lookups take another path. This page’s API doesn’t check DNS resolvers, so no automatic DNS check is available.
Check the DNS path before deciding something is wrong
- Review the DNS and routing settings in your client to see whether your system, client, or browser handles domain lookups. Note the current settings, and avoid changing several things at once before you know what’s causing the issue.
- Check whether your browser uses its own secure DNS setting. Browser DNS settings may differ from your system or client settings; confirm that they match the routing path you expect.
- For further verification, use a trusted, dedicated DNS testing tool and note the resolver details before and after connecting to a route. External tests send separate requests, so review the tool’s privacy policy first.
- Consider the resolver’s network, your client’s rules, and what happens when you access the site. A difference between the resolver’s region and your public IP’s region isn’t, by itself, evidence of a leak; public DNS services may also use distributed infrastructure.
If a site won’t load, you see a DNS error, or you still have questions after making changes, start with the DNS and connection troubleshooting guide. To contact support, open a ticket in the user dashboard and include your device platform, client mode, a description of the issue, and redacted screenshots. Don’t include passwords or subscription links.
Privacy and lookup limitations
We don’t log queries. This page only sends requests to our GeoIP API; it doesn’t fall back to third-party public IP lookup services or save results in your browser’s local storage. When you select “Copy IP,” only the displayed address is copied—not its location or proxy status.
If the API is unavailable, results will show “Unable to retrieve.” Try again later, or rerun the lookup once you’ve confirmed your network is working. A failed request doesn’t mean your proxy has disconnected. Your public IP may still reveal information about your network location, so consider masking it before sharing screenshots. See our Privacy Policy for details.