Network check · Browser egress

Current egress IP

See which network route this browser request uses. With split tunneling enabled, different apps can use different routes, so this page may not show the egress used by every app.

Results for this check

Lookup via our API

Waiting for lookup. Enable JavaScript to automatically check your current egress.

Egress IP
Temporarily unavailable
Country / region
Temporarily unavailable
Network provider / ISP
Temporarily unavailable
Proxy detected
Temporarily unavailable

Only information returned by the API is shown. If a field is missing, it stays marked “Temporarily unavailable”; we don’t infer results from other fields.

What this information means

Read the beginner’s guide →

Your egress IP isn’t your device’s local address

The egress IP is the public source address seen by the lookup API, not your device’s address on the local network. When connected to an international route, it may be the route’s exit IP. In rule-based mode, it may still be your local network’s public IP.

So seeing a local location on this page doesn’t, by itself, mean your client isn’t connected. First check whether this page’s request matched an international-route rule, then check the target app.

IP location is an estimate

Country, region, and ISP details come from the API’s IP address records. They aren’t device location data and don’t pinpoint a server’s physical location. Databases update at different times, so services may label the same address differently.

After choosing a route in a particular region, check that it works with the service you want to use. Location data alone doesn’t guarantee content access or account availability.

A proxy flag doesn’t confirm your connection status

“Proxy detected” means the API returned a proxy flag. “No proxy detected” only means the API didn’t flag this address; it doesn’t tell you whether your traffic is routed through a VPN.

If the API can’t make a clear determination, this page shows “Temporarily unavailable.” An IP lookup can’t verify encryption, logging policies, or how other apps are routed.

DNS leak check

This page doesn’t automatically test DNS

DNS translates domain names into network addresses. Routing web requests over an international route doesn’t necessarily mean DNS lookups take the same path. This page checks only egress information; it doesn’t query test domains, so it can’t confirm that you’ve passed a DNS leak test.

  1. First decide which requests should use an international route

    Check the client’s routing mode, target app, and DNS settings. Split tunneling can keep commonly used local websites on your local network. To assess whether local DNS resolution is expected, check the matching domain rule; the resolver’s location alone isn’t enough to draw a conclusion.

  2. Compare browser and system DNS settings

    Check whether the browser uses its own Secure DNS, then review the system DNS settings and whether the client handles DNS resolution. Different DNS entry points can produce different results. Note the current settings before making changes, and change one thing at a time to identify what caused any difference.

  3. Check the target domain against DNS records

    If your client provides local diagnostics, check the target domain’s resolution path and matched rules. Before using a dedicated test tool, find out which domains it queries and how it collects DNS records. Don’t treat a single test as a long-term result for every app.

  4. Recheck access after making changes

    After changing your settings, reconnect to the route and reopen the target app. Clear the DNS cache if needed. Check the egress IP, DNS path, and access to the target service separately. A webpage loading successfully only confirms that one request worked; it doesn’t replace a DNS path check.

Lookup privacy and troubleshooting

We don’t log queries. Requests use our GeoIP API; this page doesn’t send lookups to third-party public APIs. Copying writes only the current egress IP to your clipboard, not any other lookup details.

If the API is unavailable, a request times out, or the response is incomplete, the page will say so. Check your connection and try again. A failed lookup doesn’t necessarily mean your route is down, and we won’t fall back to another public lookup service.

To troubleshoot a connection issue, submit a description through the user dashboard. Before sharing a screenshot, consider hiding your egress IP and account details.

Privacy Policy → Open a support ticket →
First Month Free