Read publicly available information about your current network exit point, including your IP, location, ISP, and proxy detection status. This lookup only requests 40VPN’s same-origin GeoIP endpoint.
GeoIP results identify the public exit point used by the current request. They are useful for confirming a route change, but do not represent overall network quality or privacy on their own.
Websites and online services typically see this public address. If it changes after connecting to a route, your traffic is leaving through a different public exit point. Private addresses assigned to devices on a local network are not shown here.
The location comes from a GeoIP database mapping of the address range, not the device’s precise location. When an ISP adjusts its address ranges, database updates may lag, so the reported city or region can occasionally differ from the actual exit data center.
The ISP field identifies the network operator managing the current public exit address. When using an international route, it may show the name of the exit data center or upstream network rather than the broadband or mobile provider connected to the device.
This result uses the detection field returned directly by the GeoIP endpoint. Some address databases do not provide it, in which case the page shows “Unable to determine at this time.” Detection labels can vary with the address type and database update time, so they should not be treated as the sole basis for diagnosing a problem.
Your public IP and DNS requests provide two separate clues. This page checks your public exit point but does not enumerate DNS resolvers; verify DNS status through your client and system network settings.
Open the current client’s connection details and check whether DNS follows the selected route, or whether the client’s encrypted DNS and remote resolution options are enabled. Setting names vary by platform.
DNS entered manually in the system, secure DNS enabled independently in the browser, and resolution settings from other network tools can all override the client configuration. When several settings are present, first determine which one is actually active.
Reconnect to the route and run this lookup again. If the exit region does not match the selected route, check the connection or routing rules first. If the exit matches but domain resolution is abnormal, review the DNS configuration and cache.
After changing DNS settings, close and re-establish the network connection, then restart the affected application. Previous records may remain in the system or browser cache, so an immediate check may temporarily show the old result.