Public IP and Location

Public IP, Not Your Device’s Local Address

Your public IP is the address our interface sees when it receives your request. It isn’t your device’s address on your local network. Check it before connecting to a route, then check again afterward. A changed address can indicate that your request took a different path, but it doesn’t confirm that every app uses the same route.

Location and ISP Are Estimates

Country or region and ISP details come from IP geolocation data returned by the interface, which may not be up to date. The provider shown may be a data center operator or network resource holder rather than your local internet provider; this isn’t necessarily a fault. To see whether a route works for your needs, test the service you want to access.

Proxy Detection Doesn’t Confirm Your Connection

The proxy field reports the interface’s detection result; it doesn’t show your client’s connection status. “No proxy detected” doesn’t mean you aren’t using one, and “Proxy detected” says nothing about connection quality. If the interface doesn’t return this field, we’ll show “Temporarily unavailable” rather than treat missing data as a negative result.

To choose a route by region, see the route directory. For subscription import and connection steps, see the guides.

This page checks the route used by HTTP requests only; it doesn’t run a DNS leak test. A changed IP address alone doesn’t prove that DNS requests also use the intended route.

Check Your Client and Browser Settings

1. Confirm that your client shows as connected, check whether it’s in global or split-tunneling mode, and verify which rule applies to the website you’re testing. Don’t rely on your system proxy toggle to determine where all traffic goes.
2. Review your client’s DNS settings and local connection logs to check whether DNS requests are handled as expected. Settings vary by client, so follow the instructions in its interface.
3. Check whether your browser has Secure DNS enabled separately. Its DNS settings may differ from your system or client settings. Check your client’s compatibility guidance, and avoid changing everything at once.
4. After changing settings, clear the relevant cache or restart your browser as instructed by your client, then visit the site you want to test. Before using a dedicated DNS testing tool, find out what request information it collects.

A DNS resolver’s location may differ from your exit region without indicating a leak; public resolvers may also use distributed networks. Focus on whether the actual DNS path matches your expectations, not just on comparing place names. If you’re still unsure, describe your client, connection mode, and symptoms in a support ticket. Remove subscription details from screenshots before sharing them.