Is public Wi-Fi safe? The real risks at cafés, airports and hotels
HTTPS has made public networks safer than they used to be, but not safe. Here is what can still go wrong on shared Wi-Fi, and what actually helps.
Free Wi-Fi in a café, airport or hotel is convenient, and most of the time nothing bad happens. But a public network is different from your home network in one important way: you share it with strangers, and you did not set it up. That changes what is worth worrying about.
What can go wrong on public Wi-Fi
- Fake hotspots. Anyone can create a network called “Airport Free WiFi”. If you connect to the impostor, all of your traffic passes through their equipment.
- Snooping on unprotected traffic. Anything sent without encryption can be read by someone else on the same network. Many websites are encrypted today, but not every app or connection is.
- Metadata. Even when the content is encrypted, the network can see which sites you connect to and when, from DNS lookups and connection details.
- Tampered pages and login portals. A hostile network can serve a fake sign-in page, or redirect you somewhere you did not intend to go.
- Other devices on the network. Without client isolation, devices on the same Wi-Fi can probe each other for open services.
What HTTPS already does for you
It would be wrong to say that public Wi-Fi exposes everything. When a site uses HTTPS, the content of your page views, your passwords and your form entries are encrypted between your browser and the site, and the café network cannot read them. That is a big improvement from ten years ago.
What HTTPS does not hide is where you are going. The network still sees the names of the sites you visit, and it can still interfere with connections that are not protected, including some app traffic.
What an encrypted connection adds
- All traffic between your device and Kite’s server is encrypted, including traffic from apps that do not use HTTPS themselves.
- The Wi-Fi owner and other people on the network cannot see which sites you visit, because the destination is inside the tunnel.
- Your real IP address is replaced by the server’s for the sites you reach.
- A fake hotspot can still see that you are connected to Kite, but not what you are doing through it.
This is the case for using Kite on shared Wi-Fi: it does not make a bad network good, but it limits what that network can learn from you.
Habits that matter just as much
- Confirm the network name with the staff, rather than picking the one that looks right.
- Turn off auto-join for open networks, so your phone does not connect to anything that shares a familiar name.
- Set the network to “public” on your laptop, and turn off file sharing and AirDrop-style sharing for everyone.
- Use two-factor authentication on important accounts, so a stolen password alone is not enough.
- Keep your device up to date. Most attacks on public networks rely on known, already-fixed weaknesses.
- Be suspicious of certificate warnings. If your browser warns that a site’s certificate is wrong, stop. Do not click through on a public network.
Daniel Brooks
Privacy & security writer
Daniel writes about online privacy, network security and how Kite works under the hood.