First check how your browser connects to the internet, then investigate individual apps. The results reflect the route used for this request, not necessarily the connection path used by every app on your device.
Current connection results
Checked via our API
Public IP
Temporarily unavailable
This shows the request address observed by our API, not your device’s address on the local network.
Country / region
Temporarily unavailable
Network provider / ISP
Temporarily unavailable
Proxy detected
Temporarily unavailable
Enable JavaScript to check your current connection.
Check your IP and location with the client disconnected, then check again after connecting. In rule-based mode, requests to this site may go direct, so an unchanged result doesn’t necessarily mean the connection failed. Also check the client’s current mode and the rules applied to the target app.
Location and ISP: Identify the exit network
Location data comes from IP databases and may be out of date. The ISP field may identify the data center or network operator associated with the exit IP, rather than the provider serving your device. These details can help identify the route’s region, but they can’t establish your device’s actual location.
Proxy detection: A signal, not a verdict
This page displays “Detected” or “Not detected” only when the API explicitly returns a proxy assessment. “Not detected” doesn’t necessarily mean the request went direct, and “Detected” doesn’t mean the connection is faulty. If the API provides no assessment, the result remains “Temporarily unavailable.”
Check for DNS leaks
Instructions · Not an automated test
Check whether your DNS route matches your expectations
DNS translates domain names into IP addresses. Routing web traffic through a proxy doesn’t automatically route DNS queries the same way. This page only checks your public IP; it can’t determine whether your DNS is leaking.
Open your client settings and review DNS, routing rules, and the current connection mode. Check that the target domain is resolved as expected under your selected rules. If you’re unsure, keep the client’s default settings and avoid combining configurations from multiple tools.
Check the DNS settings for your system network and your browser’s Secure DNS settings. A browser’s built-in DNS resolver may differ from the client’s. Assess the results in light of your current configuration rather than judging by the resolver’s location alone.
After connecting, reopen the target site and review any connection or DNS logs available in your client. The system command nslookup example.com can help identify the system resolver, but it won’t show browser-specific DNS or the behavior of every app.
If the DNS route is still unclear, save the relevant settings and error messages, then contact support through a ticket. Before sharing logs, redact account details, subscription URLs, and browsing history.
Queries and privacy
We don’t log queries. Checks are sent only to our API, with no fallback to third-party public lookup services. Copying happens only when you click the button, which copies the current results to your clipboard.
An IP address can reveal details about your network environment. Before sharing a screenshot or support ticket, consider who will be able to see it. If the API fails, this page shows “Temporarily unavailable”; it won’t reuse an earlier result or generate a substitute.