About this interactive
From the lesson:
- **A key pair:** what one key encrypts, only the other can decrypt.
- **Sending a secret:** encrypt with the server's public key, and only the server's private key can decrypt it.
- **Proving who you are:** the server signs with its private key, and anyone with its public key can check that it came from the key's holder.
- **Certificate authority:** checks that the requester owns the domain, so a browser can trust the server is who it says it is.
- **Self-signed:** the traffic is still encrypted, but nobody vouches for the identity, so the browser warns that the site is not secure.
- **Why HTTPS everywhere:** without it, someone in between can impersonate even a harmless site and collect what users type.
The video calls the two keys "public and private certificates"; they are keys. A certificate holds the public key, the domain, and the CA's signature. HTTPS was first HTTP over SSL; it uses TLS today.
About TechKnowSurge
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →