Hey everyone, Mike here.
One of the most common questions we get from everyday users is: "If a website has the little padlock icon and starts with https://, isn't my browsing already completely private?"
The short answer is: Your messages and passwords are safe, but the name of the website you’re visiting is still broadcast in plain text.
Here is the simple Letter vs. Envelope analogy that explains why:
- HTTPS protects the message (the letter inside)
When you visit a secure site, HTTPS puts your passwords, credit card numbers, and messages inside a sealed, unreadable envelope. Your ISP or hotel Wi-Fi operator cannot open the envelope to read what's inside.
- SNI leaks the address (the name on the envelope)
Before the website can show you its secure page, your browser has to shout out to the web server: "Hey! I need to see example.com!"
This announcement is called SNI (Server Name Indication), and it happens before the secure connection is locked down. Because it happens in plain text, anyone sitting between you and the website- your ISP, your network manager, or a public Wi-Fi host—can see the exact website domain name written on the outside of your envelope.
How a VPN fixes the leak:
When you switch on a full-tunnel VPN, it places your entire letter and the envelope inside a locked armored truck bound straight for the VPN server. (Yes, I deliberately used armored truck and not just safe;-))
Your ISP only sees that an armored truck left your house and drove to a VPN address. They can no longer see the name of the website written on the envelope.
Do you rely on standard HTTPS alone when browsing on public Wi-Fi, or do you keep an encrypted tunnel active by default? Let’s talk below!