Check your current public IP, then connect to your chosen route and check again. Results reflect only the network path your browser uses to reach this site’s API.
Location and proxy indicators come from the API response. They don’t confirm your device’s actual location, anonymity, or whether a service is available.
A change in your public IP is a starting point, not the whole picture. For a useful comparison, use the same browser and proxy mode before and after connecting.
Your public IP is the address our API sees for your request. If it changes after you connect, that request is using a different exit. If it hasn’t changed, check that your client is connected and that this site isn’t set to bypass the proxy.
The country or region is based on an IP geolocation database. Updates may lag, and the same address can appear in different locations on different sites.
An ISP usually identifies the network provider or hosting network associated with an address; it may not be your current broadband provider. An exit on a data center network doesn’t, by itself, indicate connection quality.
Proxy indicators depend on the API’s data and detection methods. “No proxy detected” doesn’t mean you aren’t using one. If the API can’t make a clear determination, this page shows “Unable to determine.”
To check whether AI tools or other apps use a proxy, review your client’s routing rules too. A successful browser check doesn’t mean command-line tools, IDEs, or every app use the same exit. See the AI Access Guide.
This page checks the exit for HTTP requests; it doesn’t run a DNS leak test. Your public IP alone can’t show whether domain lookups use the intended network.
A mismatch between the resolver’s organization, displayed location, and your exit location is a reason to investigate—not proof of a leak. Public DNS providers may use nearby access points or distributed infrastructure, and geolocation databases may show an organization’s registered address.
The more useful question is whether domains expected to use the proxy are still being resolved by a local network you didn’t expect. If something looks unusual, review your client rules, browser settings, and test results together instead of repeatedly switching routes based only on the displayed location.
VPNWN doesn’t log lookups. Your browser requests connection details only from this site’s GeoIP API. This page doesn’t save results in persistent browser storage. The copy button writes the current results to your clipboard only when clicked.
If the API is unavailable, this page clearly says “Temporarily unavailable.” It won’t display a sample address or fall back to a public third-party API. Try again later, or check your client connection and routing settings.
Before sharing results, note that they include your full public IP. Read our Privacy Policy to learn how data is handled. For help, describe the issue in a support ticket; don’t include your password or subscription URL.