How to read the result

The local Wi-Fi operator and your ISP are different observers: the Wi-Fi operator controls the nearby network, while the ISP carries that network's internet connection. A working VPN tunnel generally hides the destinations carried inside it from both, while they can still observe a connection to the VPN endpoint and traffic patterns. A DNS lookup sent outside the tunnel is an exception; an unencrypted lookup can reveal domain names along its path.

HTTPS protects page contents between your browser and the website. It does not by itself conceal every connection detail, and it does not hide information you submit or your account and browser identifiers from the website. A VPN provider routes tunneled traffic onward, so it becomes another party to consider. The result assumes ordinary web traffic and does not account for leaks, split tunneling, captive portals, malware, or network-specific monitoring.

“DNS through the VPN” describes the route to the resolver, not necessarily encryption between your device and that resolver. The resolver can receive the domain query. With encrypted DNS outside a VPN, the Wi-Fi operator and ISP generally cannot read the query itself, but can see a connection to the DNS service; the resolver still receives the query.

For your actual setup, compare public IP and DNS results with and without the VPN, review your app's split-tunneling settings, and consult the provider's documentation. A browser check is only a point-in-time observation.