Airport lounges, hotel networks, coffee shops — convenient but dangerous. Here's what attackers can realistically do on an open network, and how to stay safe.
Marcus T.
Software Engineer · April 5, 2026
With HTTPS everywhere and TLS 1.3 being the norm, the old 'never use public Wi-Fi' advice is somewhat outdated — but not entirely. The threat model has shifted, but the risks haven't gone away. They've just gotten more sophisticated.
Here is what a motivated attacker can realistically do on the same network as you:
Even on HTTPS connections, your DNS queries are often sent in plaintext. This means anyone on the network — or your ISP — can see which domains you're visiting, even if they can't see the content. A VPN with DNS leak protection routes your queries through its encrypted tunnel, making them invisible to network observers.
You can test for DNS leaks at dnsleaktest.com. Run it with and without CueVPN connected to see the difference.
Regardless of whether you use a VPN, follow these practices on public Wi-Fi:
A VPN doesn't just encrypt your traffic — it also moves your DNS resolution to a trusted server, masks your traffic patterns from local observers, and makes evil twin attacks ineffective since the attacker sees only encrypted gibberish. For frequent travellers, it's the single highest-impact security tool available.

Free plan, no credit card. Available on iPhone and Android.