NETWORK INSPECTION
Read the browser's current public IP, country or region, and ISP, along with the proxy detection status. Results come from VPNJB's same-origin GeoIP endpoint, not a third-party public lookup service.
CURRENT EXIT
RESULT NOTES
The result describes the network exit point seen by websites, not the address your device uses on a local network. Run the check again after switching routes to confirm whether the public IP changes.
Your public IP is the address websites see when your browser connects to them. After connecting to a VPNJB route, this should normally show the selected route's exit IP rather than the one assigned by your original network. If it does not change, first confirm that the client shows an active connection, then refresh this page.
The location is estimated from GeoIP data to help identify the approximate position of the current exit point. GeoIP data may be delayed or outdated, so treat it as a network troubleshooting reference, not your device's precise location.
The ISP field identifies the network associated with the exit point. Proxy status is shown exactly as returned by the endpoint. If the field is unavailable, this page displays “Unable to determine” instead of inferring a result from the ISP name.
DNS CHECK
Your public IP and DNS resolution path are separate things. This page reads GeoIP information only and cannot list every DNS resolver your device is using. Use your system's network tools to check the resolvers, then assess them alongside the current route status.
Connect to the route you want to use, return to this page, and run the check again. Record the public IP, country or region, and ISP to confirm that the result matches the selected route.
On Windows, run nslookup in a terminal to view the DNS servers; on macOS, run scutil --dns; on common Linux systems, run resolvectl status. Review the output only; no system configuration changes are required.
If the client is connected but the system continues using resolvers supplied by the original network, DNS requests may not be following the selected route. Reconnect to the route first; if the issue persists, check the client's DNS mode and system network settings.