NETWORK NOTE / Public IP Details

IP Check and DNS Self-Test

This page reads the network information currently visible to the internet. Results come from FvVPN’s same-origin GeoIP API and help confirm your public location, ISP and proxy detection status.

Same-origin lookup No third-party public API Results are not logged

RESULT / GEOIP

Current Public IP Details

Checking
Public IP
Checking
Country or region
Checking
ISP
Checking
Proxy detected
Checking

NOTE / INTERPRETATION

What this information means

Public IP

Your public IP is the network address visible to the websites you visit. Check it before and after connecting to a route to confirm whether browser traffic has switched to the expected exit point. If the connection appears normal but the public IP has not changed, check your system proxy, per-app rules and the browser’s own network settings.

Country or region

Location data comes from an IP address database and does not represent the device’s actual location. It usually indicates the region where the address range is registered or used. Databases can lag behind real-world changes, so city-level details may differ from the route’s data center; country or region data is more useful for confirming the exit direction.

ISP

The ISP field identifies the network organization associated with the public address. Different routes may show a data center, backbone network or local carrier. Use this field as a routing clue, not as a standalone measure of speed, stability or streaming availability.

Proxy detection status

This result only reports the detection field supplied by the GeoIP API. Websites use different databases and detection rules, so “Not detected” here does not mean every destination website will reach the same conclusion. If the API does not provide this field, the page will clearly show “Temporarily unavailable.”

CHECK / DNS

DNS Leak Self-Test

DNS translates domain names into network addresses. A changed public IP does not necessarily mean DNS requests are using the same route. If DNS is still handled directly by the original network, destinations may see a resolution source that does not match the public IP region.

  1. Record a baseline before connecting.

    Temporarily disconnect from the accelerated route and use a trusted DNS test page to record the resolver and region. The baseline is for comparison only; do not treat a single result as proof of a problem.

  2. Run another test after connecting to the target route.

    Open the test page again to avoid relying on an old page cache. Compare the public IP, DNS resolver and region with the direction of the selected route.

  3. Troubleshoot inconsistencies step by step.

    First check the client’s DNS settings, then check whether the browser has its own Secure DNS enabled, and finally check whether the system or local network has fixed another resolver address. Reconnect and test again after making changes.

PRIVACY / QUERY

Query Privacy Details

FvVPN does not log the results of queries made on this page. Your browser requests current public IP details only from FvVPN’s same-origin GeoIP API; failed requests are not forwarded to a third-party public lookup service. Copying is performed locally in your browser, and copied content is never sent to the server.

First Month Free