Public IP Check.

IP address: where this request exits

This is the source address seen by this site’s lookup service, not your device’s address on the local network. Save the result before connecting to a route, then connect and check again to see whether your browser’s public IP changed. An unchanged address doesn’t necessarily mean the connection failed: your browser’s request to this site may be routed directly.

Location and ISP: information from IP databases

The reported location comes from an IP address database; it isn’t your device’s precise location, and different databases may label it differently. The ISP field may show a network operator, hosting provider, or exit network, so it can’t confirm which network your device is actually connected to. If a field is missing, this page shows “Temporarily unavailable” rather than inferring a value from other fields.

Proxy detection: based only on the service’s response

Proxy status depends on the service’s data sources and detection criteria. “No proxy detected” doesn’t mean you aren’t using a proxy, and “Proxy detected” says nothing about connection quality or the level of privacy protection. If the service doesn’t return a clear status, this page won’t treat an unknown result as a negative one.

First, find out which service resolves your domains

DNS translates domain names into IP addresses. Even when browser requests go through a selected route, domain lookups may still be handled by your operating system, your browser’s Secure DNS setting, or your client. A changed public IP doesn’t prove DNS queries took the same route.

1. Open your client’s settings and review DNS, routing, and connection mode. Note your current settings before making changes so you can restore them if needed.
2. Check whether Secure DNS is enabled separately in your browser and whether a DNS resolver is configured manually on your system. Consult your client’s documentation to understand which settings take priority.
3. For a direct check, use a dedicated test tool that lists DNS resolvers. Compare results from before and after connecting, and read the tool’s privacy policy first. This page won’t send requests to such tools automatically.
4. If the resolvers don’t match what you expect, first check whether that’s due to your routing rules. Then review your browser settings, system cache, and client DNS configuration. A difference between the resolver’s location and your public IP’s location isn’t, by itself, evidence of a leak.

How to troubleshoot a website that won’t load

If your client says it’s connected but domain names aren’t resolving properly, check your device’s date and time, system proxy, and DNS settings, then try another route. Don’t start troubleshooting by enabling multiple network tools at once; their routing rules may conflict. For a more detailed troubleshooting process, see the Troubleshooting Guide. If this is your first connection, start with the Quick Start Guide.