Connection Check / Public IP Details
Public IP and location
First see where your browser is connecting from, then check your DNS route. Run another check after connecting to compare your public IP.
Current public IP
Checking…- IP address
- Temporarily unavailable
- Country / region
- Temporarily unavailable
- Internet service provider / ISP
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
Getting the check ready. If it doesn’t start automatically, select “Check again.”
What these results mean
Public IP: the address your request comes from
This result shows the public IP used by your browser to reach our checking API. It is not your device’s address on a local network. After connecting to a VPN, make sure the client is enabled, then select “Check again.” With split tunneling, this site may still use your local network. If your IP hasn’t changed, check your routing rules before assuming the connection isn’t working.
Location and ISP: network details, not your personal location
Country, region, and ISP information comes from IP databases. These databases may be out of date, or may associate an address with the registered location of the network operator. Location is not precise, and the ISP name may differ from the name of your home broadband provider. These results can’t predict how a particular website will determine your location.
Proxy detection: an indicator, not a verdict
“Proxy detected” means the API flagged this public IP as a proxy. “No proxy detected” only means the API didn’t identify proxy characteristics; it doesn’t mean your client isn’t running. If the API can’t determine a result, this page shows “Temporarily unavailable” rather than treating missing data as a negative result. Whether other apps use the same public IP also depends on their proxy and routing settings.
DNS leak check
An IP lookup and a DNS leak test are different things. This page checks your public IP only; it doesn’t run a DNS leak test or determine from your IP alone whether DNS requests follow the route you expect.
- Check your client’s DNS mode. Open the client’s network settings and check whether it handles DNS, then review your current routing rules. A “connected” status alone doesn’t mean all domain lookups are using the new route.
- Review your browser and system settings. Secure DNS in your browser, custom DNS on your system, and other network tools may use different resolution paths. Note your current settings before making changes, so you can identify the cause without changing several things at once.
- Check which resolvers are being used. If you use a dedicated DNS testing tool, compare its resolver results before and after connecting, and check how the tool handles your data. A resolver’s name or location may differ from your public IP because of how public DNS is deployed. A location difference alone doesn’t prove there’s a leak.
- Check the setup you actually use. If a service still reports that your location doesn’t match, review its routing rules, your browser cache, and your account region. Use your client’s diagnostics to investigate, and share only information relevant to the issue if you need help.
For connection steps, see the Quick Start Guide; for routing and troubleshooting, see the Complete Guide.
Query privacy
We don’t log queries
Checks run through our API. This page doesn’t save query history or store results in your browser’s local storage. Copying happens only when you select the button, and copies only the IP address currently shown.
Your IP address is still network information. Before sharing screenshots or troubleshooting details, consider masking your public IP, and keep your account details and subscription links secure. See our Privacy Policy for details on how we handle information.