IP Address Check and Connection Details

What These Results Mean

Public IP Address: Where This Request Comes From

The public IP address is the source address our API sees for this request; it may differ from your device’s local network address. When you use a proxy or network acceleration route, your browser request may go through that route’s exit. Check before and after connecting and note the results to see whether your public IP has changed.

Results apply only to the browser request that made the lookup. Split tunneling rules may route different websites and apps differently, so a change on this page doesn’t mean every app is using the same route. If the result hasn’t changed, first check your client’s connection status, then confirm this page’s request is using the intended route.

Country / Region and ISP: Network Registration Data

Country and region indicate the location associated with the IP address in the database, not your device’s precise location. ISP refers to the relevant internet service provider or network organization; it may also show the network hosting the exit. Database updates, IP address transfers, and exit deployment methods can all affect the results.

If the location shown here differs from a streaming or AI platform’s region, follow the platform’s own guidance. Platforms may use different location databases and account rules. A single IP lookup can’t confirm catalog availability, account access, or payment region.

Proxy Detection: An Indicator, Not a Verdict

“Proxy detected” means the API identified the exit as an address associated with a proxy. “No proxy detected” only means the API didn’t flag it on this check. Neither result alone confirms whether your connection is encrypted or whether DNS is leaking. If the API can’t make a clear determination, this page will show “Temporarily unavailable.”

How to Check for DNS Leaks

DNS translates domain names into network addresses. A DNS leak generally means DNS queries aren’t following the expected proxy or tunnel route and are instead being handled by another resolver. To determine whether this is expected, check your client, system, and browser DNS settings together.

1. Confirm the expected route. Check your client’s connection mode, split tunneling rules, and DNS settings. Determine whether DNS resolution should be handled by the client or by a resolver configured in your system or browser.
2. Check your browser settings. Review your browser’s Secure DNS settings. Browsers may use a separate resolver. Don’t assume there’s a leak based only on the resolver’s location; check whether its requests follow the intended route.
3. Review DNS records. If your client provides DNS or connection logs, visit the target website after connecting and check the DNS queries and their actual routes. Distinguish the address that receives DNS requests locally from the resolver that sends queries out to the internet.
4. Verify after making changes. Reconnect after changing your settings. If needed, clear your system and browser DNS caches, then visit the target website again. Cached results may prevent a new lookup from being triggered, which can affect your assessment.

If you still can’t determine what’s happening, submit a support ticket through the user panel. Include your operating system, client connection mode, browser DNS settings, and the specific issue. Before sharing screenshots, hide subscription links, account credentials, and other sensitive information.