Network Connection Check

IP Lookup and DNS Check

See the public IP address used by this browser request. Run another lookup after switching routes to check whether it has changed.

Current connection

Lookup results

Waiting for lookup

Enable JavaScript to run the lookup automatically, or use the button below to try again.

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

These results apply only to requests made to this page’s API. They don’t represent the connection used by every app on your device.

Understanding the results

Public IP and location

The public IP is the source address seen by this site’s API; it isn’t your device’s local network address. A change before and after connecting can indicate that your browser’s request is taking a different route. If the address hasn’t changed, check your client status and routing rules.

Country and region are based on IP geolocation data, which may be outdated or differ between providers. They don’t pinpoint your device or guarantee that an app will identify the same location.

ISP and proxy detection

The ISP field usually identifies the network provider or organization that holds the IP address, which may differ from the provider of your current connection. This field can also change when you switch routes.

Proxy detection is a classification returned by the API, not a check of your client’s connection status. “No proxy detected” doesn’t mean the request wasn’t routed through a proxy. If the API doesn’t return a detection field, this page shows “Temporarily unavailable” rather than treating unknown as no.

Public IP unchanged? Troubleshoot the issue →

DNS resolution path

Check for DNS leaks

DNS translates domain names into network addresses. A change in public IP doesn’t mean DNS queries are taking the same route. This page checks connection details only; it doesn’t test for DNS leaks or report a “pass.”

  1. Check your client’s DNS settings

    Open the client you’re using and review its DNS and routing settings. Check whether DNS interception is enabled as described in the client’s documentation. Don’t enter unfamiliar DNS addresses into your configuration. Keep a copy of your original settings so you can restore them if needed.

  2. Check your browser and system settings

    Secure DNS in your browser, manually configured system DNS, and other network tools can all affect the resolution path. Check that these settings match your client configuration. A DNS provider being located elsewhere doesn’t, by itself, prove a leak; assess the setup against your client’s actual configuration.

  3. Reconnect and test your usual apps

    Save your settings, reconnect, and clear the DNS cache as described in your client’s documentation. Then try a site you use regularly. If it still behaves unexpectedly, check routing rules, DNS resolution, and the public IP separately. Changing several settings at once can make the cause harder to identify.

If you need more help troubleshooting, submit a support ticket through the dashboard with details of the issue, your platform, client settings, and when it occurs. Before sharing screenshots, hide your subscription URL and account credentials.

Open a support ticket →
First Month Free