Inside the TLS handshake

What actually happens in the padlock moment, keys, certificates, and the handshake animated.

Before any encrypted data flows, the browser and server perform a handshake: they agree on how to encrypt, the server proves its identity with a certificate, and together they establish keys that only the two of them know.

The clever part is using public-key cryptography just long enough to exchange a shared secret, then switching to fast symmetric encryption for everything after. That handshake is the padlock in your address bar, and it happens in milliseconds on every HTTPS connection.

Remember this

  • The certificate proves you're talking to the real server
  • Public-key crypto bootstraps a shared secret; symmetric crypto does the heavy lifting
  • All of HTTPS rests on this few-milliseconds ritual

Got a different question? SeaThru generates a fresh video for any topic where systems talk or data structures move.

Ask your own question →

Keep learning