Connection Check / Browser IP

Public IP Lookup

See where your browser’s connection to this site appears to come from. Switch routes and check again to see whether your public IP changes. This result applies only to this request, not every app on your device.

Current public IP

Lookup via this site

Getting your result ready.

Public IP
Waiting for lookup
Country / Region
Waiting for lookup
ISP / Network Provider
Waiting for lookup
Proxy detected
Waiting for lookup

Geolocation comes from an IP database and may be out of date. Proxy detection is not a security assessment and cannot confirm whether DNS is leaking.

What this information means

Public IP: the source address this site sees

Your public IP is the address used when your browser connects to this site. It may belong to your local ISP or to the current route’s exit. If your client proxies only some websites, requests to this site may take a different path from traffic in other apps. This address may not represent your entire device.

Country or region and ISP: address information, not your precise location

Country or region indicates how an IP database classifies the address geographically; it does not locate your device. ISP usually refers to the network provider or organization associated with the address, which may differ from the brand of the service you purchased. Route changes, IP reassignment, or database delays can cause results to differ from what you expect.

Proxy detection: a reference only

This page shows proxy detection results only when the API explicitly provides them. “No proxy detected” does not mean your connection definitely isn’t using a proxy, and “Proxy detected” does not mean the connection is unsafe. If the API doesn’t return this field, the page shows “Temporarily unavailable” rather than inferring a result from your IP or ISP name.

How to check for DNS leaks

DNS translates domain names into addresses used to connect. Even if web traffic goes through your selected route, DNS queries may still take a different path. A public IP lookup checks the source of web requests only; this page does not test DNS and cannot report that there is “no leak.”

  1. Check your client’s DNS settings. Confirm whether DNS interception or a related DNS mode is enabled in your client. The setting’s name depends on the client. Changing your exit location alone may not change the DNS route.
  2. Check your browser’s Secure DNS settings. Your browser may use its own encrypted DNS settings. Check these alongside your client configuration to avoid the browser and system using different DNS routes. Encrypted DNS does not, by itself, mean DNS queries go through your selected route.
  3. Compare DNS lookup results. If you choose to use a DNS testing tool, review its privacy policy first, then compare the resolver lists before and after connecting. A resolver’s name or location differing from your exit IP is not enough on its own to establish a leak; also consider your client settings and actual routing.
  4. Test again after making changes. Clear the relevant DNS cache or reopen your browser, then check your public IP and DNS route separately. For help, use a support ticket in the user panel and describe your operating system, routing mode, and the issue. Don’t include your password or full subscription link.

Lookup privacy

We don’t log lookups. This page gets results through our own API and does not fall back to third-party public lookup APIs or save results in your browser’s local storage. When you click “Copy IP,” only your public IP is copied to the clipboard; geolocation and ISP details are not copied automatically.

An IP address may still reveal information about your network. Before sharing a screenshot or submitting a support ticket, check that it doesn’t include information you don’t want to disclose. For details on how we handle service data, read our Privacy Policy.