Connection Snapshot / NETWORK CHECK

Public IP and Network Check

See where requests from your browser are coming from. Run the check again after switching routes to see whether your public IP has changed.

Current Connection Snapshot

From Your Browser’s Perspective

Getting your current connection details…

Public IP address
Temporarily unavailable
Country / region
Temporarily unavailable
Internet service provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

What this information means

Connection details are useful for troubleshooting, but don’t prove how your entire device is connected.

Public IP and location

The public IP is the address our endpoint sees when it receives this request. It isn’t your device’s address on your local network. The location comes from an IP geolocation database and may differ from the route name due to address reassignments or outdated records. It can’t pinpoint your physical address.

ISP and proxy detection

An ISP usually refers to the network operator or hosting provider associated with an address, not necessarily your local broadband provider. Proxy detection is based on the endpoint’s assessment and may miss or misidentify a proxy. A negative result doesn’t mean your connection isn’t using a proxy or that your privacy protections are in effect.

Smart routing may send traffic to different websites through different routes. This page only reflects requests sent to our network-check endpoint; it can’t show the path used by other apps or websites.

To check a route, save your current public IP, connect to the route you want to test, then click “Check again.” If the IP hasn’t changed, check that your client is connected and that your routing rules aren’t sending requests to this site over your local network. You can also visit the Help Center.

Manual check · No DNS test performed on this page

Check for DNS leaks

A changed public IP doesn’t mean domain lookups are using the expected route.

DNS translates domain names into network addresses. If web traffic uses your selected route but DNS requests still go to an unexpected local resolver, further investigation may be needed. Our GeoIP endpoint doesn’t return DNS routing information, so this page won’t automatically report whether a DNS leak was detected.

  1. Check your client settings. Make sure the DNS options match your current connection mode. If you’re using per-app proxying, also check that your browser is covered by the proxy.
  2. Check your browser’s DNS settings. Review its Secure DNS settings. A custom browser resolver may differ from your client configuration, so check the documentation for the client you’re using.
  3. Compare resolvers before and after connecting. To investigate further, choose a DNS testing tool you trust and note the resolver names, associated networks, and locations before and after connecting. This page won’t send requests to such tools automatically.
  4. Consider the actual network path. A resolver’s location doesn’t have to match your public IP’s location. Public DNS services may route requests to a nearby location, so a difference in location alone doesn’t prove a leak. Check whether the resolver matches your expected configuration.

Reconnect after making changes, then test the website you want to use. See Guides for setup steps. Client downloads are available in the User Dashboard.

Lookup privacy

We don’t log lookups. Check requests are sent only to a same-origin endpoint on this site to return your current connection details; we don’t use third-party public APIs as a fallback. The copy button copies only the returned public IP and doesn’t access your clipboard contents.

If the endpoint is unavailable or a field is missing, that field will show “Temporarily unavailable”—never sample data. Before sharing a screenshot with support, consider masking any address details you don’t want to share. See our Privacy Policy for details on data handling.