Check the IP address, location, and ISP visible to the outside world, along with proxy detection signals returned by the API. Results come from this site's same-origin lookup API, with no third-party public lookup service.
An IP lookup is useful for confirming an egress change, but a single result cannot replace a complete connection diagnosis. Consider the selected route, client status, and actual access together.
After connecting through an international route, the public IP should usually correspond to the selected route. If it does not change after switching routes, first confirm that the client shows an active connection, then check whether another network setting is overriding it.
Country or region data comes from an IP geolocation database, not device location services. Newly assigned address ranges, networks operating across regions, and database update timing can all cause the displayed result to differ from the route name.
The ISP in the result usually refers to the organization assigned the address range, the autonomous system name, or a data center network. It identifies the egress network and may not match the provider listed on your broadband bill. With transit or dedicated-line access, the ingress network and final egress organization may also differ.
Proxy detection depends on the network characteristics available to the API. “Not detected” only means that the API returned no matching signal; “Detected” does not by itself mean the connection is abnormal. Consider the actual use case as well.
The GeoIP lookup on this page can confirm only the egress used by the web request; it cannot prove that DNS requests follow the same route. Check DNS status in the client or your system's network diagnostics.
Check the selected route and the client's connection status, then reload this page. If the public IP does not change with the route, troubleshoot the connection itself before treating the issue as a DNS problem.
View the DNS servers and resolution path in the client's diagnostics or your system's network details. If DNS requests continue to use the local network while web traffic uses the selected egress, check the client's DNS takeover settings.
A resolver's region differing from the egress region does not necessarily indicate a leak. Public resolvers, anycast networks, and split-routing rules can all produce regional differences. The key question is whether DNS requests are still handled by an unexpected local network.
Privacy note LaoVPN does not log the IP, location, ISP, or proxy detection results returned by this page. Queries are sent only to this site's same-origin GeoIP API; if the API is unavailable, this page displays a failure notice instead of forwarding the request to a third-party public lookup service.