VPNEnd / NETWORK CHECK
See which network endpoint this browser request uses. After connecting or switching routes, run the check again and compare the exit IP and location.
Preparing lookup.
Temporarily unavailableResults describe the request from this browser to our lookup endpoint; other apps may use a different route. Proxy status is based on the endpoint’s detection and does not, by itself, confirm a successful connection or privacy protection.
Check the exit IP first, then its location. Treat proxy labels and your actual access experience as separate signals.
This is the public IP address seen by the lookup endpoint, not your device’s local network address. When a client is active, the exit IP will usually change if browser traffic is routed through the selected route. If it hasn’t changed, check whether the browser matches a direct-connection rule and whether the client is handling that traffic.
Country and region are based on IP databases, not device location. Differences can arise from address allocation, database updates, or provider labeling. If the result doesn’t match the route name, check again and compare it with your client’s exit details. Don’t diagnose a route issue based on the location label alone.
The provider field may show an access network, data center, or upstream network; it may not say VPNEnd. It can help identify the exit network, but it cannot prove on its own that an address is a residential IP or that streaming or AI tools will work.
This page shows a proxy status only when the endpoint explicitly returns one. No proxy detected does not mean no proxy is in use. If the field is missing, you’ll see “Temporarily unavailable.” To check whether a service works, verify your account, its regional rules, and the connection in the app itself.
To compare: Check and save the result on your current connection, then enable the route you want and check again. Change one setting at a time to make it easier to identify what affected the exit IP. This page doesn’t store before-and-after results.
Your exit IP and DNS resolution are separate parts of a connection. This page checks your exit details; it doesn’t actively test DNS resolvers or certify that no leak occurred.
DNS translates domain names into network addresses. Even when web traffic uses an international route, DNS lookups may still use settings from your system, browser, or local network. Conversely, a resolver in a different region from your exit IP doesn’t necessarily indicate a leak; check your client’s DNS routing policy too.
If the exit IP has changed but only one app won’t open, see Troubleshooting. If you haven’t configured a client yet, start with the Getting Started Guide. For help, use the support ticket portal and share your platform, client settings, and steps to reproduce the issue. Remove account credentials and subscription URLs before sharing logs.
We don’t log lookups. This page gets exit details through our own endpoint, doesn’t persist results in your browser, and doesn’t fall back to a third-party public API. Copying only happens when you click the button. Results include your public IP, so hide any details you don’t need to share before pasting them on a public page or sharing a screenshot.
If the endpoint is unavailable, this page will show “Temporarily unavailable.” That means the lookup didn’t complete; it doesn’t mean your route is disconnected. See our Privacy Policy for more information.