$ qavpn inspect --exit
Checking- IP Current public IP
- Loading
- GEO Location
- Loading
- ISP Internet service provider
- Loading
- PRX Proxy detected
- Loading
Reading public network details through QaVPN’s same-origin API.
NETWORK / EXIT REVIEW
Check the public address, location, and ISP currently visible to your browser, then use a DNS self-check to confirm that the connection path matches your expectations.
$ qavpn inspect --exit
CheckingReading public network details through QaVPN’s same-origin API.
RESULT INTERPRETATION
The results show the network identity presented externally when your browser made this request. They are useful for a basic check after switching routes.
CHECK / ADDRESS
This is the public address presented by the current web request. After connecting to a QaVPN route, run the check again and compare it with the previous result. If the address has not changed, first confirm the client connection, then close pages that may be reusing an old connection and check again.
CHECK / LOCATION
Location data comes from an IP address database and indicates the approximate region associated with the public address. It is not precise geolocation; database updates, network routing, and address registration details can all affect the result.
CHECK / PROVIDER
The ISP field identifies the network organization associated with the current public address. It may show a carrier, data center, or registered autonomous system name, which may not exactly match the region name shown when you selected a route.
CHECK / PROXY
The result is based on network attributes available to the API and is provided for reference only. Address databases and detection rules vary between websites, so “not detected” does not mean every service will reach the same conclusion.
DNS REVIEW
This page can display public network details, but it cannot fully determine the DNS resolution path used by your system. Use the steps below for a manual check.
Before connecting to an accelerated route, record your public IP, location, and current network environment. Keep this record for local comparison; there is no need to submit it to QaVPN.
After the route is connected, close pages that are still using an old network session. If needed, restart your browser or clear the system DNS cache before comparing the results.
Use your operating system’s built-in network diagnostics to review the current DNS configuration and confirm that requests are not still pointing to an unexpected local network. If your browser uses its own encrypted DNS, check the browser settings as well.
If your public address has changed but the system’s DNS path is still the same as before connecting, disconnect and reconnect the route, then review the client’s DNS takeover settings. Run the full comparison again after making changes.