AlgoPlusAlgoPlus
AlgoPlus//web / https
Read the theory

How HTTPS Keeps a Page Safe

What the padlock means: plain HTTP travels in the open, so a TLS handshake proves the server's identity and locks the channel with a shared key.

Step
Channel
Open
Legend
Handshake (setting up)
Encrypted / safe
Readable by anyone
AI Tutor Workspace
In a nutshell
Plain HTTP sends everything as readable text, so anyone between you and the server can read or change it. HTTPS fixes this with the TLS handshake: the server presents a certificate, signed by a Certificate Authority, that proves it really is that domain, and the browser verifies the certificate chain. The two sides then agree on a shared session key over the open wire without ever sending it, and from then on every message is encrypted with that key. An eavesdropper sees only ciphertext — that locked channel is the padlock.
Ready
Press play to begin the cinematic walkthrough.
Plain HTTP is a postcard — anyone on the path reads it. HTTPS first checks the server's ID card (its certificate), then seals the rest of the conversation in an envelope only the two of you can open.
Key terms
Go deeper in the lesson
Read the full theory, intuition & complexity for How HTTPS Keeps a Page Safe.