See which network exit your browser is using for this request. Run a lookup before and after connecting to compare the IP address and location.
Results come from our lookup API and do not show your device’s local network address.
Start with the request’s public IP, then review its location details. No single result can tell you how every app is connected.
Websites usually see your public IP address, not your device’s address on a local network. Run another lookup after switching routes to see whether this request is using a different exit.
Split-tunneling rules may send traffic to different websites along different routes. These results can’t replace testing access to the site you want to use.
Location data comes from IP geolocation databases and may differ from your device’s location, route name, or the actual data center location. The ISP field may show a hosting provider or the organization the address is registered to.
Database updates can lag. IP geolocation isn’t precise location tracking and can’t tell you how fast a connection is.
We show a proxy detection result only when the API explicitly returns that field. If it’s missing, the page says “Temporarily unavailable” rather than assuming no proxy was detected.
“No proxy detected” doesn’t mean you aren’t using one. A detection result also doesn’t prove anonymity or measure your level of privacy protection.
A public IP lookup and a DNS test are different checks. This page doesn’t collect DNS resolver addresses, so it can’t tell you whether a leak is present or absent.
After connecting to your chosen route, review the client’s DNS, split-tunneling, and system-wide routing settings. Make sure the active configuration matches your expectations. If only browser traffic is routed through the client, other apps may use a different DNS path.
Look for “Secure DNS” or “Encrypted DNS” in your browser settings. Your browser may use a resolver that’s separate from the one configured on your system. Note the current setting before making changes, and follow your client’s guide to avoid changing several options at once and making the cause harder to find.
To check your DNS resolution path, use a reputable DNS test tool. Review the resolvers and organizations it reports, then compare them with your client settings. Resolvers may use distributed networks, so a different country alone doesn’t indicate a leak. A page loading successfully also doesn’t prove that DNS is following the expected path.
Follow your system or client’s instructions to clear the DNS cache, reconnect, and check your public IP and DNS results again. If they still don’t match your expectations, include your platform, client settings, and the circumstances in which the issue occurs when contacting support through the dashboard. Don’t include your password or full subscription link.
The copy button copies only your current public IP. Be mindful of who can see your IP address and network details if you share results in a support ticket, screenshot, or public discussion. If a lookup fails, we won’t show a sample address or switch to another lookup service.
This page reflects only requests your current browser sends to our API. Other apps, protocols, or IP address families may use different network exits.