System Atlas
the atlas

HTTP vs HTTPS

The single letter that turns an open postcard into a sealed, verified envelope.

the gist

HTTP sends everything in plaintext over port 80; HTTPS wraps the same HTTP in a TLS-encrypted channel over port 443. TLS adds confidentiality, integrity and server authentication via certificates. The old 'it's slower' objection is effectively gone with TLS 1.3, and browsers now brand plain HTTP as 'Not Secure'.

ANALOGY // HTTP is shouting your order across a crowded room; HTTPS is stepping into a soundproof booth after checking the clerk's badge — nobody else can hear or alter what you say.
living diagram01 / 05
ConfidentialityTLS-encrypted vs plaintext
Integritydetects tampering in transit
AuthenticationCA-signed certificate
Browser trust & SEOno 'Not Secure' label
Performance costnegligible with TLS 1.3
HTTP is plaintext on port 80; HTTPS encrypts the same bytes with TLS on port 443, so eavesdroppers see only ciphertext.
01

Confidentiality

Plain HTTP sends requests and responses as readable text, so anyone on the path — a café Wi-Fi snoop, an ISP, a compromised router — can read passwords, cookies and page content. HTTPS wraps the exact same HTTP inside a TLS-encrypted channel, so an eavesdropper sees only meaningless ciphertext. This is the headline reason HTTPS exists and why it scores the highest on our confidentiality dimension.

02

Integrity

Beyond secrecy, TLS guarantees that data arrives exactly as it was sent, using message authentication codes to detect any tampering in transit. Over plain HTTP an attacker or a shady intermediary can silently inject ads, rewrite links, or corrupt a download and you would never know. HTTPS makes such modification detectable, so the browser rejects altered traffic rather than trusting it.

03

Authentication

During the handshake the server presents a certificate that binds its identity to a public key, signed by a Certificate Authority the browser already trusts. This proves you are actually connected to the real bank, not an impostor performing a man-in-the-middle attack. Encryption without authentication would be useless — you could be secretly whispering to the wrong person — which is why the certificate is central.

04

Trust & SEO

Because these guarantees now matter to everyone, browsers actively flag plain HTTP pages as 'Not Secure' in the address bar, and forms on them trigger warnings. Search engines also treat HTTPS as a positive ranking signal, so it affects visibility as well as safety. The lock icon has become the baseline expectation of a trustworthy site, which is why HTTPS is effectively mandatory today.

05

Performance cost

The classic objection was that TLS adds an extra handshake and encryption overhead, making HTTPS slower. With TLS 1.3 (which cuts the handshake to a single round trip, or zero on resumption) and hardware-accelerated crypto, that cost is now negligible — often unmeasurable. In fact HTTPS is a prerequisite for HTTP/2 and HTTP/3, so going secure usually makes sites faster, not slower.

the full picture
01

The same protocol, one layer apart

HTTP (HyperText Transfer Protocol) is the request/response language of the web: a client asks for a resource, a server answers. HTTPS is not a different protocol — it is exactly the same HTTP, but sent through an encrypted TLS (Transport Layer Security) channel instead of over a bare TCP connection. The mental model is a wrapper: HTTP is the letter, and HTTPS is the sealed, tamper-evident, identity-verified envelope you put the letter inside.

That single distinction has enormous consequences. Plain HTTP travels as readable text across every router, switch and Wi-Fi access point between you and the server. Anyone positioned on that path — an ISP, a network operator, someone running a rogue hotspot — can read every byte and, worse, modify it in flight. HTTPS closes that exposure by encrypting the connection before any HTTP is exchanged, so intermediaries can move the packets along but cannot read or alter their contents.

The default ports encode the difference: HTTP listens on port 80, HTTPS on port 443. When you type a URL without a port, the scheme decides which one the browser dials, which is why http:// and https:// quietly connect to different services on the same machine.

02

What TLS actually guarantees

The value of HTTPS is best understood as three guarantees delivered together, all of which plain HTTP lacks:

  • Confidentiality (encryption). The contents of every request and response are encrypted, so an eavesdropper sees only ciphertext. Passwords, session cookies, personal data and page content are all hidden.
  • Integrity (tamper-detection). TLS attaches message authentication codes so the receiver can verify that data was not altered in transit. Over plain HTTP, intermediaries have been caught injecting ads, rewriting links and corrupting downloads; HTTPS makes any such change detectable, and altered data is rejected rather than trusted.
  • Authentication (identity). The server proves who it is with a certificate, so you know you are talking to the genuine site and not an impostor.

These three are a package, and the third is what makes the first two meaningful. Encrypting a conversation is pointless if you cannot be sure who is on the other end — you might be perfectly securely talking to an attacker. Authentication is what turns 'a private channel' into 'a private channel *to the right server*'.

03

Certificates and the chain of trust

Authentication in HTTPS rests on certificates and a system of delegated trust. During the TLS handshake the server presents a digital certificate that binds its domain name to a public key. That certificate is digitally signed by a Certificate Authority (CA) — an organisation your browser and operating system already trust because their root certificates ship pre-installed.

The browser checks that the certificate is validly signed by a trusted CA, that it was issued for the domain you are visiting, and that it has not expired or been revoked. If all of that holds, the browser trusts the server's public key and uses it to safely negotiate a shared session key; if any check fails, you get the stern full-page warning that tells users to turn back.

This chain of trust is what defeats a man-in-the-middle attack. An attacker can intercept your traffic and even present their own certificate, but they cannot get a trusted CA to sign a certificate for a domain they do not control, so the browser's validation fails and the impersonation is exposed. The whole edifice — CAs, root stores, certificate validation — exists to answer one question: is this really who it claims to be?

04

Trust signals, SEO and the 'Not Secure' era

HTTPS used to be reserved for login and checkout pages; today it is the default expectation for the entire web, driven as much by ecosystem pressure as by pure security.

Browsers led the push. Modern browsers no longer reward HTTPS with a special badge so much as punish HTTP: plain-HTTP pages are labelled 'Not Secure' in the address bar, and entering data into a form on an HTTP page can trigger an explicit warning. For most users the lock icon (or its absence) is now the primary, at-a-glance signal of whether a site can be trusted at all.

Search engines reinforced it. Google and others treat HTTPS as a positive ranking signal, so serving a site over plain HTTP can cost visibility as well as user confidence. Combined with the fact that many modern browser features — geolocation, service workers, and crucially HTTP/2 and HTTP/3 — are gated behind a secure context, the practical reality is that HTTPS is no longer optional. A serious public website that ships over HTTP in the current era is broken by the standards of both browsers and search engines.

05

The performance myth and modern guidance

The last real objection to HTTPS was performance: TLS adds a handshake and encrypts every byte, so surely it must be slower? That was a defensible worry a decade ago, but it has effectively evaporated.

Two things closed the gap. First, TLS 1.3 streamlined the handshake to a single round trip, and to *zero* round trips when resuming a previous session, dramatically cutting the setup cost that used to be the main penalty. Second, CPUs gained hardware-accelerated cryptography, so the per-byte encryption overhead is now negligible on essentially all modern devices. The measurable cost of HTTPS today is, for most sites, lost in the noise.

More importantly, going secure now tends to make sites *faster*, not slower, because the newer, faster transport protocols — HTTP/2 with multiplexing and HTTP/3 over QUIC — are only available over HTTPS. So the modern guidance is unambiguous: serve everything over HTTPS, redirect HTTP to HTTPS with a 301, enable HSTS so browsers refuse to fall back to plaintext, and take advantage of free, automated certificates (as from Let's Encrypt) so there is no cost or friction excuse left. The security, trust and SEO benefits are large; the performance downside is, in practice, gone.

what to remember
01

HTTP is plaintext on port 80; HTTPS is HTTP inside a TLS tunnel on port 443.

02

TLS gives three guarantees at once: confidentiality, integrity (tamper-detection), and authentication.

03

A certificate signed by a trusted Certificate Authority proves you're really talking to the right server.

04

Browsers now label plain HTTP pages 'Not Secure', and search engines rank HTTPS higher.

05

The old performance penalty is negligible today thanks to TLS 1.3 and modern hardware.

check yourself

Quick quiz

Q1

What does the 'S' in HTTPS actually add on top of HTTP?

Q2

Which statement about HTTPS performance is true today?

follow the thread