Public IP and Location Lookup

What these results mean

Public IP: the address websites see

The public IP is the address our site identifies for this request. It may differ from your device’s address on the local network. If your browser’s request to our site goes through the selected route after you connect a client, the result will usually change. With rule-based routing, the request may still use your local network, so an unchanged result alone does not mean the client failed to connect.

Country, region, and ISP: clues about your exit

The country and region reflect how a database classifies the address; the ISP identifies the network provider or organization associated with it. Database updates, address reassignment, and network architecture can all affect the result. A region label is not a precise location and may differ from how a particular website classifies the address. When using streaming services or AI tools, check the service’s actual response.

Proxy detection: not proof of a successful connection

This field shows only an explicit proxy flag returned by the lookup interface. “No proxy detected” does not prove that the request did not pass through an intermediary, and “Proxy detected” does not mean the connection is faulty. If the interface returns no clear flag, this page shows “Temporarily unavailable” rather than inferring a result from the IP, ISP name, or location.

DNS Leak Check

DNS translates website domain names into network addresses. Routing webpage requests through your selected exit does not necessarily mean DNS requests take the same path. This page checks only exit information; it does not run a dedicated DNS test, so it cannot automatically report whether a leak is present.

1. Confirm the expected route first. Check the client’s connection, routing mode, and DNS settings. Identify which domains should use an international route and which should keep using local DNS. DNS requests handled locally by design are not automatically leaks.
2. Check browser and system settings. See whether your browser uses its own Secure DNS setting and whether your system has a custom resolver configured. These settings may interact with the client’s DNS handling. Save the original configuration before making changes, and avoid changing several options at once.
3. Check the resolver actually in use. If your client provides connection or DNS logs, check where DNS requests go when you open the domain in question. Before using a dedicated DNS testing tool, review its privacy policy. This page does not automatically send requests to external testing services.
4. Use logs to interpret the results. Compare the resolver you observe with your client settings rather than relying only on country names. A resolver’s location can differ from your exit location without indicating a leak. What matters is whether DNS resolution follows your expected routing and interception rules.

For help, use the support ticket portal in the user panel to describe your operating system, client mode, and the issue. Before sharing screenshots or logs, redact subscription links, access credentials, and any personal information unrelated to troubleshooting.