NETWORK / IP LOOKUP
See the network address your browser is currently using. Check it before and after connecting, then compare the address and location.
BROWSER EXIT
READ THE RESULT
This shows the request’s source as seen by our API. It is not your device’s address on your local network, and it doesn’t mean every app uses the same network route.
Your public IP is the address your browser presents to the internet for this request. Location comes from an IP address database and may differ from the route name or the server’s actual location. A change before and after connecting can indicate a different request route, but doesn’t by itself prove that all traffic uses the selected route.
The ISP field may identify an access provider, data center, or organization associated with the address. Proxy detection depends on the status provided by the API: “not detected” doesn’t mean no proxy is in use, and “detected” is not a security assessment. If the API returns no clear status, this page shows “Temporarily unavailable.”
IP unchanged? Check your routing rules firstYour client may be routing this site directly. Confirm the connection is enabled, check whether your browser traffic matches a proxy rule, then run the lookup again. Test other apps separately; this page alone can’t verify them. See the guide to checking your public IP, DNS, and individual apps.
DNS CHECKLIST
An IP lookup only checks the route used by this request; it can’t tell which DNS server resolved a domain. This page doesn’t run an independent DNS leak test, and an IP change doesn’t mean DNS has passed a leak test.
Check whether your client handles DNS and how its routing mode resolves domain names. If it provides DNS logs, verify that the target domain used the expected route. Setting names vary by platform and client, so refer to the actual interface.
Secure DNS in your browser, system DNS settings, and client rules may all be active at once. Note your current settings, then check them against your client’s guide. Don’t judge a leak by the DNS provider’s name or location alone, and avoid changing every setting at once.
If your client’s documentation allows it, clear the DNS cache, revisit the target domain, and check the new DNS records. If you also use a separate DNS testing tool, compare its results with your client’s routing rules to see whether the resolver is expected. Remember that the test site also receives network requests.
Note your operating system, client settings, connection mode, and what went wrong, then request help through a support ticket. Before sharing screenshots, hide subscription URLs, account credentials, and any network details you don’t want to disclose. For common issues, see Troubleshooting.
QUERY PRIVACY
We don’t log queries. Lookups use an API on our own domain; we don’t fall back to third-party public lookup services or save query history on this page. The Copy button writes the current IP to your clipboard only when clicked.
If the API is unavailable, this page shows “Temporarily unavailable” and offers an option to try again. A failed lookup doesn’t necessarily mean your connection is down; the API may be temporarily unavailable.
Your public IP is network information. Before sharing a screenshot, consider what details you want to make public. Read our Privacy Policy for details on how we handle site information, or see our Guides for connection setup.