Option A
HTTP
The original, unencrypted web protocol.
Best for: Low-stakes, read-only browsing where no personal data is entered or transmitted.
Option B
HTTPS
The secure, encrypted standard for the modern web.
Best for: Any site where you log in, shop, bank, or share personal information.
What HTTP and HTTPS Actually Mean
HTTP stands for HyperText Transfer Protocol. It is the set of rules that governs how data — text, images, links — travels between your browser and a website's server. Think of it as the postal system of the web: it moves information from point A to point B.
HTTPS adds one critical letter: the S stands for Secure. Under HTTPS, the same data transfer happens, but the information is first encrypted using a technology called TLS (Transport Layer Security). Encryption scrambles the data into unreadable code before it leaves your device. Only the intended server holds the key to unscramble it.
When a website uses HTTPS, your browser verifies a digital document called an SSL/TLS certificate issued to that site. If everything checks out, you see the padlock icon in the address bar. This handshake happens automatically and takes milliseconds — you never have to do anything manually.
| Criterion | HTTP | HTTPS |
|---|---|---|
| Encryption | None — plain text | TLS encryption in transit |
| Padlock in browser | No padlock shown | Padlock displayed |
| Safe for passwords/payments | No | Yes (connection level) |
| Vulnerable to eavesdropping | Yes, on shared networks | Significantly harder to intercept |
| Certificate required | No | Yes — SSL/TLS certificate |
| Common use today | Declining; legacy sites | Standard across modern web |
Why the Difference Matters in Real Life
Imagine sending a postcard versus a sealed, tamper-evident envelope. HTTP is the postcard — anyone handling it along the route can read what is written. HTTPS is the sealed envelope: the contents are protected in transit.
On an HTTP connection, a skilled eavesdropper on the same network — especially a public Wi-Fi hotspot at a café or airport — could potentially intercept the data flowing between you and a site. That might include usernames, passwords, or form data. This type of attack is sometimes called a man-in-the-middle attack. HTTPS makes that kind of interception extremely difficult because the data is encrypted.
For everyday browsing this matters most when you are:
- Logging into an email, banking, or social media account
- Entering a credit or debit card number
- Submitting a form with your address, date of birth, or Social Security number
- Creating a new account with a password
For tips on staying safe when browsing on shared networks, see our guide to protecting your data on shared devices.
95%+
Of web traffic now encrypted
Google's transparency report has consistently shown that the vast majority of pages loaded in Chrome use HTTPS.
1 in 3
Phishing sites use HTTPS
The Anti-Phishing Working Group has noted that a significant share of phishing pages use HTTPS, underscoring that the padlock alone is not a trust signal.
What the Padlock Does — and Does Not — Tell You
The padlock means the connection between your browser and the server is encrypted. That is a meaningful protection. But it does not mean the site itself is honest or legitimate.
Phishing sites — fake pages designed to steal your information — can and do obtain HTTPS certificates. The padlock tells you that data in transit is scrambled; it says nothing about what the site does with that data once it receives it.
So treat HTTPS as a necessary condition, not a sufficient one. Before entering sensitive information, also check:
- The domain name looks correct (watch for subtle misspellings like
paypa1.cominstead ofpaypal.com) - You arrived via a trusted link, not an unsolicited email
- The site has a legitimate privacy policy and contact information
Our quick safety checklist for everyday browsing walks through additional red flags to watch for before you click or submit anything.
It is also worth dispelling a related myth: private or incognito mode does not encrypt your connection. For more on common misconceptions like this, visit our roundup of internet myths many Americans still believe.
What Happens When a Certificate Expires?
Every HTTPS certificate has an expiration date. When one lapses, your browser will display a warning — typically a red alert page saying the connection is "not private" or "not secure." This does not necessarily mean the site is malicious; it may simply mean the site owner forgot to renew. Still, it is wise to hold off entering sensitive information until the warning is gone and the connection is secured again.
Building Stronger Online Habits Around HTTPS
Understanding HTTP vs. HTTPS is a strong foundation, but online privacy involves more than one layer. Combining secure connections with other habits dramatically reduces your risk.
A few practical steps:
- Check the address bar before entering any personal data. If you see "Not Secure" or a broken padlock, pause.
- Use strong, unique passwords for every account so that even if one site is compromised, others stay protected.
- Enable two-factor authentication wherever available — it adds a second barrier even if a password is exposed. See our beginner's guide to two-factor authentication to get started.
- Be cautious on public Wi-Fi even with HTTPS sites, since other risks (like fake hotspots) still exist.
For a broader look at how to protect your personal information online, our complete guide to online privacy covers tracking, data collection, and practical defenses in depth.
The content on this site is for informational purposes only and is not a substitute for professional advice. Always consult a qualified professional for guidance specific to your situation.

