See the public IP address your browser uses to reach this site. After connecting to or switching international routes, check again to compare results.
Current Browser Connection
Connection Details
Waiting for lookup
Public IP
Temporarily unavailable
Country / Region
Temporarily unavailable
Internet Service Provider / ISP
Temporarily unavailable
Proxy detected?
Temporarily unavailable
Enable JavaScript to retrieve your current connection details through our API.
Understanding the Results
What the Results Mean
These details reflect the network route used for this request. They don’t show your device’s physical location or confirm that every app is using the same route.
Public IP & Location
The public IP is the address identified when our site receives your request. With network acceleration enabled, it may correspond to the exit point of your selected route. With split tunneling, this site may still use your local connection. Location data comes from IP databases, which may not be up to date and can’t pinpoint your exact location.
ISP & Proxy Detection
The ISP usually identifies the provider, network organization, or hosting service associated with an address; it may not match the route name. Proxy detection depends on the categories provided by the API. A detected proxy doesn’t mean your connection has a problem, and no proxy detected doesn’t prove your privacy is protected or that a particular service will work.
Compare Before and After Connecting
Save the current result, then follow the setup guide to connect and return here to check again. If the address hasn’t changed, first check whether your client is connected, whether your split-tunneling rules include the browser, and whether the browser has its own proxy settings. You’ll still need to visit the destination site to confirm it works.
Resolution Path · Manual Check
Check for DNS Leaks
DNS translates domain names into addresses. A changed public IP doesn’t mean DNS requests are taking the same route. This page’s lookup API doesn’t test for DNS leaks, so it won’t automatically report a pass or a leak.
Check your client settings. Review the DNS, split-tunneling, and system proxy options to see whether your current configuration handles DNS requests. Coverage can vary by connection mode, so don’t rely on connection status alone.
Check how your browser resolves domains. Secure DNS or encrypted DNS settings may use a separate resolver. Note your current settings and check your client’s documentation to confirm they’re configured as expected. Don’t disable security options just to test.
Compare DNS providers. If you use a separate DNS testing tool, compare the resolvers it reports before and after connecting, and check the route against your client logs. A mismatch between the DNS provider and exit location alone doesn’t prove a leak.
Test each app separately. Browser results don’t cover command-line tools, IDE extensions, or other apps. Check proxy and DNS settings in each app you need to use. If problems persist, submit a support ticket through the user panel.