Network tools · Your browser’s public IP

Public IP Address Lookup

See where this browser request connects to the internet. Switch routes and run another lookup to check for changes. Results may not reflect the connection path used by every app on your device.

Current connection details

Lookup via our API

Waiting for lookup. Enable JavaScript to automatically retrieve your current connection details.

Public IP address
Temporarily unavailable
Country / region
Temporarily unavailable
Network provider / ISP
Temporarily unavailable
Proxy detected
Temporarily unavailable

Copy your public IP address once it’s available.

Location and proxy indicators are based on the API response and may be affected by database updates. Fields not returned by the API will show “Temporarily unavailable”; we won’t infer them from other information.

Understanding these results

Public IP address: the address used by this request

It may be assigned by your local network or by the route you’re using. With split tunneling, this site and your target app may use different routes. So an unchanged address here doesn’t necessarily mean the target app isn’t using a proxy.

Location and ISP: the network associated with the address

Country, region, and provider can help identify an exit point, but they don’t show your device’s precise location. Data center registration details may differ from the actual connection location. A region name alone also can’t tell you whether a streaming service or AI tool will work.

Proxy status: an indicator, not a definitive connection result

“Proxy detected” means the API flagged the address as a proxy. “No proxy detected” means only that it didn’t match the API’s proxy indicators; it doesn’t prove that traffic wasn’t routed through a proxy. If the API provides no determination, this page won’t make one up.

View connection and verification steps →

DNS leak self-check

DNS translates domain names into network addresses. Even if web requests use the expected exit point, DNS lookups may take a different route. This page checks your public IP address, not DNS leaks, so it can’t determine whether DNS is “passing” or “leak-free.”

  1. Check your client’s DNS settings. Confirm that domain lookups are handled by the proxy as described in your client’s documentation, and note which domains use local DNS in split-tunneling mode.
  2. Check your browser’s Secure DNS settings. Browsers may use their own DNS configuration. Compare it with your system and client settings; browser behavior may not reflect how all apps handle DNS.
  3. Check the DNS route, not just the location. For further verification, use a trusted DNS testing tool or your client’s diagnostic logs to see which resolver actually handles queries. A resolver in a different region doesn’t by itself indicate a leak.
  4. Verify again after making changes. Reconnect your client and reopen the target page, then check the public IP address and DNS route separately. A single IP lookup isn’t a complete test.

Lookup privacy

We don’t log lookups. To display results, your browser requests our GeoIP API, which identifies the public IP address used for this request. If the lookup fails, we won’t fall back to a third-party public API.

This page’s scripts don’t save lookup results in your browser’s local storage. “Copy IP” writes to your clipboard only when you click it. When sharing screenshots or troubleshooting records, consider masking any address details you don’t want to make public.

Read our Privacy Policy →