NETWORK INSPECTION
View the public address, location, and ISP used when accessing this site. Run another check after switching routes to confirm that the public IP changed with the selected route.
CURRENT EXIT
RESULT NOTES
This is the public IP address visible to this site. Compare results from before and after connecting to a route to confirm whether traffic is leaving through the selected endpoint. If the address is unchanged, first check the client connection, routing rules, and whether the current browser is covered by the proxy.
The location comes from an IP address database. It indicates the region registered or associated with the address range, not the device’s precise location. Database updates can take time, so recently reassigned ranges may temporarily show their previous location.
The ISP field identifies the network operator associated with the public address. Some data-center routes may show a hosting provider, data center, or autonomous system name instead of a familiar consumer-facing brand.
This result depends on the identification fields returned by VncVPN’s GeoIP API and is only an additional indicator of the current address. If the database provides no matching information, the page will clearly show “Temporarily unavailable” rather than infer a result from the address type.
DNS CHECK
A correct public IP does not mean every domain lookup follows the same path. This page checks GeoIP only and does not actively run multiple DNS probes.
Disconnect from the route and note the DNS service and public location currently used by the system. This provides a baseline and helps prevent the local network’s original DNS results from being mistaken for a connection problem.
After connecting to the target route, close pages that may retain old connections, then refresh the DNS cache using the method provided by your client or operating system. Reopen the site you want to check so old resolution records do not affect the result.
Check the DNS service location in the client diagnostics page or a trusted DNS testing environment. If the public IP has changed but DNS requests still use the original network, review the client’s DNS handling, routing mode, and custom system DNS settings.
Adjust only one setting per attempt, then reconnect and test again. This helps identify whether the issue comes from client rules, browser Secure DNS, system settings, or the current route itself.
PRIVACY NOTE
This page reads only the network attribution data needed for display through VncVPN’s own API. VncVPN does not log this query. If the API is temporarily unavailable, the result will show “Temporarily unavailable” and will not be routed to a third-party public lookup API.