My public IP

What this information means

Public IP: where this request came from

The public IP is the address shown when the lookup request reaches our API; it is not your device’s address on the local network. With a proxy enabled, the IP will usually change if the browser request goes through the selected route. Per-app proxying, rule-based mode, or direct-connect rules for specific sites may mean this page still shows your local network’s public IP.

Location and ISP: registration details, not device location

The country or region and ISP come from the IP ownership data returned by the API. These details may be affected by address allocation and database updates. They do not pinpoint your device and may not exactly match the route name shown in your client. The ISP field may show the egress network, a hosting network, or the organization associated with the IP address.

Proxy detection: an indication, not proof of routing

“Yes” means the API identified the current public IP as a proxy. “Not detected” only means the check did not flag it this time; it does not prove that traffic is going direct. If the field is missing, the result will show “Temporarily unavailable” rather than treating an unknown status as a no. To check whether a proxy is working, compare the public IP, client rules, and the target app’s actual access results.

DNS leak check

DNS translates domain names into network addresses. Web requests and DNS lookups may take different routes, so a changed public IP alone does not prove that DNS is using the expected route. This page does not run an independent DNS leak test and will not report a “pass.”

1. Check the client mode first. Confirm whether the client is using rule-based mode, global mode, or per-app proxying, and check that the browser is included. If the connection works but an app’s public IP is unchanged, start by reviewing its rules.
2. Review DNS settings. Check whether the client handles system DNS and whether related requests are routed as expected. A browser’s Secure DNS setting may use a separate route, so check it alongside the client settings.
3. Review resolution logs. If your client provides DNS or connection logs, revisit the domain and check the resolver and request route. If the relevant request does not appear in the logs, do not assume that it was either leaked or secure.
4. Compare before and after connecting. Keep the browser and target website the same while checking the public IP and DNS route in each state. Change one setting at a time to avoid confusion from simultaneous changes to caches, rules, and routes.

For further troubleshooting, start with the DNS and app proxy guidance in the troubleshooting guide. If you need help, submit your system, client, connection mode, and error details through a support ticket in the user panel. Before sharing screenshots, hide subscription links, credentials, and other private information.