Connection Check / Network Test

Exit IP and
Network Test

See which exit your browser is using to reach this site. Run a check before and after connecting to a route to see whether your browser’s access path has changed.

Current Exit Details

Waiting for lookup

Preparing your lookup. Results reflect only the exit used by this browser to access this site.

Exit IP
Temporarily unavailable
Country / Region
Temporarily unavailable
Network Provider / ISP
Temporarily unavailable
Proxy Detected
Temporarily unavailable

Proxy status and location are based on data returned by the endpoint. They don’t verify route connectivity or provide a complete assessment of privacy and security.

Understanding the Results

What This Information Tells You

A change in your exit is one clue when checking a connection. Consider it alongside your client rules, target app, and actual access results.

Exit IP and Location

The exit IP is the network address identified when this site receives a request from your browser. It isn’t your device’s local network address. The location comes from an IP address database; it doesn’t indicate your device’s actual location and may differ from how other sites determine your region.

Record the result before connecting to a route, then connect to the route you want and run the check again. If the address hasn’t changed, check whether this site is set to bypass the proxy, whether your browser uses a separate proxy, and whether the client is actually handling browser traffic.

ISP and Proxy Detection

The ISP field typically identifies the organization associated with the exit IP. It may show an internet provider, data center, or cloud network rather than your local broadband provider. If the field is blank, the endpoint didn’t provide that information; this alone doesn’t indicate a connection issue.

Proxy detection relies on databases and detection rules. “Not detected” doesn’t mean no proxy is in use, and “detected” doesn’t by itself indicate an account risk. Each platform makes its own assessment.

Check for DNS Leaks

Check Your DNS Route After Your Exit Changes

DNS resolves domain names to network addresses. A changed exit IP doesn’t mean DNS requests are using the same route. This page’s GeoIP lookup does not test DNS and cannot confirm that there are no leaks.

  1. Check Your Client’s DNS Settings

    Check whether your current settings route DNS through the client, and whether split-tunneling rules keep local DNS resolution for domains set to connect directly. Don’t rely only on the DNS address shown by your system to determine whether there’s a leak: the client may intercept or rewrite requests when they’re sent.

  2. Check Browser and System Settings

    Your browser’s Secure DNS, your system’s encrypted DNS, and an app’s own DNS resolution can differ from the client settings. When troubleshooting, note these options and check that they match the expected route. After making changes, reconnect to avoid stale connections and cached results affecting your assessment.

  3. Check DNS Records

    If your client provides local DNS or connection logs, visit the target domain and check which resolver and outbound rule were used. Advanced users can inspect local network requests for unexpected direct DNS lookups. A resolver’s region or organization alone isn’t enough to prove a leak.

  4. Test Access in Each App

    Check your browser and the apps you actually use separately. If a website works, that doesn’t mean your command line, IDE, or other apps use the same settings. For help, describe your operating system, client status, and the error through a support ticket in the dashboard. Hide subscription URLs and account credentials before submitting.