NETWORK / REQUEST EXIT

Public IP and location

First, check where this request is coming from, then confirm whether your apps are using the expected route.

These results apply only to the request your browser makes to this site’s lookup endpoint. They don’t show the connection routes used by every app on your device.

OBSERVATION / CURRENT REQUEST

Current connection details

Checked via our endpoint

Not checked yet. Enable JavaScript to retrieve results automatically.

IP / Public address
Temporarily unavailable
REGION / Location
Temporarily unavailable
ISP / Internet provider
Temporarily unavailable
PROXY / Proxy detected
Temporarily unavailable

Location and proxy status may be delayed or inaccurate. Don’t rely on them alone to assess connection security or whether a platform will work.

What these results mean

Your public IP isn’t your device’s address

Your public IP is the address this lookup request presents to the internet. It may come from your local network or a proxy route. With split tunneling enabled, this site’s request and international apps may follow different rules. A local IP here doesn’t mean an international app isn’t using a proxy.

The location and ISP describe the network associated with the public IP, based on an IP address database. They don’t pinpoint your device. A route’s name, an IP address’s registered location, and the region an app detects may differ.

Proxy detection doesn’t confirm your connection route

“Proxy detected” means the endpoint identified the public IP as proxy-related. “No proxy detected” only means it wasn’t identified this time. If the proxy status is missing, this page shows “Temporarily unavailable” rather than treating the missing value as proof that no proxy is in use.

To verify an app’s route, check the client’s matching rules and connection logs, then confirm the region or session details reported by the app itself. To change the route, see the Guides and route types guide.

DNS leak check

  1. Start by defining the expected route

    Check your client’s routing mode and DNS settings. Confirm which domains should use local DNS and which should be resolved through the proxy. Local DNS for local websites may be expected behavior under your rules; it doesn’t automatically indicate a leak.

  2. Check your browser and system settings

    Check whether your browser has Secure DNS enabled separately and whether your system uses a custom resolver. The browser, system, and client may handle DNS requests independently, so changing one setting may not affect every app.

  3. Verify against connection logs

    Open your client’s connection or DNS logs, then visit the domain you want to check. Compare the matched rule, resolver, and actual route with what you expect. If needed, clear the DNS cache and reopen the app. Investigate further only if DNS requests take an unexpected route.

  4. Check each app separately

    Different apps may use different DNS resolution methods. Checking your browser doesn’t verify other apps. If you still have questions, see the Help Center for connection guidance, or use the support portal to describe your operating system, client mode, and the issue you’re seeing.

Lookup privacy

We don’t log lookups. To retrieve results, your current request is processed by our GeoIP endpoint. If the lookup fails, this page won’t fall back to a third-party public API. The copy action copies only your public IP; it doesn’t submit your results elsewhere.

Before sharing a screenshot or submitting a support ticket, hide any network addresses, account details, or subscription credentials that aren’t needed. See our Privacy Policy for details about service scope and privacy.