The public address your browser presents when accessing the internet.
Network Egress Check
Current Public IP Lookup
See the public IP, location, ISP, and proxy signals currently presented by your browser. Results come from VPNRZ's same-origin GeoIP endpoint, making them useful for comparison before and after connecting to a route.
Live Lookup
Current Network Egress
Run the lookup again after switching routes to confirm that browser traffic is using the expected egress.
Retrieving egress details through VPNRZ's same-origin API.
The GeoIP database's location estimate for the current address.
The network organization or service provider associated with the current public address.
A database classification signal for reference only.
Understanding the Results
What This Information Means
Review the egress address, location, and ISP together. A change in just one field does not necessarily mean the entire access path has switched as expected.
Egress Address
Your public IP is the address international websites see. If it changes after you connect to a route, browser traffic is leaving through a different egress. If it stays the same, first check the client connection status, then verify that your browser or system is using the correct proxy mode.
Location Estimate
The country or region is inferred from the address range by a GeoIP database. Because databases can lag behind real-world changes, use this result as a broad regional estimate rather than proof of an exact location. If a target service shows a different region, the two services may be using different data sources.
Internet Service Provider
The ISP field usually identifies the operator, data center, or network organization associated with the address range. It may change when you connect through an international route. An empty field means the endpoint returned no usable information; it does not mean the network has no service provider.
Proxy Detection Signal
This signal comes from address-database classification data. Data center addresses may be flagged, while residential addresses can receive different classifications based on past use. Treat the result only as a troubleshooting clue: it cannot confirm route health on its own or replace a real access test.
Local Checks
DNS Leak Check
An IP lookup confirms your web access egress; a DNS check examines where domain-resolution requests go. These are separate steps: a correct egress location does not guarantee that DNS requests follow the route settings.
This page does not use an external DNS testing service, so it will not show an unverified resolver list. Follow the steps below to check your client, system, and browser settings.
Confirm the Client's DNS Settings
Check whether the current connection uses the DNS handling method provided by the client. If rule mode is enabled, also confirm that the target domain follows the same route rules as web traffic.
Check the System Cache
After switching routes, your system may continue using existing DNS cache entries. Disconnect and reconnect to the network, clear the system DNS cache, then close and reopen the browser to reduce interference from stale results.
Check Browser-Specific Settings
Some browsers have their own Secure DNS option, which may bypass system or client settings. During troubleshooting, confirm that the browser's resolution method matches the current connection setup, then revisit the target website.
Continue Troubleshooting by Symptom
If the egress has changed but a website still serves content for the previous region, check the account region, browser cache, and site cookies. If no website can resolve domain names, investigate local DNS or connection settings next.
Open the Troubleshooting Guide