Public IP & Network Check
See where your current request connects to the internet. Run the check again after switching routes to compare your browser’s public IP. DNS leaks need to be checked separately.
Current connection details
Lookup via our APIPublic IP address
Temporarily unavailable
- Country or region
- Temporarily unavailable
- Internet service provider (ISP)
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
Preparing lookup. Missing data won’t be replaced with sample results.
Results apply only to the request this page sends to the lookup API; other apps may use a different route. Any field the API doesn’t return will show “Temporarily unavailable.”
What this information means
Connection details can help you check your route, but they don’t prove your privacy is protected.
Public IP address: the address websites see
This is the address your request presented to the server—not your device’s address on a local network. If it changes after you connect, the request is using a different route. If it doesn’t, check that your client is connected and that your browser isn’t excluded by split-tunneling rules.
Location and ISP: IP data, not precise location
Location and ISP details come from IP data supplied by the lookup API and may not be up to date. The displayed region may not be where your device is, and the ISP may identify the data center or network operator hosting the exit point. Don’t use this information to pinpoint a device.
Proxy detection: an indicator, not a connection verdict
This page displays a proxy assessment only when the API explicitly provides one. “Proxy detected” doesn’t mean your connection has a problem, and “No proxy detected” doesn’t prove you aren’t using one. If the field is missing, it shows “Temporarily unavailable” rather than treating it as a negative result.
Check for DNS leaks
This page checks your public IP only. It doesn’t run a DNS leak test or automatically determine that no leak occurred.
DNS translates website names into network addresses. If app traffic uses the intended route but DNS queries still go to an unexpected resolver, check the DNS path. A change in public IP alone can’t tell you where DNS queries are going.
-
First, check your client’s DNS settings
Review the connection mode and DNS interception options, and make sure DNS behavior matches your routing rules. If only browser proxying is enabled, other programs on your system may still use the original network settings.
-
Next, review browser and system settings
Browser Secure DNS, the resolver configured on your system and other networking tools can all affect the DNS route. Note your current settings, then make changes according to your client’s documentation. A resolver’s brand name alone doesn’t tell you whether a leak is occurring.
-
Verify against actual DNS query records
If your client provides DNS request logs, check which component handled each query and which resolver it went to. For a dedicated test, compare the resolver information from a trusted test tool with your intended configuration. A difference between the resolver’s region and your exit region alone isn’t enough to establish a leak.
After changing settings, reconnect, check your public IP again and verify the DNS route. If the issue persists, describe your platform, connection mode and symptoms in a support ticket in the user panel. Before sharing screenshots, hide subscription links, credentials and other personal information.
We don’t log queries
Checks are sent only to our GeoIP API. This page doesn’t write results to persistent browser storage or save lookup history. If the API is unavailable, we won’t query a third-party public API instead.
The server needs to receive the public IP for this request to return location details. Copying writes only the IP currently shown to your clipboard; it doesn’t send it to another website. On a shared device, remember to clear your clipboard when you’re done.