Connection Check · Public IP Details

Public IP Lookup.

Check your browser’s current public IP, then connect to a route and check again. Compare the results to see whether this browser request followed the expected network path.

Current IP Details

Lookup via our API

Waiting for lookup. The check will run automatically when JavaScript is enabled.

Public IP
Temporarily unavailable
Country / Region
Temporarily unavailable
ISP / Network Provider
Temporarily unavailable
Proxy detected
Temporarily unavailable

This result applies only to the current request. It doesn’t mean every app on your device uses the same route. Proxy detection is not a substitute for checking your connection.

What this information means

Public IP: where this request came from

The public IP is the address our API sees for this request. It is usually different from your device’s address on the local network. If the address changes after you connect, this request is using a different exit. If it stays the same, check the client mode, browser routing rules, and current route before drawing conclusions; this alone doesn’t mean the client isn’t working.

Country, region, and ISP: database-based location details

The country and region come from an IP geolocation database, not your device’s live location. ISP identifies the provider or network organization recognized by the database, which may differ from the route name shown in your client. Database updates can take time, so if the location doesn’t match what you expect, check your current route and run the lookup again.

Proxy detection: an indicator, not a privacy verdict

This page shows a proxy detected or not detected result only when our API explicitly returns one. No detection doesn’t mean you aren’t using a proxy, and detection doesn’t tell you whether your connection is encrypted. This page can’t verify that military-grade encryption is active in your client, or determine whether streaming services or AI tools will work.

DNS Leak Check

DNS translates domain names into network addresses. Routing browser requests through your chosen route doesn’t automatically mean DNS lookups take the same path. This page checks only your public IP; it doesn’t run a DNS leak test or label the result as “passed.”

  1. Review your client’s DNS and routing settings to see how the current mode handles DNS lookups. If you use system proxy mode, also check apps that don’t follow the system proxy.
  2. Check whether your browser has its own Secure DNS setting enabled. Your browser, operating system, and client may use different DNS routes. Review them against your client’s documentation rather than relying on the reported IP location alone.
  3. For a more thorough check, use a reputable DNS testing tool to see which resolvers it detects, then compare them with your expected configuration. A resolver on your local network may warrant further investigation, but matching or different locations alone don’t prove a leak.
  4. After changing your settings, reconnect and check both your public IP and DNS results. Before sharing a screenshot, hide your public IP and account details, and never share your subscription link.

DNS checks generally require specialized tools that can observe DNS lookups; a standard GeoIP lookup can’t provide that evidence. If you’re unsure what a setting means, open a ticket in the user dashboard and include your client platform, connection mode, and a description of the issue.