Browser IP · Network checks

Check your current public IP

See the public IP address used by your current connection. After connecting or switching routes, run the lookup again to compare the IP and its location.

Connection details

Checked via our API
IP address
Temporarily unavailable
Country / Region
Temporarily unavailable
Internet service provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

Getting your current connection details…

These results show only the connection your browser used to reach our API. They don’t represent every app’s connection and aren’t a DNS leak test report.

What this information means

Your public IP can help confirm your connection route. Interpret its location and proxy status in context.

IP address and location

The IP is the public source address seen by our API. It may belong to a home network, a shared ISP connection, or the international route you’re using. The location comes from an IP database, not your device’s precise location. Database updates can lag, so the listed location may differ from the route’s label.

After switching routes, wait for the connection to establish, then select “Check again.” If the IP hasn’t changed, check whether your browser is using proxy rules and whether this site is set to connect directly.

ISP and proxy detection

An ISP usually refers to the provider or network organization associated with the public IP; it may not be your local broadband provider. Proxy detection depends on the API’s data sources and classification rules, so results may miss or misidentify proxies.

“No proxy detected” doesn’t mean all traffic is connecting directly. “Proxy detected” doesn’t indicate connection quality. This label can’t replace checking your client’s status or assessing your privacy.

DNS leak check

IP lookups and DNS checks cover different parts of a connection. This page doesn’t run a dedicated DNS test, so it won’t automatically report a pass or a leak.

DNS translates website domain names into IP addresses. Routing a browser’s web traffic through a proxy doesn’t mean its DNS queries follow the same route. If DNS requests still use an unexpected local network, check the DNS settings in your client, operating system, and browser.

  1. Confirm your public IP first. Connect to your chosen route and look up your IP on this page. Once it matches your expectations, check DNS resolution. This helps avoid mistaking an inactive route for a DNS issue.
  2. Check your client settings. Review DNS interception, remote resolution, and routing mode against your client’s documentation. Split tunneling may send some domains to local DNS, so check the rules rather than relying only on whether a toggle is on.
  3. Check your browser and system. Secure DNS, custom DNS settings, and other network tools on your device can all affect how DNS requests are routed. Note your original settings before making changes, change one thing at a time, and test again.
  4. Verify with a dedicated test. To identify the resolvers actually in use, choose a trusted, dedicated DNS test tool and compare the resolver details before and after connecting. This page won’t contact external test sites automatically. A resolver’s location alone isn’t enough to conclude that a leak has occurred.

If only one app is affected, first check whether it supports proxies and review its routing rules. If settings across multiple tools are interacting, restore a clear, repeatable configuration and troubleshoot one step at a time. For more help, see our Guides or describe the issue in a support ticket in your account.