IP Lookup and DNS Checks

What These Details Mean

Your public IP is the source address for this request

This page uses a J6VPN endpoint to look up the public IP address used by your browser’s request. When you use a proxy route, this may be the route’s exit address; with a direct connection, it may be your network’s public IP. Per-app proxy settings, browser proxy settings, and client routing rules can send different apps through different exits. So these results can’t replace a check within the app you’re using.

IP geolocation and ISP data aren’t precise location tracking

Country, region, and ISP details come from IP geolocation databases. Update schedules, IP address assignments, and network operations can all affect the results. The displayed location doesn’t confirm where your device is, and streaming services or AI tools may determine your location differently.

Proxy detection is only an indicator

“Proxy detected” means the endpoint identified this address as a proxy-related exit. “No proxy detected” only means the check didn’t flag it; it doesn’t prove your connection isn’t working or guarantee any particular level of privacy. If the endpoint doesn’t return a proxy status, this page shows “Temporarily unavailable” rather than treating the missing result as a negative.

If the lookup fails, first check whether other websites load, then review your client and browser connection settings. This page won’t use a third-party public endpoint to fill in missing results. Try again later, or visit the Help Center to continue troubleshooting.

How to Check for DNS Leaks

DNS translates domain names into network addresses. A public IP lookup only shows the exit used for this web request; it can’t reveal where all DNS requests go. This page doesn’t run a DNS leak test or infer “no leak” from your exit location.

1. Check your client’s DNS settings. Confirm whether the current mode handles DNS resolution, and look for rules that send specific domains direct or use the system resolver. Enabling a proxy connection doesn’t necessarily change the DNS route.
2. Check your browser’s secure DNS settings. Your browser may use DNS settings that are separate from the system’s. Note the current settings and compare them with your client’s documentation to avoid overlapping DNS policies. Don’t enter an unfamiliar DNS server just to test.
3. Check your system’s network settings. Review the DNS servers configured for your active network adapter, including any manual settings, workplace policies, or settings left by other networking tools. The DNS address shown by your system reflects its configuration; by itself, it doesn’t prove where requests ultimately go.
4. Check diagnostic logs. If your client provides DNS diagnostics or connection logs, check whether requests for test domains follow the expected route. If you use a separate DNS testing tool, read its privacy policy and assess the results alongside the resolver’s ownership, client rules, and behavior in the target app—not just whether the displayed locations match.

If the results don’t match, save your current settings and change one thing at a time, checking again after each change. A difference between the resolver’s location and your exit location doesn’t automatically mean there’s a leak. What matters is whether the client handles requests as expected and whether DNS requests you intended to route through it are exposed.

A streaming account’s region, payment region, and route exit are separate factors. For help troubleshooting playback region issues, read the Complete Guide to Streaming Access.

Privacy and Lookup Limitations

We don’t log lookups. Requests are handled through a same-origin endpoint on this site. This page doesn’t save results in browser storage or fall back to a third-party public lookup service. Selecting Copy only copies your current public IP to the clipboard for your own reference.

Before submitting a support ticket or sharing a screenshot, make sure it doesn’t include subscription links, account passwords, or other access credentials. An IP address can also reveal network information, so share it only with the support channels that need it. For details on how the site handles data, see our Privacy Policy.