ZONE VECTOR · Egress Check
Current Public IP Lookup
See the public IP address used when your browser connects to this site. Check again after switching routes to confirm whether this request uses the expected egress.
Egress Details
- Current Public IP
- Temporarily unavailable
- Country / Region
- Temporarily unavailable
- Network Provider / ISP
- Temporarily unavailable
- Proxy Detected
- Temporarily unavailable
Results apply only to this browser request.
This tool checks egress metadata; it does not test for DNS leaks. Missing fields do not necessarily indicate a connection problem.
What This Information Means
Egress Address vs. Device Location
The public IP is the network address this site sees for the current request. When you use a network acceleration service, it may belong to the selected route's egress network rather than your device's local network. Split-tunneling rules, browser proxy settings, and connection status can all change the path this request takes.
The country or region is based on IP geolocation data, not your device's precise location. Records may be out of date or differ from a route's label or the data center's actual location. To confirm a route change, check the client connection status, which rules were applied, and whether the egress address changed.
ISP and Proxy Detection
An ISP usually identifies the provider or hosting network associated with the egress address; it may not be your local internet provider. This name helps identify the egress network and does not indicate route speed or reliability.
Proxy status is information returned by the lookup service. A proxy detection result does not mean the connection is faulty, and no detection does not prove the request bypassed a proxy. If the service returns no definitive result, this page shows “Temporarily unavailable” rather than inferring one from the address or provider name.
DNS Leak Check
DNS translates domain names into addresses that devices can connect to. A changed public IP does not mean DNS queries use the same route. This page's GeoIP service cannot observe every DNS request, so it does not automatically declare a test passed or a leak detected.
- Record a baseline before connecting.Note the egress location while the acceleration service is disconnected, along with your system's current DNS settings. Avoid sharing network screenshots that contain account information.
- Check the client's DNS rules.Connect to the target route and confirm that the client handles DNS as expected. If you use per-app or domain-based routing, make sure the request you're checking matches the relevant rule.
- Check your browser's secure DNS settings.The browser may use its own resolver, separately from the system or client settings. Compare its behavior with your intended setup; a resolver in a different region alone does not prove there's a leak.
- Verify against DNS query records.For a hands-on test, use a trusted DNS testing tool or query records for a domain you control, then compare the resolvers observed with your expected configuration. This page does not automatically send requests to external testing sites.
- Check again after making changes.Follow the client instructions to clear DNS caches and restart relevant apps, then check your egress IP and verify the resolution path again. If results still differ, you can submit diagnostic details with sensitive information removed.
Resolvers may handle queries through forwarding or distributed networks. The resolver, egress, and device may all be in different locations; assess the results alongside your configuration and observed records.