🔒 HTTPS Explained Like You're 5
Building AI systems and writing about how they actually work. Master of AI @ University of Technology Sydney. Previously B.Tech CS with focus on IoT. I believe the best way to learn is to explain. That's why I'm documenting tech concepts with simple analogies (@sreekarreddy.com). AWS Certified • Azure AI Certified • Neo4j Professional • Google Data Analytics When not coding: exploring Sydney, working on side projects, and teaching tech to anyone who'll listen.
A sealed envelope instead of postcard
Day 43 of 149
👉 Full deep-dive with code examples
Postcard vs Sealed Letter
HTTP (no S): Like a postcard
- Anyone who handles it can read it
- Your password could be visible to others along the way
HTTPS (with S): Like a sealed envelope
- Typically the sender and receiver can read the contents
- Carriers just see a sealed envelope
The S = Encrypted
HTTPS uses encryption (via TLS):
Your message: "hello"
↓ encrypted
Sent as: "xK9#mL@pQr!5vB2n..."
↓ decrypted by server
Server sees: "hello"
Anyone in between typically sees encrypted data.
How You Know
Look at the URL:
https://usually means your connection is encryptedhttp://means it isn't
Avoid entering passwords on HTTP sites.
What It Protects
- Passwords and login info (in transit)
- Credit card numbers (in transit)
- Personal messages (in transit)
- Any data you send between your browser and the site
Note: HTTPS protects data in transit. It doesn't make a malicious website trustworthy.
In One Sentence
HTTPS encrypts the connection between your browser and the website, protecting your data from eavesdroppers.
🔗 Enjoying these? Follow for daily ELI5 explanations!
Making complex tech concepts simple, one day at a time.