NETWORK DIAGNOSTICS

Public IP & Network Check

View the IP, location, and ISP details shown to the outside world by your current connection. Results come from VPNVR's same-origin check API, with no third-party public lookup service.

  • Public IP
  • Location & ISP
  • Proxy status
  • DNS check
CURRENT ROUTE

Current public IP result

Ready to check
Public IP
Temporarily unavailable
Country or region
Temporarily unavailable
ISP
Temporarily unavailable
Proxy detected
Temporarily unavailable

RESULT READING

What this network information means

The results describe the connection details visible to external services when requests leave your network from the current browser. Use them to confirm whether your route has changed and whether the network exit matches your expectations.

IP

Public IP

Websites usually see your public IP, not the address assigned to your device on its local network. Connect to a VPNVR route and check again. If the public IP differs from before, your browser requests are leaving through a new network exit.

GEO

Country or region

Location data comes from network ownership records in an IP address database and can help verify the approximate location of your current exit. It does not indicate your device's exact location; a data center's registered address may differ from the city where the network exit is actually located.

ISP

Internet service provider

The ISP field identifies the carrier, data center, or network organization associated with the exit address. It may change with the exit network after switching routes, so compare it with the location data to assess the current connection path.

ROUTE

Proxy detection

Proxy status is a reference result generated by the API from characteristics of the current exit. A result showing no proxy does not mean the route has no intermediary; detecting a proxy does not by itself indicate a connection problem. Consider the public IP and actual browsing behavior together.

DNS CHECK

DNS leak check

DNS converts domain names into network addresses. Even when your public IP changes, DNS requests may still travel along a different network path. The key check is whether the DNS resolution services before and after connecting belong to the expected network for the current route.

This page does not connect to external DNS test APIs or forward queries to third parties. Follow the steps on the right for a basic check. If the results look unusual, reconnect first, then review the DNS settings in your system and browser.

  1. Record the pre-connection results

    Disconnect the acceleration route first, then record your public IP, location, and ISP. Use these details to compare with the results after connecting.

  2. Connect to the target route

    Connect in your client, return to this page, and select “Check again” to confirm that the public connection details have changed.

  3. Check DNS ownership

    Use the network diagnostics built into your operating system or browser to view the DNS servers and their network ownership. The resolution path should match your current connection policy.

  4. Address inconsistent results

    Reconnect and disable any browser security DNS settings that may override system settings. If the results still differ, submit a support ticket from the user panel with details of what you observed.

Start Free