Is public Wi-Fi still as dangerous as people say

Most major services now use HTTPS, which encrypts content between the browser and the website. That sharply reduces the old ease of reading pages or passwords merely because they crossed the same Wi-Fi network. Risk therefore depends on the protocol actually used, not on the word “public” alone.

Encryption protects the connection to a domain, but it cannot stop you visiting a fake site or voluntarily entering a secret into a phishing form. Browser warnings, the actual domain name and multi-factor authentication still matter.

An attacker can copy the venue’s network name or present a misleading captive portal. Automatic connections to remembered networks or accepting unusual certificate warnings increase exposure. Security guidance therefore still recommends checking the network and disabling unnecessary automatic joins.

An unpatched system, open file sharing or exposed services can make a shared network more dangerous. A fully updated phone with limited services has a different risk profile from an old laptop configured as if every network were trusted.

When administering systems, handling sensitive material or carrying out critical operations, a personal cellular connection or controlled corporate access may be preferable. On a hotspot, keep HTTPS, reject certificate warnings and share no more data than necessary.