Public IP & Location
See where this request reaches VPNBX from. After switching routes, check again and compare the result with your expected location.
Current results
Waiting for results- Public IP
- Temporarily unavailable
- Country / Region
- Temporarily unavailable
- Internet service provider (ISP)
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
Understanding the results
Public IP: the address seen by VPNBX
Your public IP is the address seen by VPNBX’s API, not your device’s address on the local network. When you connect to a route, this lookup will usually show its exit IP if your browser traffic goes through it. Check once before connecting, then check again after connecting to your chosen route and compare the IP and location.
These results apply only to the path your browser uses to reach VPNBX. Split-tunneling rules may send VPNBX traffic over your regular connection while routing a target app through a different route. Your browser’s proxy settings may also differ from your system settings. If the IP hasn’t changed, check your rules before deciding whether the connection is working. A changed IP also doesn’t mean every app uses the same exit.
Country, region, and ISP: information from IP databases
Country and region are based on IP geolocation databases, not your device’s live location. Database updates can lag, and different sites may identify your location differently. The ISP field may show a network operator, data center, or organization associated with the exit IP—not necessarily your local internet provider.
If the location doesn’t match your selected route, first check which route is active and review your browser rules, then run the lookup again. If a site still shows a different location, check its account region, cached data, and location-detection rules. Don’t rely on this page alone to determine the cause.
Proxy detection: an indicator, not proof of connection status
“Proxy detected” means the API flagged the exit IP as a proxy. “No proxy detected” only means the API returned no positive flag; it doesn’t prove your traffic isn’t using a route. If this field isn’t returned, the page shows “Temporarily unavailable” rather than treating the missing value as a negative result.
To verify your connection, consider the IP check alongside access to the target app. For a full walkthrough, read the Getting Started Guide. To compare locations and route types, see the Route and Node Guide.
How to check for DNS leaks
DNS translates domain names into addresses your device can connect to. Routing web traffic through a route doesn’t guarantee that DNS requests follow the same path. This page checks only the exit IP for HTTP requests; it does not run a DNS leak test or label the result “passed” or “leaked” based on your IP.
Start with your client and browser settings
- Confirm that your client is connected and check its current routing mode. Note which rules apply to the target app and to VPNBX so you don’t compare results from different paths.
- Review your client’s DNS settings or diagnostics to confirm that DNS requests follow the expected route. Pay particular attention to how system DNS, client DNS, and remote resolution are handled.
- Check your browser’s Secure DNS settings. The browser may choose its own DNS resolver instead of using your system or client settings. Review your routing rules to understand which path it takes.
- If your client provides connection logs or DNS diagnostics, check the same domain name there. After changing settings, revisit the target service and check both the exit IP and DNS path.
A DNS resolver’s location not matching your exit location doesn’t automatically mean there’s a leak. Resolvers may use distributed networks, and databases may list the location of the organization that operates them. Check whether requests follow the expected path rather than comparing locations alone.
For further help, sign in and submit a ticket through the user panel. Include your client platform, connection mode, and a description of the issue. Before sharing screenshots or diagnostic excerpts, hide subscription URLs, access credentials, and other personal information.
Query privacy and limitations
VPNBX does not log lookups. Requests go only to VPNBX’s API to retrieve your current exit information. If the API is unavailable, this page won’t switch to a third-party public lookup service.
You don’t need to enter an account or subscription URL to run a lookup. The copy button copies only your public IP, not the other fields. A public IP may reveal information about your network, so consider hiding it before sharing screenshots. For details on how VPNBX handles data, see the Privacy Policy.