Reads the egress information presented to websites by your current network connection, helping verify the route region, ISP and proxy detection status.
Results are retrieved from EQVPN's GeoIP endpoint after the page loads. No substitute data is generated when the endpoint is unavailable.
Retrieving current egress information
Compare the page results with the region of the route you plan to use to quickly confirm whether the egress changed as expected.
The public IP is the network address visible to the destination website. Refresh this page before and after connecting to a route. If the address and location change, traffic is usually being sent through a different egress. If nothing changes, first check the client connection, then verify that your browser or application is using the correct routing rules.
The country or region is inferred from an IP address database and does not represent the device's actual location. It is useful for checking the area of the current route's egress, but database updates may lag, and city-level data may point to the ISP's registered location.
The ISP field shows the network organization associated with the egress address. Home broadband, corporate networks, data centers and shared egresses may display different attribution names, helping indicate what type of network ultimately sent the request.
The result is based on network characteristics returned by the endpoint, not a definitive determination of the connection method. When troubleshooting access issues, consider it alongside the public IP, location, client status and actual access behavior rather than relying on a single label.
The public IP and DNS requests use different paths. GeoIP results on this page alone cannot prove that DNS requests are being forwarded as expected.
Connect to the route you plan to use and refresh this page, then note the public IP, country or region and ISP. If these fields still match the original network, troubleshoot the client connection or routing configuration before assessing DNS.
Check the DNS server attribution in the client's connection details or diagnostic tools. If DNS requests still use the original network while web traffic has switched to another egress, the DNS path may be inconsistent.
Make sure the client's DNS options match the current proxy mode. In rule-based mode, also check whether DNS queries are excluded from the proxy chain. After making changes, reconnect and verify the egress and DNS attribution again.