CURRENT EGRESS
Current exit results
Fetching network information through this site’s API…
- IP address
- Checking
- Country / Region
- Checking
- ISP
- Checking
- Proxy status
- Checking
NETWORK CHECK Same-origin lookup tool
Read the IP, location and network provider information visible to websites. Run the lookup again after switching routes to confirm that the exit region changed as expected.
CURRENT EGRESS
Fetching network information through this site’s API…
RESULT GUIDE
Your public IP is the network address seen by websites and online services. With a global connection enabled, it usually corresponds to the current route’s exit. With split routing, whether this page uses the accelerated route depends on whether the client rules match this site.
Location is inferred from an IP database and is useful for checking regional routing, but it is not the device’s actual location. Database updates may lag, and city-level results can point to a nearby area, so first verify that the country or region matches your expectation.
The ISP field identifies the network operator or data center associated with the exit. Some APIs return an organization name, while others provide only a network number. A missing field does not affect the IP or location result.
This field indicates whether the API identifies the current address as a proxy-type network. Detection criteria and update times vary between databases, so use the result only for troubleshooting—not as a substitute for real access tests or client logs.
DNS CHECK
DNS converts domain names into network addresses that can be reached. When traffic uses the selected route but name resolution is still handled by the original network, the resolver’s location may not match the exit region. This can lead to unexpected regional results or unstable connections to some sites.
Use the result card above to record the IP, country or region and ISP. With split routing, also confirm which rule matched when the browser accessed this page.
Open the connection details in your current client and check whether DNS is enabled with the route configuration. If a manually specified resolver is still present in the system, confirm that it fits the current network setup.
Use your system network diagnostics or the client’s built-in DNS check to view the resolver’s location. The resolver does not need to be in the same city as the exit, but if it continues to point to the original network unrelated to the target route, check DNS handling and split-routing settings.
After changing the DNS configuration, disconnect and reconnect, then clear the system and browser DNS caches. Return to this page to check the exit again and retest the service that previously showed an unexpected regional result.
PRIVACY NOTE
Lookup requests are sent only to UWVPN’s same-origin GeoIP API. This site does not log lookup content or forward failed lookups to public lookup services. If the API is temporarily unavailable, the result card will display “Temporarily unavailable.”