# HTTPS and TLS Encryption

> What HTTPS adds to HTTP, and how TLS locks the line and checks the server. Why the padlock does not mean a site is honest.

**Course:** [Computer Networking](https://learn.benibix.com/learn/infrastructure-networking)  
**Time:** 12 min

**After this lesson you can:**

- Say what TLS protects against
- Explain what the certificate proves
- Say what the padlock does not promise

## What HTTPS adds, and what the padlock means

HTTPS is HTTP sent over a locked line. The lock is TLS, transport layer security. It does two jobs. It scrambles the data so no one in between can read or change it. And it checks that the server really is the site you asked for. HTTPS uses port 443, and almost every site now uses it.

Without the lock, plain HTTP crosses the network as readable text. Anyone on the same cafe Wi-Fi, or any box along the way, can read a password or swap the page for a fake. With TLS, all they see is noise.

Before any page moves, the browser and the server do a short greeting. They agree on a secret key that only the two of them know. The newest version, TLS 1.3, needs just one round trip for this. Everything after it is scrambled with that key.

The check uses a certificate. It is a small file the server shows, saying this key belongs to this name. It is signed by a company that browsers trust. The browser checks the signature, the name and the date, and only then shows the padlock.

If any check fails, the browser shows a full-page warning instead of the site. The name may not match, the certificate may have run out, or nobody trusted signed it. Clicking past that warning throws away the very check that makes HTTPS safe.

The padlock proves that the line is private and that you reached the name in the address bar. It does not prove the site is honest. A fake shop at a name that looks like a real one can have a valid certificate too. Read the name, not just the lock.

People often think HTTPS slows a site down. Today the cost is tiny, and HTTPS also allows the newer, faster versions of HTTP. Browsers now mark plain HTTP pages as not secure, so there is no good reason left to run a site without it.

![The same login sent twice past someone listening on cafe Wi-Fi. In the top lane, marked HTTP, the text pass=sunflower22 crosses from browser to server in plain view, and a note says the listener reads it and could change it. In the bottom lane, marked HTTPS, the same login crosses as scrambled characters, and notes say TLS locks the line first, so the listener sees only noise, and the browser has checked the server is the real one.](https://learn.benibix.com/diagrams/infc-https-lock.svg)

### Example: Jack works from a hotel

Jack logs in to his bank from hotel Wi-Fi shared by 200 guests. The bank uses HTTPS, so the hotel's network only sees that he reached the bank's name.

One night the browser shows a warning that the certificate does not match. He does not click past it. He switches to his phone's own data, and the bank loads with its padlock as normal.

**Words in this lesson:** [HyperText Transfer Protocol Secure (HTTPS)](https://learn.benibix.com/term/infrastructure/https), [Transport Layer Security (TLS)](https://learn.benibix.com/term/infrastructure/tls), [TLS Certificate](https://learn.benibix.com/term/infrastructure/tls-certificate)

**Question:** What does the padlock next to a web address prove?

**Answer:** That the line is private and you reached the name in the address bar. TLS proves the line is locked and the server owns that name. A scam site can have a padlock too, so the name itself still has to be read.

---

Source: https://learn.benibix.com/learn/infrastructure-networking/https-and-tls-encryption
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
