See which network route your browser is using for this request. After connecting to a route, run the lookup again to compare your egress IP.
Lookup Results
Current Egress
Checked via VPNRS
IP Address
Temporarily unavailable
Country / Region
Temporarily unavailable
ISP / Network Provider
Temporarily unavailable
Proxy Detected
Temporarily unavailable
The lookup runs automatically when JavaScript is enabled.
Understanding the Results
What These Details Mean
Egress IP and Location
The IP address is the request source seen by VPNRS’s lookup endpoint, not your device’s local network address. When using a proxy, it may be the route’s exit IP. If your browser routes traffic according to rules, this page may still use your original network.
The country or region is based on IP database records. It may differ from the actual data center location or be out of date. It can’t identify a person’s home address, and other websites may determine your location differently.
ISP and Proxy Detection
ISP usually refers to the network provider or hosting network associated with the egress IP. It may not be the broadband provider currently serving your device.
The proxy field reports only what the lookup endpoint detects. No proxy detected doesn’t mean your connection isn’t using one. “Temporarily unavailable” means the endpoint couldn’t provide a classification; it doesn’t indicate your connection status.
DNS Resolution Path
DNS Leak Checks
An IP lookup and a DNS leak test are different. This page doesn’t run an active DNS leak test, and an egress IP alone can’t show whether DNS is leaking.
Set expectations, then check the actual path
Check your client’s DNS settings. See whether DNS settings provided by the client are enabled and which domains are resolved by your local network in rule-based mode. With split routing, some domains using local DNS may be expected.
Check your browser’s Secure DNS settings. The browser’s built-in encrypted DNS may use a separate path. Compare the browser and client settings to confirm that DNS requests are handled as expected; don’t rely on a setting’s name alone.
Review DNS query logs. Check the DNS server and request path in diagnostic logs provided by your system or client. If you use a dedicated DNS testing tool, review its privacy information and compare results before and after connecting.
Review the domain and routing rules together. If domains expected to use the route are still resolved over your local network, check DNS interception, routing rules and app settings. A DNS server’s location alone isn’t enough to confirm a leak.
Keep your browser and network environment as consistent as possible before and after testing. After changing settings, reconnect and repeat the same steps to compare results. This helps avoid mistaking browser cache or rule differences for a route issue.
VPNRS doesn’t log lookups. Requests are sent only to the VPNRS endpoint, and this page doesn’t save results to local storage. The copy button copies only the IP address shown.
The lookup endpoint needs to receive the egress IP address of your current request to return a result. If the network or endpoint is unavailable, this page shows “Temporarily unavailable.” It won’t switch to a public third-party endpoint or generate a substitute result.