Public Wi-Fi Safety: What Can Go Wrong and the Habits That Fix It
HTTPS made public Wi-Fi safer than it used to be, but fake hotspots, fake login pages, and automatic connections remain real risks. A short checklist handles them.
Public Wi-Fi is safer than it used to be, but it is not risk-free. Most websites and apps now encrypt their traffic with HTTPS, so another person on the same café or airport network usually cannot read your passwords or messages. Google has said that around 95 to 99 percent of Chrome page loads use HTTPS. The risks that remain are narrower but real: fake networks set up to look like the real one, fake sign-in pages, the few sites that still do not use HTTPS, and your device connecting to networks automatically without asking you.
What HTTPS protects, and what it does not
When you see the padlock, the content of your connection to that site is encrypted, and your browser checks the site's certificate. That is genuine protection. What HTTPS does not do is prove the site is trustworthy: a lookalike site run by a scammer can use HTTPS too. It also does not hide which sites you visit from the network operator, and it does nothing for apps or background services that still send data unencrypted. Treat HTTPS as a seatbelt — essential, but not a reason to stop paying attention.
The fake hotspot is the main trap
An attacker can set up a network named almost exactly like the café's real one — "CoffeeShop_WiFi" next to "CoffeeShop WiFi" — and wait for people to join the wrong one. Once you are connected, they can present a fake login page asking for an email address, a social login, or even card details. The defense is boring and effective: ask staff for the exact network name before you connect. Two networks with nearly identical names is a red flag. And a legitimate network will never ask you to install software or enter card details just to get online. If a login page asks for either, disconnect.
Turn on a VPN on networks you do not control
A VPN encrypts everything leaving your device — browser, apps, background services — and sends it through a server you chose. On a public network, that closes the main remaining gap: even if someone is listening, they see encrypted traffic to one server and nothing else. Pick a VPN with a kill switch, which cuts your internet the moment the VPN connection drops, so nothing leaks in the open. Turn the VPN on before you open anything, not after you have already signed in to three accounts. One honest caveat: a VPN moves your trust from the network operator to the VPN company, so this advice assumes you use a provider you have already vetted.
Settings to change before your next trip
Turn off auto-join. Your phone remembers every network it has joined and reconnects automatically — including to a network with a familiar name run by a stranger. On iPhone, go to Settings, then Wi-Fi, tap the information icon next to a network, and turn off Auto-Join. On Android, the equivalent lives in the network's settings. Use "Forget This Network" for places you will not return to.
Turn off file sharing and network discovery. Sharing features designed for a trusted home network can create openings on a public one. On Windows, mark public networks as Public so sharing is limited. On a Mac, check the sharing settings before you connect.
Turn on HTTPS-only browsing. Chrome offers "Always use secure connections" and Firefox offers HTTPS-Only Mode. Both make the browser warn you — or refuse — when a site tries to load over plain HTTP.
Keep your firewall on. Your operating system's firewall is an extra barrier between your device and other devices on the network. It should be on by default; check that it is before you travel.
Save the sensitive stuff for a trusted network
Skip online banking, shopping checkouts, and work accounts while on public Wi-Fi. These actions expose high-value information that attackers target on unsecured networks. If you must handle something sensitive away from home, use your phone's mobile data or your own hotspot instead — the cellular connection is a network you control, and it avoids the shared-network problem entirely. For everything else, two-factor authentication is your safety net: even if a password is intercepted, the attacker still cannot get in without the second factor.
A quick checklist before you connect
Confirm the exact network name with staff. Turn on your VPN before opening anything. Check for HTTPS and the correct domain on login pages. Do not install anything a Wi-Fi login page asks you to install. Turn off file sharing and network discovery. Forget the network when you leave. Public Wi-Fi is not a minefield — it is a shared space with a few known risks and a short list of habits that handle them. Set the settings once, and the checklist becomes automatic.