NETWORK · Public IP

Public IP Lookup

See the public IP used by this browser request. After switching routes, check again and compare the address and location.

Lookup Results

Our API

Retrieving information about this request’s public IP…

Public IP
Checking
Country or region
Checking
Internet service provider · ISP
Checking
Proxy detected
Checking

What this information means

Public IP: the address websites see

Your public IP is the address used when this request reaches our API. It is not your device’s local network address. When you connect through a proxy, this will usually show the selected route’s public IP if your client rules send the request through it. If our site is set to bypass the proxy, the result may still show your local network’s public IP.

First, check the result without a proxy connection. Then connect to your chosen route and select “Check again.” Compare results using the same browser and network. One browser’s result does not represent other apps, and IPv4 and IPv6 requests may take different paths.

Location and ISP: results from address databases

Country or region reflects how the API’s database classifies the public IP; it is not your device’s live location. The ISP is the network provider associated with that address, which may also be a data center or network operator. Database update schedules and IP allocation practices can cause discrepancies, so a location label alone cannot tell you whether a route is faulty.

Proxy detection: an indicator, not proof of your connection

“Proxy detected” means the API returned a corresponding detection signal. “No proxy detected” does not necessarily mean the request connected directly. If the API provides no clear result, this page displays “Temporarily unavailable” rather than making an inference from the IP or ISP name. To confirm your client is working, also check which rules were applied, whether the public IP changed, and how the target service behaves.

DNS · Path checks

DNS Leak Check

DNS translates domain names into IP addresses. A DNS path may differ from the expected one if a proxy connection is established but DNS requests still take another route. Public IP lookups and DNS checks are separate: this page does not read your system DNS settings and cannot confirm that you have passed a DNS leak test.

  1. Check your proxy scope first. Review the client’s current mode and routing rules to confirm whether the app you’re testing is included. In rule-based mode, some domains may intentionally connect directly.
  2. Then check your DNS settings. Review the client’s DNS configuration and confirm that DNS requests are routed as expected. Browser Secure DNS, system settings, and client configuration may each apply independently; consult your client’s documentation.
  3. Clear caches before testing again. Existing connections and DNS cache entries may persist after you change routes or DNS settings. Reopen the app you’re testing, then check the DNS path using your client’s local diagnostics.
  4. Check IPv6 separately. If your network and apps support IPv6, confirm that your client handles this traffic too. A changed public IP alone does not prove that DNS requests and other address types are also routed through the proxy.

A different DNS provider name or location alone does not prove a leak. What matters is whether requests follow your configured rules. If you need help, use a support ticket in the user panel and include your operating system, client, connection mode, symptoms, and network conditions. Before sharing diagnostic screenshots, hide account details and subscription links.

Privacy and Query Limits

We do not log queries. This page requests public IP information only from our API; it does not use third-party public lookup services or require account details. The Copy button writes the current public IP only when clicked and does not read your clipboard.

If the API is temporarily unavailable, this page will say “Temporarily unavailable.” That means no valid result was retrieved; it does not mean the route is down or that a leak was detected. Try again later. For connection troubleshooting, visit the Help Center; for details on data handling, see our Privacy Policy.

Start Free