Current IP Lookup

What these results mean

Public IP: where this request comes from

The public IP is the address our API sees as the source of this request. It isn't your device's address on the local network. Devices on the same network may share a public IP. With a proxy enabled, only apps that follow its rules may use the new route. These results reflect only this browser's connection to our API, not every app on your device.

Location and ISP: clues from IP databases

The country or region and ISP are based on IP geolocation data. They may identify the network operator or data center used by the connection, not the device's actual location. Database updates can take time. If the reported location differs from your selected route, that alone doesn't mean the connection has failed.

Proxy detection: an indicator, not a verdict

“Proxy detected” means the API classified the address as a proxy exit. “No proxy detected” only means it wasn't flagged; it doesn't prove that no proxy is in use. If the API returns no clear result, this page will show “Temporarily unavailable” rather than treating missing data as proof that no proxy is being used.

First check the results without a connection, then connect to your chosen route and run the lookup again. Consider the client's connection status, any change in public IP, and whether the destination site loads. If this site follows a direct-connection rule, the results may not change.

To review your client settings, read the Quick Start Guide. To compare available routes, see the Route List.

DNS Leak Check

DNS translates domain names into IP addresses. A changed public IP doesn't necessarily mean DNS queries are following the intended route. This page only calls the IP lookup API; it doesn't check DNS resolvers, so it can't automatically confirm or rule out a leak.

1. Confirm the intended route. Review your client's DNS settings and routing rules to see which domains should be resolved through the proxy and which should use your local network. Deliberately configured local DNS resolution isn't automatically a leak.
2. Check your browser's Secure DNS settings. A browser may use its own encrypted DNS settings, separate from your system or client configuration. Make sure they match your setup; there's no need to disable security features just to test.
3. Review actual DNS records. If your client provides connection or DNS diagnostic logs, check where a domain resolves after visiting it. If the logs aren't conclusive, leave the result as “uncertain.” The IP shown on this page can't provide that missing evidence.
4. Verify again after changing settings. Cached data may prevent new settings from appearing in the connection path right away. Follow your client's instructions to clear the cache or reconnect, then compare the logs and public IP. For help, describe the issue in a support ticket in the user portal.

A separate DNS test generates additional network requests. Before using one, review how it handles your data. This page won't automatically send requests to third-party testing services.

Lookup Privacy

We don't log lookups. Requests go only to our API. This page doesn't save results in your browser's local storage or fall back to a public third-party IP API. If our API is unavailable, we'll say so rather than generating substitute results.

The copy button writes your public IP to the clipboard only when clicked; it doesn't read clipboard contents. Before sharing a screenshot or submitting a support ticket, check for IP addresses and network details, and remove sensitive information such as account passwords and subscription links. See our Privacy Policy for details.