Public IP, geolocation, and DNS routing. Check which route your browser is using, then review your client’s split-tunneling rules.
Getting your browser’s current connection details…
These results apply only to your browser’s connection to our lookup API. Other apps may use different network routes.
The lookup API shows the public IP used for this request. With split tunneling enabled, our site may connect directly while AI tools or streaming services use international routes, so the IP shown here may differ from the one used by those apps.
To check a specific service, also review the rule-match log in your client. Our lookup results alone can’t confirm that another website uses the same public IP.
The country or region is based on IP geolocation data, not your device’s physical location. Services may use different databases and update them at different times. If the displayed location doesn’t match your selected route, check your split-tunneling rules and run the lookup again.
Streaming and AI services may also consider account region, session history, and other signals. A matching IP location doesn’t guarantee that a service will be available.
ISP usually identifies the network provider or hosting network associated with the public IP, not the local network your device is connected to. Proxy detection depends on whether the API provides a corresponding flag.
“Not detected” doesn’t guarantee privacy, and “detected” doesn’t mean your connection is faulty. If the API doesn’t provide this field, we’ll show “No status provided by API” rather than infer a result.
DNS translates domain names into network addresses. Even when web traffic uses an international route, DNS requests may take a different path. This page checks your public IP; it does not directly identify your DNS servers or determine whether a DNS leak test has passed.
Review your client’s DNS and split-tunneling settings to confirm that international domains use the expected resolution path. Direct connections for local websites may be part of your routing setup; seeing a local resolver alone doesn’t prove a leak.
Secure DNS or encrypted DNS in your browser may work independently of your system settings. Compare your browser configuration with your client’s DNS handling to make sure they aren’t sending DNS requests along an unexpected route.
If your client supports it, check DNS request logs and rule-match records. If you use a dedicated DNS test tool, verify which network the resolver belongs to and whether it follows the expected route. A resolver in a different region does not, by itself, indicate a leak.
After changing a setting, follow your client’s instructions to flush the DNS cache and reconnect. Then check again using the same browser and service. Change one setting at a time to see which configuration affects the result.
For client setup steps, see the setup guide. For differences in routing between AI websites and developer tools, see the complete AI guide.
We don’t log queries. This page retrieves results through a same-origin API, doesn’t fall back to a third-party public lookup service, and doesn’t save results in your browser’s persistent storage. When you copy results, they’re placed on your device’s clipboard. Keep this in mind when using a shared device.
Your IP address may reveal your network and approximate location. Consider masking the full IP before sharing screenshots. For details on how information is handled, see our Privacy Policy.