First check where your current browser connection exits, then confirm whether your route is working as expected. This shows the exit point for this request only, not for every app on your device.
Temporarily unavailable
Switch routes and check again to see whether your public IP has changed.
Enable JavaScript to check your IP through our interface.
Location and proxy labels come from the interface’s identification data and may be outdated or missing. Fields that are not provided are not inferred or filled in.
Checking your exit IP, location, and app behavior separately is more useful than relying on a single proxy label.
Your public IP is the source address seen by our interface. When a network proxy is enabled, the address will usually change if this request passes through the selected route. The country or region is based on an IP address database; it is not your device’s precise location and may not match the city named in the route.
The ISP may identify the network operator or data center hosting the exit point, rather than your local broadband provider. A proxy detected result means the database assigned a relevant label. No proxy detected does not prove that your connection bypasses a proxy, and a missing label says nothing about the strength of your privacy protection.
An IP lookup checks only your exit point; it cannot confirm whether DNS requests follow the expected path. This page does not run an automatic DNS leak test.
Review your client’s DNS and routing settings to see whether the current mode is meant to use system DNS, client-side DNS, or the browser’s secure DNS. Results can vary by mode; a DNS provider located in your region does not, on its own, indicate a leak.
Check the DNS configuration in your system’s network settings, then review your browser’s secure DNS options. Browsers may choose a DNS provider independently, so a change to system settings may not affect the browser. Do not disable security settings you do not understand just to test your connection.
If your client supports DNS diagnostics or connection logs, use them locally to check whether test-domain lookups follow the expected path. If you use a DNS testing tool with dedicated detection features, review how it works and its privacy policy. The IP results on this page cannot replace this check.
If DNS requests do not follow the expected path, check for conflicts involving client DNS handling, routing rules, browser settings, or other network software. After making changes, reconnect and test again; do not treat an existing connection or cached result as evidence of the new configuration.
Queries are not logged. This page sends requests only to VPNRole’s same-origin GeoIP interface and does not fall back to a public third-party API. The copy action writes only the current IP to your clipboard; clipboard contents are never submitted.
If the interface is unavailable, the page displays “Temporarily unavailable” rather than a sample address or an old result. Your public IP may reveal your network location, so consider masking it before sharing a screenshot. You do not need to share subscription links or account credentials to troubleshoot a connection.