Why These Terms Matter for Everyday Internet Users
Encryption language shows up constantly — in browser address bars, app privacy disclosures, and news headlines about data breaches. Yet most explanations either skip the definitions entirely or bury them in technical jargon that assumes a computer science background.
This glossary fills that gap. Whether you're evaluating a messaging app, checking whether a website is safe to enter your credit card number, or just trying to understand what your phone's settings menu actually means, these definitions give you a grounded, accurate foundation. For a broader look at internet vocabulary, see our internet terminology reference covering bandwidth, latency, routers, and more.
Once you're comfortable with these terms, building safer digital habits becomes a much more achievable goal — because you'll understand the "why" behind each recommendation.
Encryption
The process of converting readable data (plaintext) into a scrambled format (ciphertext) using a mathematical algorithm. Only someone with the correct key can decode it back into readable form.
HTTPS
HyperText Transfer Protocol Secure — the standard that encrypts the connection between your browser and a website. The padlock icon in your browser's address bar signals an active HTTPS connection.
End-to-End Encryption (E2EE)
A method where only the sender and the intended recipient can read the message. Not even the app provider or the server relaying the message can access its contents.
TLS (Transport Layer Security)
The current cryptographic protocol that powers HTTPS. TLS replaced its predecessor, SSL, and is what actually secures data in transit between devices and servers today.
SSL (Secure Sockets Layer)
An older encryption protocol that TLS replaced. You'll still hear "SSL" used informally to mean any secure web connection, but modern connections use TLS — the term is largely a legacy holdover.
Encryption Key
A string of data used to encrypt or decrypt information. Think of it as a unique combination for a lock — the right key opens it; any other key cannot.
Public Key / Private Key
In asymmetric encryption, a public key is shared openly and used to encrypt messages, while the private key is kept secret and used to decrypt them. Data encrypted with your public key can only be unlocked by your private key.
Cipher
The specific algorithm used to perform encryption. AES (Advanced Encryption Standard) is one widely used cipher; it governs exactly how plaintext gets transformed into ciphertext.
Plaintext / Ciphertext
Plaintext is data in its original, readable form. Ciphertext is what that data looks like after encryption — a scrambled string that appears meaningless without the decryption key.
Zero-Knowledge Encryption
An architecture where a service provider stores your encrypted data but has no way to read it — they hold no copy of your key. Common in privacy-focused cloud storage services.
Digital Certificate
A file that verifies a website's identity and enables encrypted connections. Issued by a trusted Certificate Authority, it confirms that the site is legitimate before your browser establishes a secure session.
VPN (Virtual Private Network)
A service that encrypts your internet traffic and routes it through a server in another location, masking your IP address and protecting data on unsecured networks like public Wi-Fi.
Core Concepts, Defined Clearly
Encryption terms tend to cluster around a few core ideas: how data is scrambled, who holds the keys to unscramble it, and at what points during transmission the data is protected. The distinctions matter because not all encryption is created equal.
| Current secure web protocol | TLS 1.3 (released 2018) (Internet Engineering Task Force (IETF) RFC 8446) |
| What the browser padlock indicates | Active HTTPS / TLS connection |
| AES key length (common standard) | 128-bit or 256-bit (U.S. National Institute of Standards and Technology (NIST)) |
| Who can read E2EE messages | Sender and recipient only |
| SSL vs. TLS | SSL is obsolete; TLS is the active standard (SSL 3.0 deprecated via IETF RFC 7568 (2015)) |
Encryption in Transit vs. Encryption at Rest
Encryption in transit protects your data while it moves between your device and a server — for example, when you submit a login form. Encryption at rest protects data while it sits stored on a server or hard drive. A service can offer one without the other, so it's worth knowing which type a provider uses when privacy is important to you.
Symmetric vs. Asymmetric Encryption
These two approaches describe how encryption keys are managed. Symmetric encryption uses the same key to lock and unlock data — fast and efficient, but the key must be shared securely. Asymmetric encryption uses a mathematically linked key pair: a public key anyone can use to encrypt, and a private key only the recipient holds. HTTPS relies on asymmetric encryption during the initial handshake before switching to symmetric for speed. For more on how foundational digital concepts connect across verticals, our Devices & Gadgets hub covers related consumer technology topics in accessible language.
Certificates and Certificate Authorities
When your browser displays a padlock icon, it's trusting a digital certificate — a file that verifies a website is who it claims to be. These certificates are issued by organizations called Certificate Authorities (CAs), which act as trusted third-party verifiers. If a certificate is expired, self-signed without proper verification, or issued by an untrusted CA, your browser will warn you — and that warning is worth heeding.
The content on this site is provided for informational purposes only and should not be considered a substitute for professional advice. While we strive to provide accurate and up-to-date information, we make no guarantees regarding its completeness or accuracy. Always consult a qualified professional for advice specific to your circumstances before making any decisions.