Skip to content
CryptoAcademy logo CryptoAcademy
Menu
Intermediate Cryptography

TLS & HTTPS

The protocol that encrypts and authenticates your connection to a website.

TLS & HTTPS at a glance
Symmetric encryption uses one shared key; asymmetric uses a public and a private key Symmetric — AES-GCM Same key encrypts and decrypts Plaintext pay 1 BTC Ciphertext a9f3…1c Shared key K secret, 256-bit Fast · problem: how to share the key safely? Asymmetric — RSA / ECDSA A public key and its private key are a pair Public key shared with everyone Private key never leaves the owner mathematically linked (trapdoor) Anyone encrypts → only owner decrypts Slower · solves key distribution and signatures How the web combines both (TLS) 1. Your browser fetches the site's public key inside a certificate. 2. Both sides derive a temporary symmetric session key (key exchange). 3. Everything after that is encrypted fast with AES-GCM — signatures only prove who you are.

In simple terms

The padlock means your traffic is encrypted and the server proved it owns the domain — nobody on the network can read or tamper with the pages you load.

Analogy

An armoured courier who also checks the sender's ID badge against a government registry before handing anything over.

Going deeper

TLS 1.3 handshakes combine an X.509 certificate chain check (asymmetric, for identity) with ephemeral X25519 key exchange (forward secrecy) and then switch to fast symmetric AEAD for the data. Fewer round trips than TLS 1.2 and no legacy cipher suites.

Common mistake

A valid certificate only proves the connection is encrypted to the right domain — phishing sites have padlocks too.

Share this page

Send this link to a friend, or scan the QR code to open it on your phone.