IP Lookup

What these details mean

Public IP: where this request originates

The public IP shown here is the address our lookup API sees for this request. It is not your device’s address on your local network. Whether enabling network acceleration changes your public IP depends on the client mode and routing rules. If this page or our API still uses your local network, the address shown may remain the same.

To compare, look up and copy your current IP, switch routes, wait for the client to connect, then select “Check again.” A changed address means the route used for this lookup changed; it doesn’t show that every app is using the same route.

Location and ISP: classifications from IP databases

The country, region, and ISP come from geolocation data returned by the API. Database updates may lag, and the ISP name may refer to the egress or hosting network rather than your current access provider. These fields don’t reveal your device’s precise location or confirm where a route is physically hosted.

Proxy detection: an indicator, not a connection verdict

This page shows “Detected” or “Not detected” only when the API explicitly returns a proxy detection result. If the field is missing, it shows “Temporarily unavailable.” “Not detected” doesn’t mean you aren’t using a proxy, and “Detected” doesn’t mean your connection is faulty. Check the app itself to confirm whether it works.

DNS leak check

DNS translates domain names into network addresses. Sending web traffic over an accelerated route doesn’t mean DNS requests take the same path. This page does not test for DNS leaks, and neither your public IP nor proxy detection result can prove that DNS is not leaking.

1. Check the client mode. See whether the client is using rule-based routing or another connection mode, and confirm that DNS settings follow that mode. With rule-based routing, different domains may use different DNS paths by design.
2. Check your browser settings. See whether the browser’s Secure DNS setting specifies a separate resolver. Browser, system, and client settings may each affect the DNS path.
3. Run a separate DNS test. To check which resolver handles your requests, use a dedicated tool that triggers test domain lookups and reports the DNS servers. This page does not automatically send requests to third-party testing services.
4. Compare results with the expected route. Consider the detected DNS servers alongside your client rules and local network setup. A difference between the DNS server’s location and your public IP’s location alone is not enough to conclude there is a leak.

If your settings appear consistent but you still have questions, describe your client mode, browser DNS settings, and the issue you’re experiencing in a support ticket through the user panel. Before sharing screenshots, hide account details and subscription links.