See the public IP address used by your browser’s current request. After switching routes, run the lookup again and compare the result with your client’s connection status.
This page will check your public IP through a VPNRB endpoint after it loads.
The endpoint sees the public IP address your browser uses to access this site, not your device’s local network address. Split-tunneling rules may connect this site directly while routing a target app through a proxy, so this result may not reflect how every app connects. After switching routes, run the lookup again and check your client’s rules.
The country, region, and network provider are based on the endpoint’s IP geolocation data. Database updates may lag, and the ISP may be listed as a data center or upstream network rather than the selected route. Geolocation cannot confirm your device’s actual location or the region associated with a streaming account.
“Proxy detected” means the endpoint returned a proxy flag; it doesn’t mean the connection has failed. “No proxy detected” doesn’t prove the connection is direct. If the endpoint can’t make a clear determination, this page shows “Temporarily unavailable” rather than treating an unknown result as a negative.
Once the public IP matches your expectations, check access in the target app as well. Regional access may also depend on your account, payment region, device settings, and the platform’s rules. An IP lookup alone can’t confirm that streaming is available or verify that all traffic uses the same route.
An IP lookup and a DNS check are separate tests. This page’s endpoint doesn’t return DNS resolver details, so it won’t show “test passed” or automatically determine whether a leak has occurred.
In your client, check the actual DNS, system proxy, and tunnel-mode settings. With system proxy enabled alone, some apps may still use the system to resolve domain names. Behavior varies by client and app, so don’t rely on the connection toggle alone.
Check whether your browser has a separately configured encrypted DNS service. Browser settings may operate independently of system DNS. Note the original configuration before making changes, and follow your client’s instructions to avoid changing several settings at once and making the cause harder to identify.
Check the DNS configuration in your system’s network settings, then review your client’s diagnostic logs to see where domain lookup requests are routed. The resolver address shown by your system is a configuration clue; if your client intercepts requests, the actual route may differ.
If you use a diagnostic tool that displays resolver details, check whether its DNS requests follow the expected route. A resolver and public IP in different regions are not, by themselves, evidence of a leak. If you need help, submit a redacted configuration and a description of the error through the user panel.
This page checks only the public IP used to access this site. DNS request routes and how other apps are routed must be checked separately.
VPNRB doesn’t log lookups. This page sends a request only to VPNRB’s public IP lookup endpoint. Results stay on the current page and aren’t saved to browser storage. An IP address is written to your clipboard only if you click “Copy IP.”
If the endpoint can’t be reached, returns an unexpected response, or omits a field, that field shows “Temporarily unavailable.” This page doesn’t fall back to third-party public APIs. Check your connection, then click “Check Again.” A failed lookup doesn’t, by itself, mean your proxy is down or that a DNS leak has occurred.
Before sharing a screenshot or submitting a support ticket, redact subscription URLs, account credentials, and any IP addresses you don’t want to share. See the Privacy Policy for details.