R1VPN · Network Check

Public IP Lookup

See which network route your browser request is using. After switching routes, check again to see whether the location matches your expectations.

Current Connection Details

Lookup via R1VPN

Retrieving connection details.

Public IP: Temporarily unavailable
Country / Region: Temporarily unavailable
Internet Service Provider (ISP): Temporarily unavailable
Proxy Detected: Temporarily unavailable

Results apply only to the route used when this browser accessed our lookup API. Other apps may use different routes. Fields with no response are shown as “Temporarily unavailable.”

What These Details Mean

Public IP and Location

The public IP is the address our API identifies when it receives a request. It is not your device’s address on the local network. With a proxy enabled, the result will usually show the selected route’s exit IP if this request went through it. With rule-based routing, requests to this site may still use your local network.

The country or region is based on an IP geolocation database, not your device’s physical location. Database updates may lag, and websites can identify locations differently. The location shown here does not guarantee that a particular AI tool or streaming platform will be available.

ISP and Proxy Detection

ISP refers to the network provider information returned by the API. If your traffic goes through an intermediary or data center, this may show the provider for the exit network rather than your local broadband provider.

Proxy detection classifies the exit IP based on the API’s data; it does not read your client’s proxy toggle. “No proxy detected” does not mean your request did not use a proxy, and “Proxy detected” does not mean the connection has a problem. If the API provides no clear result, this page won’t make its own guess.

DNS Leak Check

DNS translates domain names into network addresses. Routing web requests through a proxy does not necessarily route DNS lookups the same way. If lookups go to an unexpected resolver, the request may be visible to relevant parties on that network.

Check Your DNS Settings First

Check the DNS or domain resolution settings in your client and confirm that the configured DNS policy is in use. Don’t assume DNS is routed through the proxy just because the connection toggle is on.
Check your browser’s Secure DNS settings. Browsers may select a resolver independently, so consult your client’s documentation to confirm that its behavior matches your expectations.
After changing networks or routes, reconnect and review your settings. Caches in your operating system, browser, or apps may delay the effects of new settings.

How to Interpret Further Test Results

To verify DNS behavior, you need a test environment that can observe queries to a dedicated test domain. This page does not automatically contact external testing services. If you use another test tool, review its privacy policy first, then compare the resolver provider and location it reports with your expected configuration.

A difference between the resolver’s location and the exit IP’s location does not necessarily indicate a leak; it may reflect how the DNS service is deployed. Consider your client’s DNS policy and the actual request route together. For help troubleshooting, describe your client platform, connection mode, and the issue in a support ticket in the user panel. Don’t include your password or full subscription link.

Privacy Notice

We don’t log queries. Lookups run through our API; if it fails, we don’t fall back to a third-party public API. This page does not save results in your browser’s persistent storage. Your current IP is only sent to the clipboard if you click “Copy IP.”

Your public IP may reveal information about your network location. Before sharing a screenshot, consider obscuring any addresses or account details you don’t want to disclose. R1VPN keeps no logs. See our Privacy Policy for details on how information is handled.