Browser Network Diagnostics

Public IP and Location Lookup

See the network endpoint used by this browser request. Look up your IP again after connecting to a route to compare results. This does not mean every app on your device uses the same route.

Current Connection Details

Lookup Result

Waiting to check. JavaScript is required to retrieve your public IP details.

Public IP Address
Temporarily unavailable
Country or Region
Temporarily unavailable
ISP / Network Provider
Temporarily unavailable
Proxy Detected
Temporarily unavailable

What This Information Means

Public IP and Location

The public IP is the address our endpoint sees as the source of your request. If you use a proxy or VPN, this may be the route's exit address rather than your device's address on the local network. The country or region comes from an IP database, not your device's precise location. Database updates, address assignments, and exit-node deployment can all affect the listed location.

ISP and Proxy Detection

ISP usually refers to the network organization associated with the public IP. This may be a broadband provider, data center, or another network operator. Proxy detection is an assessment from the endpoint, not proof that a connection is working. Even if no proxy is detected, that does not mean your request did not go through a VPN. If a field is unavailable, this page will show “Temporarily unavailable.”

DNS Leak Check

DNS translates domain names into network addresses. A change in your public IP does not mean DNS requests are taking the same route. This page checks only your public IP; it does not run a DNS leak test, so it cannot confirm whether a leak is present or absent.

  1. Check your client's DNS settings. Make sure the client's DNS mode matches your expectations, and review how system DNS, proxy DNS, and routing rules interact. Note your original settings before making changes so you can restore them.
  2. Check your browser's Secure DNS settings. Your browser may use encrypted DNS independently of your system settings. Check the browser's network or privacy settings to confirm the resolver is what you expect. Don't infer the DNS route from the public IP's listed location alone.
  3. Use your client's diagnostics to investigate. If your client provides DNS logs or connection records, use a standard test domain to observe the resolution path. A resolver in a different region does not necessarily mean there's a leak. Consider encrypted DNS, routing rules, and the resolver's network deployment together.
  4. Reconnect and check again. After restoring your preferred settings, reconnect and check your browser's public IP. If domain lookups still fail or a particular app remains inaccessible, continue with the troubleshooting guide.

Privacy Notice

We don't log lookups. This page sends requests only to our endpoint, doesn't use third-party public lookup services, and doesn't save results in persistent browser storage. Results appear only on this page. Copying is initiated by the user; take care where you paste clipboard contents.

If the endpoint is temporarily unavailable, this page won't generate a substitute result. Try again later. If you need to submit a support ticket, describe your network environment, client connection status, and any error message. Hide subscription links, passwords, and other sensitive information. Read our Privacy Policy, or visit the Support Center.