exit / network

Current public IP

See the public IP address your browser uses to access this site. After switching routes, run the lookup again to check whether the exit location matches your expectations.

network / exit check

Lookup results

Our API
Public IP
Temporarily unavailable
Country / region
Temporarily unavailable
ISP / network provider
Temporarily unavailable
Proxy detected
Temporarily unavailable

No lookup results yet. JavaScript must be enabled for automatic lookup.

This reflects only the public IP used for this browser request. It does not represent traffic from other apps or guarantee that a particular service will be available or your account will be secure.

read / the result

What this information means

IP address, geolocation and proxy detection describe different things. Consider them in light of your actual connection.

Public IP and location

The public IP is the address observed by our API, not your device’s local network address. The country or region comes from an IP database and may reflect an ISP’s registered location or an exit server’s data center—not your device’s actual location.

ISP and network ownership

The ISP field usually identifies the organization associated with the IP address. When connected through an international route, it may show a data center or network provider rather than your local broadband provider.

Limits of proxy detection

The proxy indicator reflects the API’s detection result. A detected proxy doesn’t mean the connection is faulty, and no proxy detected doesn’t prove that all traffic is routed as expected. If the API doesn’t return this field, this page won’t infer a result.

To check a route, note your current public IP, switch routes in your client, then run the lookup again. If the address hasn’t changed, check whether the browser is covered by the client’s proxy rules, whether the client is connected, and whether other proxy settings are active. A changed IP alone doesn’t confirm that DNS switched too.

dns / self-check

DNS Leak Check

This page looks up your public IP; it does not test for DNS leaks. The steps below are a guide, not an automated test result.

Check the DNS resolution path, not just your public IP

DNS translates domain names into IP addresses. Routing web requests through the expected exit doesn’t mean DNS queries follow the same path. Browser secure DNS, system resolver settings and client routing rules can each affect where queries go.

  1. Note your settings before connecting. Check the DNS source in your system network settings, and see whether secure DNS is enabled separately in your browser. Understand your configuration first so you can identify the cause if something changes.
  2. Check your client’s DNS and routing mode. After connecting to a route, confirm how the client handles DNS queries. In rule-based mode, some domains may use local DNS resolution; make sure this matches your intended setup.
  3. Check the resolver actually in use. To run a test, use a DNS testing tool you trust or check your device’s DNS logs. These tests typically send requests to dedicated test domains; this page’s public IP lookup is not a substitute.
  4. Compare and test again. Compare the resolver’s network ownership before and after connecting, taking your client settings into account. After changing settings, reconnect, clear the DNS cache using your system’s usual method, then test again to confirm the results match your rules.

Lookup privacy

We don’t log lookup requests. Requests are sent only to an API on this site’s domain; no third-party public API is used as a fallback. If the API is unavailable, this page shows “Temporarily unavailable” rather than estimated data.

Copying writes only your public IP to the clipboard. Before sharing a troubleshooting screenshot, hide any addresses and account details you don’t want to disclose. Don’t include subscription links or login credentials.

Read the Privacy Policy →