Public IP and Network Check

What these results mean

Public IP: the address seen by our interface

Your public IP is the address shown when this request reaches our lookup interface. It isn’t your device’s local network address. After connecting to a route, check again and compare the results. If the address hasn’t changed, make sure your client is connected and your browser is using the selected route to access this site.

Split tunneling may route this site differently from other websites. Browser extensions and in-app proxy settings can also change a request’s egress. So, seeing your local IP here doesn’t prove that other apps aren’t using a route; seeing the selected region doesn’t prove that all traffic uses the same egress.

Location and ISP: reference data from IP databases

The country or region comes from IP geolocation data and doesn’t indicate your device’s actual location. IP allocations, network operations, and database updates can differ. ISP usually refers to the network provider or organization associated with an address. With a data center egress, the displayed name may differ from your subscription provider’s brand.

Proxy detection: not a connection test

Proxy details appear only when the interface explicitly returns a detection result. “Not detected” doesn’t confirm that no proxy is in use, and “Detected” doesn’t mean the connection is faulty. If the interface doesn’t provide this field, this page shows “Temporarily unavailable” rather than inferring a result from your IP or location.

To verify your connection, check your client status, split-tunneling rules, and access to the destination site. For setup help, see the Quick Start Guide or FAQ.

How to check for DNS leaks

DNS translates domain names into network addresses. An IP lookup checks where web requests exit; it can’t tell you whether DNS queries follow the route you expect. This page doesn’t run a DNS leak test and won’t mark a successful IP lookup as a passed DNS check.

1. Check your client’s DNS settings. Confirm the active mode and how DNS requests are handled under your client’s configuration. Don’t rely on the DNS address shown by your operating system alone to determine who ultimately handles queries.
2. Check your browser’s Secure DNS settings. Your browser may choose its own encrypted DNS service, using a different resolution path from your system or client. Make sure the settings match your expectations, then reload the destination page.
3. Compare resolvers with your expected settings. If you use a separate DNS test tool, read its privacy policy first, then review the detected resolver providers. A difference between the resolver’s location and your egress region doesn’t automatically mean there’s a leak; distributed public DNS infrastructure can affect what you see.
4. Troubleshoot based on how you use your network. If DNS requests aren’t taking the expected path, check split-tunneling rules, system network settings, and whether other network tools are active. Change one setting at a time and compare results so you can tell what made a difference.

To learn more about how split tunneling, protocols, and routes work together, read Routes and Protocols. This page doesn’t send requests to third-party DNS testing services.