Network Exit Check

Current Public IP
and Location

See the network exit used when your browser accesses this site. After connecting or switching routes, run another check to see whether the exit matches your expectations.

Network Exit Results

Our API

Waiting for a check. If it doesn't start automatically, select Check Again.

Current Public IP
Temporarily unavailable
Country / Region
Temporarily unavailable
ISP / Network Provider
Temporarily unavailable
Proxy detected?
Temporarily unavailable

Shows the exit for this request only. It doesn't check connections from every app on your device or detect DNS leaks.

What These Results Mean

First check whether the exit changed, then verify the route. No single field can confirm the network status of your entire device.

Public IP and Location

The IP is the address used for this request. Its location comes from an IP database and may differ from the data center's actual location or the region assigned by a service. It can't be used to locate someone's home address.

If the address hasn't changed after switching routes, this site's requests may still be using the original route. Check that the client is connected and that its routing rules include this site, then run another check.

ISP and Network Route

The ISP field usually identifies the network provider or organization associated with the address, not necessarily your local broadband provider. When using an international route, seeing the provider name for the exit network is expected.

This page doesn't measure latency, bandwidth, or reliability. Even after confirming the exit, verify the connection in the app you actually use.

Limits of Proxy Detection

The proxy status is based on detection data returned by the API. A proxy detected result doesn't mean the connection is having problems; no proxy detected doesn't guarantee that the request didn't pass through a proxy.

If the API provides no clear status, this page shows “Temporarily unavailable” rather than guessing based on the IP or provider name. This status also says nothing about whether AI or streaming platforms are accessible.

DNS Leak Self-Check

DNS translates domain names into network addresses. A web request using your selected route doesn't mean DNS lookups use the same path. This tool checks only your network exit; it doesn't probe DNS resolvers, so it can't determine whether DNS is leaking.

  1. Check your client's DNS settings. See whether DNS interception or remote resolution is enabled, and confirm in the client documentation that these settings apply to your current connection mode. Don't use configuration from an unverified source.
  2. Review your system and browser settings. Secure DNS in your browser, system DNS settings, and other network software may handle domain requests separately. Make sure they align with your client configuration; a web exit check alone can't confirm the DNS route.
  3. Verify routing rules in each app. Browsers, command-line tools, and developer tools may use different proxy settings. Check your client's connection logs and DNS diagnostics to confirm how the target domain is resolved and routed. Remove credentials and subscription details before sharing logs.
  4. Keep your environment details if something doesn't match. Note the platform, connection mode, relevant settings, and error message, then request help through a support ticket in the dashboard. Don't post screenshots containing your full network details publicly.

View the connection guide · Visit the help center · Open a dashboard support ticket

Try It Free