My IP and location

What these details mean

Public IP: reflects this request’s route only

The public IP is the address our endpoint sees for this request, not your device’s address on your local network. After turning on your client, confirm that it’s connected, then run another lookup. If the address changes, this request is using a different exit route. That doesn’t prove other apps are using the same route.

Rule-based mode routes traffic according to its destination, so lookup requests to this site may still use your local network. An unchanged IP doesn’t necessarily mean the client failed to connect. You can temporarily switch to global mode and compare again, then switch back to your usual mode. See the user guide for setup details.

Location and ISP: network data, not precise location

Country or region and ISP details come from IP geolocation data. They may differ from your device’s actual location and can be inaccurate due to IP allocation or outdated records. The ISP field may identify the exit data center or network operator rather than your home broadband provider. Don’t use it to determine someone’s address or identity.

Proxy detection: a database result, not a connection switch

“Proxy detected” means the endpoint identified the current exit IP as proxy-related. “No proxy detected” means only that the endpoint returned no positive match. If data is missing, the result is shown as “Temporarily unavailable”—an unknown result is never treated as proof that no proxy is in use. Check the client status, changes in your public IP, and access to the destination service to determine whether the connection is working.

DNS Leak Check

DNS translates domain names into network addresses. Sending web traffic over an international route doesn’t mean DNS queries take the same route. If DNS requests follow an unexpected path, you may run into access issues or send domain queries to an unintended resolver.

Check your client and browser settings first

1. Confirm that the client is connected, check whether it’s in rule-based or global mode, and see whether the client manages DNS. A webpage loading in your browser alone doesn’t confirm that everything is configured correctly.
2. Check your browser’s Secure DNS settings. A resolver selected in the browser may differ from the one configured in your client. Follow the client’s instructions to keep your DNS settings consistent, and avoid stacking settings from unknown sources.
3. To run your own test, use a tool that explicitly offers DNS leak testing. The test will generate DNS queries, so check how the tool handles data before you begin.
4. Compare the returned DNS providers with your expected settings. If you see an unfamiliar provider, first check whether it’s part of the infrastructure for your selected resolver. Don’t judge by country name alone.

After changing your settings, reconnect and test again on the same network. If the result is still unexpected, note your platform, connection mode, and the issue, then troubleshoot through a support ticket. Don’t post your full subscription URL publicly.