Network egress · Lookup via our API

Public IP and location

See where this browser request enters the network. After switching routes, run the lookup again to check whether your public IP has changed.

Current lookup results

Egress details

Waiting for lookup. Enable JavaScript to retrieve your current network details.

Public IP
Temporarily unavailable
Country / Region
Temporarily unavailable
Internet service provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

This reflects the egress used by this browser request only, not the connection path of every app on your device.

What this information means

Public IP: the network address seen when a request reaches our site

Your public IP may belong to your current internet provider or to the egress of your selected route. Check it on your original connection, then switch routes and check again to see whether your browser is using a different egress. Split-tunneling rules may send traffic to our site directly. If your IP hasn't changed, check which rule applies to our site before assuming the client connection has failed.

Location and ISP: useful for cross-checking, not your actual location

Country and region come from an IP database and may be out of date. The ISP is the network affiliation identified by the database, which may show a carrier, data center, or network organization. Neither provides your device's precise location, nor can either alone determine how a streaming or AI service will classify your account's region. Fields unavailable from the API will show “Temporarily unavailable.”

Proxy detection: an indicator, not a privacy verdict

This page displays a proxy status only when the API explicitly returns one. “No proxy detected” doesn't mean you're not using a proxy, and “Proxy detected” doesn't mean your connection is faulty. Database classifications, route egress, and each website's own detection methods can all affect the result. It can't tell you how anonymous you are.

DNS leak check

DNS translates domain names into network addresses. Routing web requests through your selected route doesn't guarantee that DNS queries use the same path. This page checks the egress of HTTP requests; it does not run a separate DNS leak test, so a successful IP lookup is not proof that your DNS is secure.

  1. Check your client's DNS settings. See whether DNS interception or remote resolution provided by the client is enabled, and configure it according to the client's instructions. If you connect to a route without handling DNS, queries may still use your local network's resolver.
  2. Check whether your browser or system uses a different DNS method. Secure DNS in your browser, custom system DNS settings, and other networking tools may each take effect independently. Note your current settings, then check them one at a time so you can identify the cause.
  3. Test in the split-tunneling mode you actually use. For a dedicated test, use a DNS testing tool that displays resolver information and compare it with the resolution path configured in your client. A resolver in a different region doesn't necessarily indicate a leak; consider how the DNS service is deployed as well.
  4. Keep a record of the configuration when the issue occurs. Note your operating system, client, connection mode, and symptoms. Redact subscription credentials before submitting a support ticket. Don't judge whether your DNS is configured correctly based only on the country or region shown on this page.

If your browser's egress differs from what you expected, start with connection troubleshooting. To check how to import a subscription and connect, see the subscription guide.

Start Free