Public IP lookup
See the public IP used for this page request. Connect to a route and check again to compare results. This does not show the connection path used by every app on your device.
Current route
Waiting for data- IP address
- Temporarily unavailable
- Country / region
- Temporarily unavailable
- ISP / network provider
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
Enable JavaScript for an automatic lookup, or click Check again.
What this information means
IP address and location: where your request exits
The IP address is the public address seen by VPNS8’s API. Without an acceleration route, it usually matches your local network’s public IP. After connecting, whether it changes depends on the client’s routing rules. If browser requests still use your local network, this page may show the original address even when other apps use a route.
The country and region are based on an IP geolocation database, not your device’s precise location. Database updates can lag, and results may differ from the route name. To confirm that a route is active, check the client’s current route and whether the destination service is reachable as expected.
ISP and proxy status: useful clues, not definitive answers
The ISP usually identifies the provider associated with the public IP. It may instead show a data center or network carrier, and does not necessarily identify VPNS8. Proxy detection depends on the API’s capabilities: no proxy detected doesn’t prove that no proxy is in use, and a positive result alone says nothing about encryption or connection quality.
DNS leak check
DNS translates domain names into network addresses. Routing web requests through a selected route doesn’t mean DNS lookups follow the same path. This page checks only the public IP used for HTTP requests; it doesn’t run an active DNS leak test and can’t confirm that there are no leaks based on your IP alone.
- Check your client’s DNS settings. Confirm which resolver method is configured and whether DNS requests are routed through the selected route as expected. Settings names vary by client; refer to its interface and configuration guide.
- Check your browser’s Secure DNS settings. A browser may use a separately configured DNS resolver. Note the current settings, then check that they match the client’s routing setup. Changing one setting alone doesn’t mean every DNS request now follows a different path.
- Check the DNS resolvers in use. If you use a separate DNS test tool, review the listed resolvers and their networks, then compare them with your client’s configuration. A difference between the resolver’s region and your web traffic’s exit region is a clue to investigate, not proof of a leak.
- Recheck after changing networks. After switching networks or routes, verify the client connection, browser proxy, and DNS settings again. If something seems wrong, describe the issue in a support ticket. Don’t post a complete subscription link publicly.
Lookup privacy
Queries aren’t logged. Requests are handled through an API on this site’s domain. If the API is unavailable, this page won’t fall back to a third-party public API or substitute a sample address for the actual result.
The copy function writes the IP address only after you click it; it doesn’t read your clipboard. When sharing screenshots or submitting a support ticket, consider hiding unnecessary connection details, account information, and subscription links. See our Privacy Policy for details on data handling.