Public IP check
See the public IP address our site receives. Check once before and once after connecting to a route, then compare the address and location.
Current connection details
Checked via our API- Public IP
- Temporarily unavailable
- Country / Region
- Temporarily unavailable
- Internet Service Provider (ISP)
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
Waiting for results. If your details don’t load automatically, select “Check again.”
What these results mean
Public IP: where this request came from
This is the public IP address received by our lookup API, not your device’s address on a local network. If your browser’s request uses the selected route while network acceleration is enabled, the result will usually show that route’s exit address. If the address hasn’t changed, check that your client is connected and that your browser is routed through it, then check again.
This check reflects only the path taken by this browser request. Other apps may use different routing rules, and IPv4 and IPv6 may take different paths. One result therefore can’t represent the exit address of every connection on your device.
Country, region and ISP: approximate IP data, not your exact location
Location and ISP details come from IP databases and may change as addresses are reassigned, networks are updated or databases are refreshed. They don’t show your device’s actual location or identify you personally. The ISP field may name a data center or upstream network provider rather than your service brand.
Proxy detection: an indicator, not a verdict on your connection
This page shows “Proxy detected” or “No proxy detected” only when the API explicitly returns a detection result. No detection doesn’t mean you aren’t using a proxy, and detection doesn’t mean your connection is faulty. If the API doesn’t return a detection field, the result is “Temporarily unavailable”—it isn’t assumed to mean no proxy.
Check the service you want to use, too. A changed exit address doesn’t guarantee access to a particular streaming region or AI tool. Services may also consider your account region, licensing terms and their own risk controls. See access support details for guidance on specific services.
Check for DNS leaks
DNS translates domain names into network addresses. The public IP check only observes requests to this site; it doesn’t check where your DNS requests go. This page doesn’t run a separate DNS leak test or declare a “pass” based on your IP location alone.
- Start by confirming your expected routing. Check your client’s DNS and routing settings to see whether the client, your system or your browser is expected to handle DNS resolution. Expected behavior varies by mode.
- Check your browser settings. See whether your browser has Secure DNS or a custom DNS resolver enabled. Browser settings and client rules may both apply, so consider your actual routing setup.
- Review DNS activity. If your client has a connection or DNS diagnostics view, visit the domain you want to check and review the resolver and matching rules. For further checks, use your system’s built-in network diagnostics. The system’s default resolver details don’t necessarily reflect the browser’s actual requests.
- Compare the paths, not just the locations. Check whether DNS resolution before and after connecting matches your settings. A resolver in a different region doesn’t by itself prove a leak; check whether requests bypassed the route you intended to use.
If you’re unsure, note your client’s operating mode, DNS settings and the issue you’re seeing, then contact support through the user dashboard. Before sharing screenshots, hide subscription URLs, access tokens and other sensitive account details.
Privacy notice
We don’t log queries. Checks are sent only to our API, with no fallback to a third-party public lookup service. To return a result, the API must process the public IP address for this request. This page doesn’t attach your user dashboard login token to the lookup request.
Your IP is copied only when you select the button. Before sharing a result publicly, consider hiding the full address. For details on how we handle service data, read our Privacy Policy.
If a check fails, try again later or check your network connection before reopening this page. A failure message alone doesn’t show that a route is unavailable or that your exit address is abnormal.