Network Check Tools

IP Address Lookup

See the network route used by your browser’s current request. Check again after connecting to a route and compare the IP address and location.

Current Connection Details

Results come from this site’s lookup API and may not reflect the connection route used by every app.

Waiting for lookup
Public IP Address
Not checked yet
Country / Region
Not checked yet
Internet Service Provider (ISP)
Not checked yet
Proxy detected
Not checked yet

Your current connection details will be checked when the page loads.

What These Details Mean

Public IP address: See where your request comes from

The public IP address is the source address seen by this site’s API. It is not your device’s local network address. Check it before connecting to a route, then connect and check again. If the address changes, this browser request is using a different exit point.

Split-tunneling rules may send your browser and other apps through different routes. The domain used for this site’s lookup may also be set to connect directly, so an unchanged IP does not mean every connection is unaffected. Check your client rules and test the app you want to use.

Location and ISP: Identify the exit network

Country, region, and ISP details come from IP geolocation data. They may differ from the route name, your device’s location, or the data center’s actual location. Records can also be out of date, so use them as a general reference, not for precise location tracking.

The ISP may appear as a data center operator or upstream network. This alone does not indicate route speed, reliability, or whether a particular platform will work.

Proxy detection: A reference, not proof of your connection

The proxy field reflects only what the API detects. “Proxy detected” does not identify the protocol in use, and “No proxy detected” does not prove that the request bypassed a proxy.

If the API cannot return a clear result, this page displays “Temporarily unavailable.” Missing information is not a negative finding and should not be used to infer anonymity or security.

Read the guide to checking your IP and DNS →

Check for DNS leaks

This page checks the exit details of HTTP requests only; it does not automatically test for DNS leaks. A changed public IP does not mean DNS queries use the same route.

Compare your client and system DNS settings

  1. Check what the client handles. Find out whether it only sets a system proxy or routes all device traffic. A system proxy alone usually cannot ensure that every app’s DNS requests use the route.
  2. Check the DNS route. Review the client’s DNS settings and query logs to confirm which resolver handles the domain. System DNS, browser secure DNS, and client DNS may use different routes.
  3. Check split-tunneling rules. Local and international services may use different DNS policies. A local resolver does not necessarily indicate a leak; what matters is whether the domain is resolved according to the expected rules. Check further if it is resolved directly when that was not expected.
  4. Rule out cached results. Clear the DNS cache as directed by your system or client, then reopen the service. Cached results may prevent a new query from appearing in the logs.
  5. Test the app itself. If the app still has issues, check whether it uses its own proxy or DNS settings. If you need help, note your system, client, rules, and error message. Do not share your full subscription link.

This page does not send requests to external testing sites or use third-party public APIs to fill in results. For a deeper check, see protocol and route reference. For your first setup, see the setup guide.

Lookup Privacy and Error Messages

Lookups are not logged. To return results, the same-origin API must process the source address of the current request. This page does not save results in browser storage or copy them to your clipboard automatically. It only attempts to copy the address when you click “Copy Public IP.”

If a lookup fails, the page displays “Temporarily unavailable” instead of sample data. Check your connection and try again, or switch routes and retry. A failure only means this request did not return usable results; it does not necessarily mean the route is faulty.

View the Privacy Policy →