RN Relay · IP Check

IP Address Check

See the network route used by this browser request. After connecting to or switching routes, run the check again to confirm the IP location meets the target service’s access requirements.

Current IP Details

Waiting for lookup
Public IP
Waiting for lookup
Country / Region
Waiting for lookup
Internet Service Provider / ISP
Waiting for lookup
Proxy Detected
Waiting for lookup

This page checks your current public IP through VPNRN’s API after it loads.

Understanding the Results

The results reflect the route used to reach this page’s API. Other apps may use different routes.

Public IP and Location

Your public IP is the address the VPNRN API sees as the source of your request—not your device’s address on a local network. Country and region are based on IP geolocation data, which may not be up to date and can’t pinpoint your device’s actual location.

Run the check again after switching routes to see whether your IP and location have changed. With split tunneling, this page, AI tools, and streaming sites may use different routes. Verify the result with the target service.

ISP and Proxy Detection

The ISP field identifies the provider associated with your public IP. It may show a carrier, data center, or cloud network, and may differ from the name of the network you’re currently connected to.

Proxy detection depends on the data returned by the API. “Not detected” doesn’t mean you aren’t using a proxy, and “Proxy detected” doesn’t mean your connection has a problem. If the API can’t provide a clear result, this page will say “Temporarily unavailable” rather than guessing from the ISP name.

DNS · Manual Checks

Check for DNS Leaks

DNS translates domain names into IP addresses. If you expect DNS queries to use your selected route but they’re handled by an unexpected local resolver, check how DNS traffic is routed.

  1. Check Your Client’s DNS Settings

    Open your client’s network or DNS settings and make sure the DNS mode matches your connection setup. If you use rule-based routing, check that DNS queries follow the relevant rules too. If you’re unsure what a setting means, consult the client’s documentation.

  2. Check System and Browser Settings

    Review the DNS settings for your current network connection, then check your browser’s Secure DNS settings. A browser may choose its own DNS resolver. Different system and browser settings don’t automatically mean there’s a leak; compare them with the route you expect.

  3. Verify Against DNS Logs

    If your client provides DNS or connection logs, check how it handled the relevant domain when you opened the target website. System network tools typically show only the system’s DNS route, not every case where a browser uses its own resolver or a client forwards queries internally.

After changing settings, reconnect and visit the target service again. For further troubleshooting, see the Help Center, or sign in to the dashboard and submit a support ticket. Include your device platform, connection method, and the issue you’re seeing. Never include your full subscription link.

Query Privacy and Limitations

VPNRN doesn’t log queries. Checks run through the VPNRN API and don’t fall back to a third-party public lookup service if a request fails. The page doesn’t save lookup results in your browser’s local storage.

The copy function writes your public IP to the clipboard only when you click it. Check for network addresses in screenshots before sharing them; troubleshooting usually only requires your IP location and the error message. See the Privacy Policy for details on how data is handled.