My IP and location
Check the public IP address your browser is currently using. Run the lookup again after connecting to compare addresses. This result does not verify the connection of your entire device.
Current lookup
Checked via our APINo results yet. The lookup will run automatically when JavaScript is enabled.
- Public IP address
- Temporarily unavailable
- Location
- Temporarily unavailable
- ISP / network provider
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
Understanding the results
Public IP address and location
The public IP address is the one our API sees when it receives this browser request. It is not your device’s local network address. Location comes from an IP geolocation database and may differ from the route name or your device’s actual location. It cannot pinpoint a street address.
Before connecting, copy your address for comparison. After connecting, select “Check again.” If the address hasn’t changed, check that your client is connected and that your browser traffic isn’t set to bypass the route. If only some apps use the route, this result reflects only this browser request.
ISP and proxy status
ISP identifies the network or provider associated with the address. It may show a data center or network service provider rather than your local broadband provider. Proxy status reflects only what the API explicitly reports. No proxy detected doesn’t prove the connection is direct, and a proxy detected result doesn’t mean there’s a connection problem.
Fields not provided by the API appear as “Temporarily unavailable.” If a location or status differs from what you expect, check your client’s status and how the destination website behaves. Don’t draw conclusions from a single lookup.
DNS leak check
DNS translates domain names into network addresses. Browser requests and DNS lookups can take different routes, so an expected location for your public IP doesn’t prove that DNS requests use the same route.
- Check your client settings. Confirm the route is connected, then review your DNS settings, routing rules, and system proxy mode. Enabling the system proxy alone doesn’t guarantee that all system requests use the route.
- Check your browser settings. Secure DNS or encrypted DNS in your browser may work independently of your system settings. Note the current settings first, then compare them with your client’s instructions. Avoid changing multiple settings at once, so you can identify the cause.
- Compare resolver results. If you use a dedicated DNS test, review its privacy policy and note which networks the resolvers belong to before and after connecting. Resolver locations are estimates and don’t need to match your exit city exactly.
- Check one issue at a time. If DNS requests still take an unexpected route, review your routing rules and DNS cache. Reconnect and test again. Keep a copy of your original settings so you can restore them.
For further troubleshooting, start with the getting started guide. When you contact support, include your platform, connection mode, and a description of the issue.
Queries and privacy
We don’t log queries. Lookups use only our same-origin API and won’t fall back to a third-party public lookup service if the API is unavailable. The API needs to identify your public IP address to process the request. No sign-in is required, and lookup results aren’t saved in your browser’s local storage.
The Copy button writes your public IP address to the clipboard only when clicked; it doesn’t read clipboard contents. Before sharing screenshots or troubleshooting logs, redact your IP address as needed. Don’t include account passwords or subscription links. Read our Privacy Policy for details.