VPNCape / Network Check
Public IP Lookup
See the network route used when your browser connects to this site. Run another lookup after switching routes to check whether your public IP and location have changed.
Current Route
Lookup via our API- IP address
- Temporarily unavailable
- Country / Region
- Temporarily unavailable
- ISP / Network provider
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
No lookup results yet. Select “Check again” to view your current connection details.
Results apply only to this browser request and don’t show the routes used by other apps. If proxy detection returns no result, we show “Temporarily unavailable” rather than assume no proxy is in use.
Understanding your results
What this information tells you
IP address: check your public connection
This is the public IP address seen by our API, not your device’s private address on the local network. Check it before and after connecting to a route. If it changes, this request is using a different exit. If it doesn’t, check that your client connected successfully and that your browser isn’t excluded by a split-routing rule.
A changed exit IP doesn’t mean every app uses the same route. Command-line tools, IDE extensions, and other apps may use their own proxy settings, so check each one separately. You can also review the connection steps in Quick Start.
Location and ISP: identify the exit network
The country or region comes from an IP geolocation database. The ISP field shows the network provider or organization identified by our API. These describe the exit network, not your device’s precise location. Database updates may lag. If the displayed location doesn’t match your selected route, run the lookup again and report it through a support ticket in the dashboard. Don’t rely on this result alone to decide whether your connection has failed.
Proxy detection: a signal, not a verdict
Proxy status depends on the API’s data sources and detection criteria. A proxy detected result doesn’t mean a destination site will block access; no proxy detected doesn’t mean your traffic isn’t using one. Destination services may use different location databases and risk rules, so this page can’t replace checking whether the destination service itself is available.
DNS checks
How to check for DNS leaks
This page checks your public IP; it doesn’t run a dedicated DNS leak test. Your location shown above can’t confirm whether DNS requests are taking the expected route.
Start by clarifying the expected route
DNS translates domain names into network addresses. If your browser traffic uses the selected route but domain lookups still go through an unexpected local resolver, DNS and browsing traffic may take different routes. Some split-routing rules intentionally resolve local domains locally. That differs from setups where all domains should use a remote resolver, so first confirm what your configuration is meant to do.
Check your client and browser settings
- Open your client’s DNS or domain resolution settings. Check whether the client handles DNS requests and how split-routing rules resolve the domains in question. Available options vary by client version.
- Check your browser’s Secure DNS settings. A resolver set directly in the browser may differ from your client’s settings. Confirm that it matches your intended setup rather than judging security by the toggle alone.
- After switching routes, check your client’s DNS logs or diagnostics, if available, to verify the resolver and request path. Successfully opening a website doesn’t prove its DNS requests used the selected route.
- For an independent check, use a dedicated DNS test that can show where DNS requests came from, and interpret the results according to its methodology. A difference between the resolver’s location and your exit location isn’t, by itself, proof of a leak.
If your client says it’s connected but apps can’t access the network, see the Help Center for connection and split-routing troubleshooting. For differences between AI websites, APIs, and developer tools, see the Complete Guide to AI.
Lookup privacy
We don’t log lookups
This tool gets results through an API on our own domain, and we don’t log lookups. If the API is temporarily unavailable, we show an error instead of falling back to a third-party public API. The copy button copies only the current IP address, not any other fields.
When troubleshooting, share only the information that’s needed. Cover your IP address before sharing screenshots publicly, and don’t include your account password or subscription link. Read our Privacy Policy for details on how we handle data.