Browser IP Check

Public IP and DNS Check

First check your browser’s current public IP, then verify the service you want to use. These results apply only to this lookup request and don’t verify connections from other apps.

Current Connection Details

Waiting for lookup

Public IP: Temporarily unavailable
Country or region: Temporarily unavailable
Internet service provider (ISP): Temporarily unavailable
Proxy detected: Temporarily unavailable

Enable JavaScript to check your current public IP through our service.

What These Results Mean

A change in your public IP is a starting point for checking your connection, not a guarantee that a particular website will work.

IP Address and Location

Your public IP is the network address our service sees when your browser sends a request. After connecting to a route, select “Check again” to compare the addresses before and after. With split tunneling, requests to this site may use your local network while requests to another service take a different route.

The country or region is based on IP databases and may not reflect your device’s actual location. Database updates can lag, and different websites may associate the same address with different locations.

ISP and Proxy Detection

The ISP field shows which network provider is associated with your public IP. It may display the name of a data center or upstream network rather than the brand of your current subscription.

Proxy detection is based on a flag returned by the lookup service. “No proxy detected” doesn’t mean you aren’t using a proxy, and “Proxy detected” doesn’t mean your connection has a problem. If the field is missing, we show “Temporarily unavailable” rather than treating an unknown status as negative.

After selecting a route in your client, check again, then open the AI tool or streaming service you actually use to verify access. For help organizing your setup, see Quick Start. If you run into connection issues, visit the Support page.

Check for DNS Leaks

This page checks the IP address used for HTTP requests; it doesn’t run a DNS leak test. A change in your public IP alone doesn’t prove that domain lookups are using the expected route.

Check Your DNS Routing

Review your client’s DNS settings and routing rules to confirm that the client handles lookups for the domains you want to access. Changing your browser’s proxy settings alone may not change how your system resolves domain names.
Check whether your browser has its own Secure DNS setting enabled. Your browser and operating system may use different resolvers, so check your client’s documentation rather than relying on the setting’s name alone.
Check your current resolver in your system’s network settings or diagnostic tools, then compare it with your client’s DNS logs or diagnostics. Caching, in-app DNS and remote resolution can all affect what you see.
If DNS requests aren’t taking the expected route, adjust the relevant settings first, then restart the app you want to use and test again. When configuring split tunneling, make sure local network resources remain accessible.

How to Interpret the Results

A difference between the resolver’s location and your public IP’s location doesn’t necessarily mean there’s a leak. Public DNS services, distributed networks and remote resolution can all cause this difference. What matters is whether DNS requests take the expected route and reach only the resolvers you intend to use.

A regular webpage can’t show how every app on your system handles DNS. This page doesn’t provide a “DNS security” verdict. To troubleshoot, note your client version, routing mode and any error messages, then describe the issue in a support ticket in the user portal.

Lookup Privacy and Error Messages

We don’t log lookups. Checks are sent only to our service and don’t fall back to third-party public lookup services. Results aren’t saved in your browser’s local storage. When you select Copy, only your public IP is written to the clipboard.

If the service times out, the network disconnects or the response is incomplete, the page will tell you. Check your connection and try again, or switch routes and retry. Missing information doesn’t mean your connection has failed; check access in the app you want to use.

View Privacy Policy →