Network Egress · Browser Check

IP Address Lookup

See where this browser request is coming from. Check before and after connecting for a clearer picture than the client’s connection icon alone.

Current request’s exit

Results come from our lookup service and may not reflect the network path used by every app.

IP address
Temporarily unavailable
Country / region
Temporarily unavailable
ISP / network provider
Temporarily unavailable
Proxy detected
Temporarily unavailable

Getting ready to check. If the lookup doesn’t start automatically, select “Check current exit.”

What these results mean

Exit IP and location

The exit IP is the address our lookup service sees for your request. It may differ after you connect to an international route. With split tunneling enabled, this site may still use your local network.

The country or region is based on IP registration data, not your device’s location. Updates to that data and ISP address assignments can affect the result, so it can’t pinpoint your location.

ISP and proxy detection

ISP usually refers to the provider or network organization associated with the exit IP—not necessarily the provider of your current internet connection. If the lookup service doesn’t return this field, you’ll see “Temporarily unavailable.”

Proxy detection is only a reference. “No proxy detected” doesn’t mean you aren’t using one, and it can’t tell you how well your privacy is protected or whether an app connected successfully.

How to check for DNS leaks

DNS translates domain names into network addresses. Routing web traffic through your chosen route doesn’t guarantee that DNS requests follow the same path. This page only checks your exit information; it does not run a DNS leak test and can’t report that your connection “passed.”

Cross-check settings and actual requests

  1. Check your client’s DNS and split-tunneling settings. Confirm that DNS requests follow your current connection mode. If you use custom rules, check whether DNS requests are routed separately.
  2. Check your system and browser DNS settings. Secure DNS in your browser, custom system DNS, and DNS handling by your client may all take effect independently. Review your current setup before making changes; changing just one setting isn’t enough to draw a conclusion.
  3. Check which resolver handles your DNS requests. For a direct test, use a dedicated tool that shows the source of DNS requests, and read its privacy policy first. This page won’t send requests to other testing services automatically.
  4. Interpret results in light of your connection mode. With split tunneling, local DNS resolution may be expected by your rules. With global routing, check that DNS requests follow the path specified by your configuration. Don’t rely on the resolver’s name alone to decide whether there’s a leak.

Need a step-by-step connection check? See the client setup guide or the beginner-to-advanced handbook. Change one setting at a time and keep your original configuration so you can compare and restore it.

Lookups and privacy

We don’t log lookups. This page retrieves information through our own service and doesn’t fall back to third-party public lookup services. If our service is unavailable, we’ll say so rather than guess.

The copy button writes your exit IP to the clipboard only when clicked. Before sharing a troubleshooting screenshot, consider obscuring your full IP address, account details, and subscription link. See the service’s Privacy Policy.

Start Free