View the IP, country or region, ISP, and proxy status exposed by your current request. Checking before and after connecting to a network acceleration service can help determine whether your outbound route has changed.
CURRENT NETWORK
RESULT GUIDE
A single lookup shows what is publicly visible after your current request leaves the network. It can help confirm a change in outbound routing, but it does not by itself represent connection quality, privacy, or access to a specific service.
Your public IP is the network address that websites and online services can usually see. Refresh this page before and after connecting to VPNFB. If the address or location changes, your browser request is using a different outbound route.
Location data comes from GeoIP databases and reflects the registered or inferred location of an address, not the device's precise position. Databases update at different rates, so the result may differ from the physical location of the hosting facility.
The ISP field identifies the network operator or data center associated with the public address. Home broadband, mobile networks, and server routes may display different types of names; this can provide supporting information when identifying the outbound route.
Proxy detection is an assessment based on network attributes and should be treated as a reference only. “Not detected” does not prove that all traffic uses the same route, nor does it replace DNS or per-application checks.
DNS CHECK
DNS translates domain names into network addresses. A changed public IP does not necessarily mean that every DNS request follows the same connection path. This page reads GeoIP data only and does not present an ordinary IP geolocation result as a DNS check.
For a self-check, review the client connection status, the resolver currently used by the system, and whether the target app uses its own DNS. Compare the resolution paths before and after connecting instead of relying only on a location name.
Disconnect from the acceleration service, refresh this page, and note the public IP, location, and ISP. Then check the current DNS resolver in your operating system's network settings or the client's diagnostics page.
Reconnect, run the check again, and review the DNS information shown by the system or client. Confirm that the public address has changed and check whether the resolver has switched to the expected path.
If only certain apps need acceleration, verify the browser and target app separately. Different apps may use their own network and DNS settings, so one browser result cannot represent all traffic on the device.
If the resolution path still points to the original network, disconnect and reconnect, then check the system proxy, client DNS, and routing rules. Repeat the same process after making changes instead of relying only on the connection icon.
PRIVACY
We do not record results from this page. Your browser sends requests only to our same-origin GeoIP API, and the page does not fall back to a third-party public lookup service if the API fails.
To perform the check, the API must read the network address included with the current request and return location, ISP, and proxy-status fields. The page does not ask for account details or save lookup results in browser storage.