A postcard can be read by every handler; a sealed envelope can't. HTTPS puts your web traffic in a sealed, encrypted envelope so the WiFi, the cafe, and eavesdroppers can't read your password on the way.
Anyone on the path can read plain packets
A packet passes through many routers you do not control. Sent in the clear, its contents — passwords, messages, card numbers — could be read or altered along the way. Encryption scrambles the contents so that only the intended recipient, holding the right key, can unscramble them.
Each letter slides 3 places down the alphabet. Only 26 keys exist — that's why Caesar is easy to crack.
A toy cipher shifts each letter by a secret key. Real encryption uses the same idea — a shared secret — but with math no eavesdropper can undo by guessing.
When you see https and a padlock, your connection to the site is encrypted with TLS. Eavesdroppers see only scrambled bytes, and your browser verifies it is really talking to the right server, not an imposter.
- Use the Caesar cipher simulation to encode a short message with a shift you keep secret.
- Hand the scrambled text to a partner (or your future self) and challenge them to crack it.
- Because there are only 26 shifts, they can try them all. About how many guesses until it breaks?
- Explain why real encryption needs an astronomically larger key space than 26.
What you should see: You saw why a small key space is trivially breakable, motivating the enormous keys that make HTTPS secure.