The Padlock Doesn't Mean the Site Is Safe
For years people were taught a simple rule: look for the padlock before you type anything in. It was good advice back when most of the web ran on plain HTTP. These days it's the opposite of helpful, because nearly every site has a padlock, including the scam ones.
So what does that little icon actually promise? Three things, and they're all about the connection, not the site.
Your traffic is encrypted. Anyone between you and the server, like the coffee shop Wi-Fi, your ISP, or someone snooping on the network, can't read what you send or receive. Your password, the page contents, the form you fill out are all scrambled in transit.
Nobody tampered with it on the way. HTTPS also protects integrity. Nobody in the middle can quietly inject ads, swap a download for something nasty, or change a bank account number on a page. If the data is modified in transit, the connection fails.
You're talking to the server for that domain name. The site presented a certificate, signed by a certificate authority your browser trusts, that says this server is allowed to speak for this exact domain. That stops someone from impersonating yourbank.com on the network.
That third point is where people get tripped up. The certificate proves you reached the real owner of whatever domain is in the address bar. It says nothing about who that owner is or whether they're honest. Certificates for basic domain validation are free and automatic now (which is a good thing overall), so a phishing site at yourbank-secure-login.com can get one in a minute. The padlock will show up, perfectly legitimate, for a site whose whole purpose is to steal your password.
Here's what HTTPS doesn't do:
- It doesn't tell you a business is real or trustworthy.
- It doesn't protect you from malware the site itself serves up.
- It doesn't stop the site from tracking you, selling your data or mishandling it once it arrives.
- It doesn't hide which site you visited. The domain name usually still leaks through DNS and the initial connection setup, even though the specific pages and content are hidden.
This mismatch between what people think the padlock means and what it actually means is a big reason some browsers have moved away from showing it as a "secure" badge at all, in favor of a more neutral icon. Encryption is just expected now. The thing to worry about is when it's missing, and browsers warn loudly about that.
What should you look at instead? The domain name itself. Read it, right to left from the first single slash. login.yourbank.com is your bank. yourbank.com.account-verify.net is not, because the actual domain there is account-verify.net. Lookalike letters and extra words are the oldest tricks around.
Honestly, though, eyeballing URLs is tiring and humans are bad at it. The better move is to let software check for you. A password manager won't autofill on a domain it doesn't recognize, and a passkey simply won't work on the wrong site. And for anything important, like your bank, go there through a bookmark or the app instead of a link someone sent you. That habit does more than any padlock ever did.

Comments