My IP and location
See the public IP address our API actually sees, then compare it with the address before connecting. Results reflect this request only, not the network route used by every app.
IP lookup results
Ready to check- Current public IP
- Waiting for lookup
- Country / Region
- Waiting for lookup
- ISP / Network Provider
- Waiting for lookup
- Proxy detected?
- Waiting for lookup
This page will retrieve results through our API.
What this information means
Public IP: the source address seen by this site
Your public IP is the address used for this request, not your device’s local network address. Check again after connecting to see whether your browser’s public IP has changed. Split tunneling may route this site directly through your local connection. If the result is unchanged, check the client’s routing rules for this site before assuming the connection failed.
Location and ISP: useful for comparison, not precise geolocation
Location data comes from IP databases and may differ from the actual data center location. The ISP field may show a network provider, hosting company, or organization associated with the egress network—not necessarily your current broadband provider. Other websites may use different databases, so this page’s location result may not match how a particular service determines your region.
Proxy detection: not a security verdict
This field shows only the detection result explicitly returned by the API. A proxy detected does not mean your connection is risky; no proxy detected does not prove that you aren’t using one or indicate how anonymous you are. If the API returns no verdict, this page displays “Temporarily unavailable” rather than treating missing data as a negative result.
DNS leak check
This page checks your public IP; it does not test for DNS leaks. A change in your public IP alone cannot confirm that domain lookups are using the expected route.
- Note your current settings first. Check your client’s DNS and routing rules, and note whether your browser has its own Secure DNS setting enabled. Browser and system settings may differ.
- Check the resolution path after connecting. Review the connection or DNS logs available in your client to see which rules and resolvers were used for the domain. If you use a system DNS lookup tool, keep in mind that command-line traffic may not go through your browser’s proxy.
- Compare with the expected behavior, not just the location. If DNS lookups should go through the proxy but are still handled by your local network, check whether DNS follows the proxy, along with your routing rules and the browser’s separate resolution settings. With distributed DNS networks, the displayed location alone is not proof of a leak.
- Verify again after making changes. Follow your client’s instructions to clear the DNS cache, then make a new request and compare the DNS logs with the public IP shown on this page. Without DNS evidence, treat the result as “not yet verified.”
For connection setup steps, see Guides. If you’re having connection issues, visit the Help Center. Don’t repeatedly switch routes just to change the detection label.