My IP and Location

Understanding the results

Public IP: where your request comes from

Websites typically see the public IP address of your network connection, not your device’s local network address. After you connect to an international route, requests from your browser will usually show that route’s exit IP. With split tunneling, this page may still use your local connection, so an unchanged result alone doesn’t mean the client failed to connect.

Location and ISP: IP registration details

Location is based on IP registration data, not your device’s precise location. The ISP is the network provider identified by the API; a route’s exit IP may show the name of a data center or upstream network. Registration data can vary or be out of date, so it can’t confirm whether a particular streaming service or AI tool will work. Check by accessing the service itself.

Proxy detection: an indicator, not a privacy verdict

“Proxy detected” means the API returned a corresponding indicator. “No proxy detected” means only that the check didn’t return that indicator. If the API doesn’t provide a valid field, the result is shown as “Temporarily unavailable.” This result can’t confirm whether your connection is encrypted or whether all traffic uses the selected route.

Note your public IP before connecting, then select “Check again” and visit the service you want to use. If the result isn’t what you expected, check the client’s connection status, selected route, and split-tunneling rules.

DNS leak check

DNS translates website domain names into network addresses. A changed public IP doesn’t mean DNS requests use the same route. This page’s lookup API doesn’t test for DNS leaks, so the IP result above can’t tell you whether DNS is protected or leaking.

1. Check your client’s DNS settings. See whether your client offers DNS configuration and review its documentation to understand how DNS requests are handled. Don’t assume DNS follows the intended route just because the client says it’s connected.
2. Check your browser settings. The browser’s Secure DNS settings may differ from your system or client configuration. Check which DNS resolution method is in use and whether it matches your connection mode.
3. Check the actual DNS results. To verify, choose a DNS test tool that clearly explains its privacy policy and shows the DNS servers it detects. Test before and after connecting, then compare the DNS provider with your expected configuration. The test sends requests to its provider, so review how it handles data before using it.
4. Consider your network setup. A DNS provider in a different region from your exit IP doesn’t necessarily indicate a leak. Check your client’s DNS settings, browser resolution method, and the test tool’s documentation together. If you can’t explain the results, contact support.

When reporting an issue, include your operating system, client connection mode, and whether Secure DNS is enabled in your browser. Hide subscription links, account credentials, and other sensitive information before sharing screenshots.

Lookup & privacy

We don’t log queries. Lookups use our API and don’t fall back to a public third-party API. The copy button copies only the retrieved public IP, not account or subscription details.

If the API is unavailable or doesn’t return a valid public IP, this page clears the results and displays “Temporarily unavailable.” This means the lookup didn’t complete; it doesn’t mean your internet connection is down. Try again later or check your client’s connection status.