Browser IP Lookup

IP Address and Location

See the public IP used for this lookup. After switching routes, check again and compare the result with the location selected in your client. This reflects only the path taken by your browser’s request.

Current connection details

Waiting for lookup
Public IP
Temporarily unavailable
Country / Region
Temporarily unavailable
ISP / Network provider
Temporarily unavailable
Proxy detected
Temporarily unavailable

Preparing lookup.

Proxy detection and location are based on information returned by the interface. They do not confirm that a connection is secure and cannot replace a DNS check.

What this information means

Public IP: the address websites see

Your public IP is the address used when this request reaches the lookup interface. It is not your device’s local network address. When a proxy is enabled, only requests that actually pass through it use its exit address. Split-tunneling rules, browser settings, and client mode can all affect the result.

Country, region, and ISP: database classifications

The reported location is a database estimate for the IP address, not your device’s precise location. The ISP field usually identifies the network provider or hosting network associated with the address, which may differ from the broadband brand you use day to day. Databases update at different times, so if the reported region and route name do not match, check your client status and actual access.

Proxy detection: a reference label, not proof of privacy

“Proxy detected” means the interface marked the current exit address as a proxy. “No proxy detected” only means the interface did not identify one; it does not prove that your connection is not using a proxy. If the interface provides no clear status, this page shows “Temporarily unavailable” rather than guessing.

Check for DNS leaks

DNS translates domain names into network addresses. A change in your public IP does not mean DNS requests are taking the same route. This page checks only your public IP; it does not collect DNS resolver addresses, so it cannot automatically report that there are “no DNS leaks.”

  1. Check your client’s DNS settings.

    Check whether DNS interception or proxy-based DNS resolution is enabled, and confirm in your client’s documentation which modes support it. With only the system proxy enabled, some apps may still use the system’s DNS settings.

  2. Check your browser and system DNS paths.

    Secure DNS in your browser, encrypted DNS in your system, and your client’s DNS settings may all be active at once. Check where each DNS request is sent. A single enabled setting does not mean every request is being handled by it.

  3. Review DNS records alongside your setup.

    If your client provides local diagnostic logs, check whether the expected component handled DNS requests when you accessed the target website. A difference between the resolver’s location and your exit location is not, by itself, evidence of a leak. Check whether requests left the expected proxy route.

  4. Note what happens, then change settings one at a time.

    Note the affected app, connection mode, and relevant settings, then repeat the same steps after each change. If you need help, describe the issue in a support ticket in the user panel. Do not share your password or full subscription link.

Privacy and lookup limits

We do not log lookups. Checks are sent only to a same-origin interface on this site. This page does not save results to local storage or fall back to a third-party public lookup service. The copy button copies only your public IP, and the action takes place in your browser.

If the lookup interface is unavailable, the page will say so and show “Temporarily unavailable.” This does not mean your proxy is malfunctioning. Try again later, or check your network and client connection. For details, see our Privacy Policy and Help Center.