Public IP
This is the network address that websites can typically see. Run a lookup before and after connecting to a route. If the result changes, the request is using a new exit. IPv4 and IPv6 may both be present, so the format can vary by network.
Network Exit Diagnostics
IP Lookup & Exit Check
Read the IP, country or region, ISP, and proxy status visible to the public for your current connection. Results come from H5VPN's same-site GeoIP endpoint, with no third-party lookup service.
Current network exit
Same-site endpoint
Results not logged
Current lookup result
Current exit information
The lookup runs automatically when the page opens. After switching networks or routes, run it again to compare the results.
Fetching current exit information
- Public IP
- Checking
- Country or region
- Checking
- ISP
- Checking
- Proxy detected
- Checking
Field guide
What this information means
A single lookup shows the exit information visible to the public after the current request leaves the network. Use it to confirm whether a route has changed and whether the location matches your needs.
Country or region
The location is determined from GeoIP data and reflects where the address range is generally registered or used, not the device's exact location. Databases may lag behind recent changes, so some addresses can briefly show their previous region after a route change.
ISP
The ISP field identifies the network operator or data center associated with the exit address. It comes from address registration data and may show a corporate group, autonomous system, or facility operator rather than the company providing your current access.
Proxy detection
The result comes from the address-type label supplied by the GeoIP endpoint and is only a supporting signal. Databases use different classification rules; a data center address may be marked as a proxy even when the route is working normally, so this alone cannot determine connection quality.
DNS Resolution Path Check
DNS Leak Check
A changed exit IP does not mean DNS requests follow the same path. A DNS leak typically occurs when web traffic uses the intended route while domain lookups are still handled by resolvers from the original network. Websites may load normally even though the resolution path is not what you expect.
-
Record the pre-connection state
Disconnect the accelerated connection, record your current public IP, and check the DNS server details in your system network settings or client connection logs.
-
Run another lookup after connecting
Connect to the target route, then click “Check again” on this page. Confirm that the public IP and country or region changed as expected before checking DNS.
-
Verify the DNS source
Review the client connection logs or system network details. If DNS still points to resolvers provided by the original access network, check the client's DNS takeover, encrypted DNS, and system proxy settings.
-
Clear the cache and check again
Your system and browser may retain old DNS cache entries. After changing settings, reconnect, close pages opened earlier, and check the exit and resolution paths again.