HTTPS and TLS: How the Browser Padlock Works

What HTTPS Is — and What It Isn't

When you visit a website and see https:// in the address bar along with a padlock icon, you're looking at HTTPS — HyperText Transfer Protocol Secure. It means the connection between your browser and the web server is encrypted.

But here's what surprises most people: HTTPS does not mean the website is trustworthy or legitimate. A phishing site can — and often does — use HTTPS. The padlock only tells you that your connection to that server is encrypted, not that the server belongs to who you think it does.

HTTPS is powered by TLS (Transport Layer Security), a cryptographic protocol. TLS replaced the older SSL protocol, though the terms are still used interchangeably. If someone says "SSL certificate," they almost certainly mean a TLS certificate.

The TLS Handshake: How a Secure Connection Is Established

Every time your browser connects to an HTTPS website, it performs a TLS handshake in milliseconds. Here's what happens:

1. Client Hello: Your browser sends a message to the server with the TLS versions and cipher suites it supports.
2. Server Hello: The server responds, selecting the agreed-upon TLS version and cipher suite, and sends its digital certificate.
3. Certificate verification: Your browser checks the certificate against a list of trusted Certificate Authorities (CAs) built into your OS and browser. It verifies the certificate is valid, not expired, and issued for the correct domain.
4. Key exchange: Browser and server perform a key exchange (using algorithms like ECDHE) to derive a shared session key — without ever transmitting the key itself over the network.
5. Encrypted communication begins: All subsequent data is encrypted symmetrically using the session key.

The brilliant part: even if someone recorded every packet of your TLS handshake, they cannot derive the session key — this is forward secrecy.

What Is a TLS Certificate?

A TLS certificate is a digital document that proves a server's identity. It contains:

• The domain name it's issued for
• The public key of the server
• The issuing Certificate Authority
• An expiration date
• A digital signature from the CA

Certificate Authorities are organizations trusted to verify that a domain is controlled by who claims to own it. There are three levels of validation:

• Domain Validation (DV): The CA confirms you control the domain. Fast and cheap (often free via Let's Encrypt). No identity verification.
• Organization Validation (OV): The CA verifies the organization exists and owns the domain. More trust, more process.
• Extended Validation (EV): Rigorous vetting of the legal entity. Previously showed a green company name in browsers — most browsers have deprecated this visual indicator.

For most purposes, DV certificates (like those from Let's Encrypt) provide strong encryption. The level of validation doesn't affect the strength of encryption — only how much identity verification was done.

What TLS Protects Against

TLS provides three security properties:

• Confidentiality: Data is encrypted and unreadable to anyone intercepting the traffic.
• Integrity: A MAC (Message Authentication Code) ensures data cannot be modified in transit without detection.
• Authentication: The certificate proves you're talking to the right server (assuming you trust the CA chain).

This makes TLS highly effective against passive eavesdropping — someone listening on a public Wi-Fi network cannot read your HTTPS traffic.

What TLS Does Not Protect Against

• Compromised endpoints: If malware is installed on your device, it can intercept data before it's encrypted or after it's decrypted.
• Malicious websites with valid certificates: A legitimate certificate on a fraudulent site means your traffic to the scam site is encrypted — but you're still being scammed.
• Certificate Authority compromise: If a CA is hacked or issues rogue certificates, attackers can impersonate legitimate sites. This has happened historically (e.g., DigiNotar in 2011).
• Content at the server: TLS protects data in transit only. What the server does with your data after receiving it is entirely separate.

TLS Versions and Why They Matter

Not all TLS versions are equal:

• TLS 1.0 and 1.1: Deprecated. Known vulnerabilities. No modern browser accepts these.
• TLS 1.2: Widely supported, generally secure with correct configuration.
• TLS 1.3: Current best version. Faster handshake, removed legacy cipher suites, mandatory forward secrecy. Use this if you're configuring a server.

You can check which TLS version a site uses by clicking the padlock in your browser and viewing certificate details, or using tools like SSL Labs' server test (ssllabs.com/ssltest).

Practical Takeaways

• Always ensure sites handling sensitive data (banking, shopping, accounts) use HTTPS — look for the padlock
• Do not assume a padlocked site is safe from fraud — verify the domain carefully
• HTTPS does not protect your data once it reaches the server
• Use SSL Labs to audit your own website's TLS configuration
• Prefer sites that support TLS 1.3 and have HSTS headers set (which force HTTPS connections)