Exit Information / Connection Check

My IP

View your browser’s current exit details and compare them before and after connecting.

Current Exit Information

Checked via our API

Waiting for a query. Enable JavaScript to check your current exit details.

Public IP
Temporarily unavailable
Country or Region
Temporarily unavailable
ISP / Network Provider
Temporarily unavailable
Proxy Detected
Temporarily unavailable

Results apply only to the connection used to reach our API for this request. Other apps may use different routes.

Understanding the Results

What These Details Mean

A change in your exit IP can help indicate whether your connection is active, but it doesn’t by itself confirm privacy protection or access to a particular site.

IP and Country or Region

The exit IP is the network address seen by our API. Note the result before connecting, then check again to see whether it changed. Location data comes from IP databases and may be out of date; it is not your device’s precise location and should not be used to locate you.

ISP and Proxy Detection

The ISP is the network provider associated with the exit address, which may differ from your local internet provider. Proxy detection depends on the classifications supplied by the API and may be inaccurate or unavailable. “Not detected” doesn’t mean no proxy is in use, and “detected” doesn’t by itself mean your connection is at risk.

If your exit IP hasn’t changed, first check your client’s connection status and whether a routing rule sends this site directly. Different apps may use different routes. Review your settings, then check again. For setup steps, see the beginner’s guide.

DNS Checks

How to Check for DNS Leaks

This page’s exit check does not test for DNS leaks. A changed exit IP doesn’t prove that DNS requests follow the same route.

First, Distinguish Exit IPs from DNS Lookups

Before a browser visits a site, it usually looks up the domain name to find its network address. Website traffic may go through a proxy while DNS lookups are still handled by your local network. What to expect depends on your client’s DNS mode, routing rules, and the browser’s own Secure DNS settings.

  1. Before connecting, note the DNS settings used by your system, browser, and client. Don’t rely only on the resolver’s name or location to decide whether a leak is occurring.
  2. After connecting, check your client’s DNS interception settings and lookup route. If your client provides diagnostic logs, check which resolver handled the domain lookups and whether they followed the expected route through the proxy.
  3. Check whether your browser’s Secure DNS settings override the system configuration. Coordinate these settings using your client’s instructions. Avoid changing several settings at once, so you can identify what caused any difference.
  4. For further verification, use a DNS testing tool that clearly identifies its resolvers and testing method. Compare results before and after connecting, and consider your routing rules. This page does not automatically send requests to third-party testing services.

A local network resolver appearing in the results is a clue to investigate, not a definitive conclusion. Organization networks, independent browser lookups, and intentional direct-routing rules can all affect the results. If you’re unsure, use the support ticket portal to share your operating system, connection method, and the issue you’re seeing. Don’t include passwords or full subscription links.

Privacy Notice

Queries and Data Handling

We don’t log queries. Checks use an API on our own domain. If it’s unavailable, we’ll let you know rather than fall back to a public third-party API. This page doesn’t store query results in your browser; copying happens only when you click the button.

Your exit IP can still identify your network. When sharing screenshots or reporting an issue, include only what’s needed to troubleshoot and conceal account credentials. See our Privacy Policy for details.