Check the IP address, country or region, and ISP visible to external websites, along with the proxy signals returned by our API. This page contacts only same-origin 35VPN APIs and does not use third-party public lookup services.
The result card shows the network information presented externally when your browser accesses our APIs. It can help confirm whether your public IP has changed, but it is not a standalone measure of connection quality or privacy.
Your public IP is the network address that target websites can typically see. Run the test again after switching routes to confirm whether the public address changed with the connection. If it remains the same, check your client connection and traffic-routing rules.
The location is identified from the IP range in an IP database and represents the region where that address is generally registered or assigned. Database updates may take time, so use this information to verify route direction rather than treating it as your device’s actual location.
The ISP field identifies the operator, data center, or network organization associated with the public address. Different routes may show different names; the name itself does not indicate speed. Actual performance depends on your local network, route path, and current destination.
This result reports only the identification signal returned by our API. “Not detected” does not mean every website will reach the same conclusion; services may use different data sources and detection rules. Review the result alongside the public address and actual connection status.
DNS translates website names into network addresses. If your public IP changes while DNS requests are still handled by the original network environment, the route used for traffic and the DNS resolution path may no longer match.
The GeoIP API on this page can read only the public network information seen when your browser accesses 35VPN. It cannot spoof or infer your DNS resolvers. The DNS section therefore uses a verifiable manual process instead of displaying an unsupported detection result.
Disconnect your acceleration connection, refresh this page, and note the public IP, region, and ISP as a reference for your current network environment.
Confirm that the client shows a connected status, then select “Run Test Again.” The public IP and region should reflect the selected route. If they do not change, check whether the rule mode is sending browser traffic through the original network.
Check whether the client manages DNS, and whether your browser has its own Secure DNS setting enabled. A resolver configured separately in the browser may bypass the client’s settings, so keep them aligned for your use case.
Reconnect the route first, then disable potentially conflicting browser network extensions and review the system DNS settings. Change one setting at a time to identify which setting caused the resolution paths to differ.