Network Connection Check

Public IP and Location

See the network route used by your browser to access this site. Check again after connecting to compare your public IP.

Current Results

Waiting for lookup
Public IP
Temporarily unavailable
Country or Region
Temporarily unavailable
ISP / Network Provider
Temporarily unavailable
Proxy detected
Temporarily unavailable

Enable JavaScript to look up your IP through this site’s API.

Results apply only to this browser request; other apps may use a different route. This page does not test for DNS leaks.

What These Results Mean

A changed IP is a starting point for troubleshooting, not the whole story. Location and proxy status are identified by the API and may be unavailable or out of date.

Public IP: Where Your Request Comes From

This is the source address seen by this site’s API, not your device’s address on your local network. Copy and save it before and after connecting to compare.

If the address hasn’t changed, first check your client’s connection status and whether your browser is covered by the active routing rules. An unchanged IP alone doesn’t prove the entire route is broken.

Location and ISP: Network Registration Details

Country or region is usually determined from an IP address database. The ISP is the network provider associated with the address; it may also show a data center or network services company.

This information does not reveal your device’s precise location. Databases and websites may use different methods, so these results can’t guarantee how a particular platform will identify your region.

Proxy Status: One Signal to Consider

“Proxy detected” means the API identified this connection’s public IP as proxy-related. “No proxy detected” means only that no such status was returned; it doesn’t prove the connection isn’t using a proxy.

If a field is unavailable, it will show “Temporarily unavailable” rather than treating an unknown result as “not detected.” This status also can’t prove anonymity or the effectiveness of privacy protections.

DNS Leak Self-Check

DNS translates domain names into network addresses. A changed browser IP doesn’t mean DNS requests follow the same route. This page only checks requests to this site’s API; it can’t read all DNS traffic from your device or automatically confirm that there are no leaks.

  1. Check your public IP first. Connect your client, then check this page again and note the IP and location. If you use split tunneling, make sure your browser is using the intended rule when accessing this site.
  2. Review your DNS settings. Check your client’s DNS and routing settings, then review your system DNS and browser Secure DNS settings. A browser using its own resolver may follow a different route from the system. Don’t draw conclusions based only on whether a setting is enabled.
  3. Test DNS separately. Use a DNS testing tool you trust before and after connecting, then compare the resolver information. Read the tool’s privacy policy before using it. This page does not automatically send requests to external testing services.
  4. Compare the results with your expectations. If you still see a resolver associated with your local ISP after connecting, but expect DNS to use your selected route, check your DNS routing and rules. A resolver in another region isn’t necessarily a leak; it may be part of a Secure DNS service or its network infrastructure.

For import and connection steps, read our Guides. For routing rules and routine maintenance, see our Complete Guide.

Lookups and Privacy

We don’t log lookups. This page retrieves results from an API on the same domain and does not fall back to a third-party public API. The copy button writes your public IP to the clipboard only when clicked.

Your public IP is network information, so consider masking it before sharing screenshots. If a lookup fails, the page clears old results and explains the issue instead of showing sample data. See our Privacy Policy for details.