IP Check & Public IP Verification
See where this browser request is coming from. After connecting or switching routes, check again and compare the result with access in the app you’re using.
Current connection details
Waiting for check- Public IP
- Temporarily unavailable
- Country or region
- Temporarily unavailable
- Internet provider / ISP
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
Enable JavaScript to check your current public IP. If no data is returned, we won’t show an estimate.
This check covers only browser requests to this page’s API. It doesn’t represent other apps or test for DNS leaks.
What these details mean
Public IP: the address seen by this request
Your public IP is the address our API sees as the source of this request. Check it before connecting to a route, then check again to see whether your browser’s public IP has changed. If it hasn’t, first confirm that the client is connected and that routing rules aren’t sending this site over your local network. A changed address alone doesn’t confirm that every app is connected as expected.
Location and ISP: network details from IP databases
The country or region reflects how an IP database maps the address; the ISP identifies the provider or network organization associated with it. These details don’t pinpoint your device, and they may not exactly match a route’s name. Database updates, address assignments, and differences in how services determine location can all lead to discrepancies. Check the region shown by your destination site separately.
Proxy detection: an indicator, not a connection verdict
Proxy detection depends on the data available to the API. “No proxy detected” doesn’t mean you aren’t using an accelerated route; “Proxy detected” doesn’t mean there’s a connection problem. If the API doesn’t provide this field, we’ll show “Temporarily unavailable” rather than treat missing data as a negative result.
DNS leak check
DNS translates domain names into network addresses. Changing your public IP doesn’t mean DNS requests are taking the expected route. This page only queries a GeoIP API and can’t observe the full DNS resolution path, so it won’t automatically report that “DNS is not leaking.”
- Confirm the expected route. Check DNS and routing settings in your client, and determine which domains should use the route and which should resolve locally. You need to know what to expect before you can spot a problem.
- Check your browser settings. See whether Secure DNS or a custom DNS service is enabled. Browser settings may differ from your system settings. Note the original settings before making changes to avoid disrupting your setup.
- Inspect DNS requests. For a closer check, use a DNS testing tool you trust or local network diagnostic logs to see which services handled resolution. This will send additional requests to the tool; review its privacy policy before using it.
- Interpret results alongside your rules. A local DNS resolver doesn’t necessarily indicate a leak; it may be part of your intended routing setup. Check the test domain, client rules, and resolver together, then test again after changing your configuration.
If the app you’re trying to use is still inaccessible, don’t just keep switching regions. First determine whether the issue is DNS resolution, connectivity, or an account region restriction. Then check your client settings with our Guides, or continue troubleshooting in the Help Center.