Same-Origin GeoIP Lookup
See the IP address, location, ISP and proxy status presented by your browser’s current connection. Lookups use only VPNWe’s own same-origin endpoint and are not sent to third-party public lookup services.
CURRENT CONNECTION
RESULT GUIDE
The results describe the network exit point shown when your browser request reaches this site. They can help confirm whether the connection path has changed, but they are not a complete privacy or security audit.
Your public IP is the network address visible to a website when it receives a request. Run a check before and after connecting to a VPNWe route to compare the address and its registered location. If the result stays the same, first check the client connection status, system proxy settings and whether the browser uses separate network settings.
The location comes from a GeoIP database’s assessment of the address associated with the network exit. Websites commonly use it for content regions, language and risk policies. Database updates can lag, so the result may not exactly match the route city or the provider’s registered location. Treat it as a network-affiliation reference, not precise location data.
The ISP field usually shows the network operator associated with the public IP. It can help indicate whether traffic is still leaving directly through the local access network or has switched to the selected route’s exit network. Some data sources may show an upstream network organization rather than the consumer-facing brand.
Proxy detection is a supporting signal returned by the GeoIP interface based on network attributes. “Detected” does not indicate a connection problem; it may appear when using a network acceleration route. “Not detected” does not mean every application uses the same exit. For verification, consider the IP change, target location and the behavior of the specific application together.
DNS CHECK
A changed public IP only shows that the browser request reached this site through a new exit. Domain resolution requests may still be handled by the system, router, browser or another resolver on the access network, so they need to be checked separately.
Before connecting to a route, check the DNS resolver or network settings currently used by the system and note the associated network. This gives you a baseline for comparison afterward and avoids judging a possible leak by an unfamiliar name alone.
After connecting to the required route, close and reopen the browser page, and clear the system and browser DNS caches if needed. Then check the resolver information again to confirm that requests are following the expected network path.
The browser’s secure DNS, the system’s custom resolver and the configuration provided by the router may differ. If a setting explicitly specifies another DNS service, confirm that it fits the current use case rather than checking only the client’s connection icon.
Per-app mode may route only selected programs through the route. Even when the browser check looks normal, other programs may use different exit points or DNS settings. For important apps such as meeting tools, streaming services and developer tools, verify their actual connection paths separately.