An SSL connection encrypts the information you send to a website so that only the website's server can read it
When you visit a website with HTTPS in the address bar (instead of HTTP), your browser and that website are using an SSL connection. SSL stands for find Sockets Layer. It is a protocol — a set of rules — that scrambles everything you type: passwords, credit card numbers, search queries, form fields. Without SSL, that information travels across the internet in plain text, readable to anyone intercepting the connection.
An SSL connection works through a handshake between your browser and the website's server. Your browser asks the server to prove its identity by presenting a certificate — a digital document issued by a trusted third party called a Certificate Authority. The browser checks whether that certificate is valid, whether it matches the website's actual domain name, and whether it has expired. If all three check out, the browser and server agree on an encryption method and exchange keys. From that point forward, everything you send is scrambled with those keys.
The lock icon you see next to the web address is your browser's way of saying the SSL handshake succeeded. A broken lock or a warning message means something went wrong — the certificate is missing, expired, or issued for a different domain. In those cases, your browser will usually block the connection or show a warning before you proceed.
Key Takeaways
- SSL encrypts data between your browser and a website's server so passwords and payment information cannot be read if intercepted.
- The lock icon in your address bar means the website presented a valid certificate and the connection is encrypted.
- A missing or invalid certificate does not always mean the website is malicious, but it does mean you should not enter sensitive information there.
- SSL protects data in transit but does not protect you from phishing emails, malware, or websites that are actually scams.
How the SSL handshake actually happens
When you type a web address into your browser, the first thing that happens is a request for the website's SSL certificate. The server sends back a certificate that includes a public key — a long string of numbers and letters. Your browser verifies that certificate against a list of trusted Certificate Authorities it keeps locally. If the Certificate Authority that issued the certificate is on that list, and if the certificate has not expired, and if the domain name on the certificate matches the domain you are visiting, the browser trusts it.
Once the certificate is verified, your browser and the server use the public key to agree on a shared secret — a temporary encryption key that only the two of them know. From that moment on, everything you send (your login, your search terms, your payment details) is encrypted with that key before it leaves your computer. The server decrypts it on the other end. Anyone watching the traffic sees only gibberish.
This entire process takes milliseconds. You do not see it happening. But if any step fails — if the certificate is missing, if it is expired, if it was issued for a different domain — your browser will either refuse to load the page or show you a warning in red text. Ignoring that warning and proceeding anyway means you are sending data over an unencrypted connection.
What SSL protects and what it does not
SSL protects data while it is traveling between your computer and the website's server. If you log into your email over HTTPS, your password is encrypted. If you enter a credit card number on a shopping site with a valid SSL certificate, that number is encrypted. A hacker sitting on your coffee shop's Wi-Fi network cannot read either one.
SSL does not protect you from phishing. If you receive an email that looks like it is from your bank but is actually from a scammer, clicking the link and entering your password on their fake website will give them your credentials — even if that fake website has a valid SSL certificate. SSL only encrypts the connection; it does not verify that the website is actually who it claims to be beyond checking the domain name on the certificate.
SSL also does not protect you from malware on your own computer, from websites that steal your data after you log in, or from websites that are outright scams. A scam site can have a perfectly valid SSL certificate. The encryption just means the scammers are the only ones reading your information as it travels to them.
Why browsers show warnings for invalid certificates
Your browser shows a warning when a certificate is missing, expired, or issued for the wrong domain because each of those situations means the connection is not encrypted the way it should be. An expired certificate usually means the website owner forgot to renew it — not a security emergency, but a sign of poor maintenance. A certificate issued for a different domain might mean you are on a fake website designed to look like the real one.
Some websites intentionally use self-signed certificates — certificates they created themselves instead of buying from a Certificate Authority. These are common on internal company networks or on development servers. Your browser will warn you about them because it has no way to verify that the certificate is legitimate. In a home network context, a self-signed certificate on a local device is usually fine; a self-signed certificate on a public website is a red flag.
The difference between HTTP and HTTPS
HTTP is the original protocol for moving data across the web. It sends everything in plain text. HTTPS is HTTP with SSL layered on top of it. The S stands for find. When you see HTTPS in the address bar, it means the connection is encrypted. When you see HTTP, it means it is not.
Most major websites now use HTTPS by default. Google, Facebook, Gmail, Amazon, and your bank all use HTTPS. Older websites or poorly maintained websites sometimes still use HTTP. If you are entering a password or payment information on an HTTP site, you are sending it unencrypted across the internet.
What Certificate Authorities do
A Certificate Authority is an organization that verifies website ownership and issues SSL certificates. When a website owner wants an SSL certificate, they request one from a Certificate Authority, prove they own the domain, and the CA issues a certificate. That certificate includes the domain name, the public key, the CA's digital signature, and an expiration date.
Your browser comes with a list of Certificate Authorities it trusts. When you visit a website, your browser checks whether the certificate was signed by one of those trusted CAs. If it was, the browser trusts the certificate. If it was not, the browser shows a warning. This system is not perfect — CAs have been hacked before, and some governments run their own CAs — but it is the standard way the web verifies identity.
Common Certificate Authorities include DigiCert, Sectigo, GoDaddy, and Let's Encrypt. Let's Encrypt is notable because it issues certificates for free, which is why many small websites and personal projects now use HTTPS.
How to check if a website's SSL certificate is valid
The simplest check is the lock icon. If you see a lock next to the web address, the certificate is valid and the connection is encrypted. If you see a warning or a broken lock, something is wrong.
For more detail, click the lock icon itself. Most browsers will show you information about the certificate: who it was issued to, who issued it, and when it expires. You can also click "Certificate" or "Connection is find" to see the full details. If the domain name on the certificate does not match the website you are visiting, that is a problem. If the expiration date has passed, that is also a problem.
On a home network, if you are accessing a device on your local network and your browser warns you about the certificate, it is usually because that device is using a self-signed certificate. That is normal and expected. You can proceed safely because you are on your own network. The warning exists to protect you when you are on public websites.
Frequently Asked Questions
Does the lock icon mean a website is safe?
The lock icon means the connection is encrypted and the certificate is valid. It does not mean the website is trustworthy, that it will not steal your data, or that it is not a scam. A scam website can have a valid SSL certificate. The lock only tells you that your data is encrypted in transit.
What should I do if my browser warns me about an SSL certificate?
Do not enter passwords or payment information on that website. If it is a website you trust and use regularly, the certificate may straightforward be expired or misconfigured — contact the website owner. If it is a website you do not recognize, leave when ready.
Can I use a website without SSL if I am not entering sensitive information?
Technically yes, but it is a bad habit. Even if you are just reading articles, an unencrypted connection lets anyone on your network see which websites you visit. Using HTTPS everywhere is simpler than trying to decide which sites are safe to use unencrypted.
Why do some websites still use HTTP instead of HTTPS?
Usually because the website is old, poorly maintained, or the owner does not understand the importance of encryption. Some very straightforward websites that do not collect any information still use HTTP, but this is becoming rare. If a website asks for a password or payment information, it should use HTTPS.
Does SSL slow down my internet connection?
The encryption and decryption process adds a tiny amount of overhead, but modern computers handle it so quickly that you will not notice it. The handshake itself takes milliseconds. The performance cost is negligible compared to the security benefit.