HTTPS: How TLS Protects HTTP
HTTPS carries HTTP over TLS. TLS can protect confidentiality and integrity and authenticate a server when the client validates its certificate and name.
Updated · Editorial approach and simulation limits
HTTPS combines HTTP with a protected channel
The browser resolves and connects to a server, negotiates TLS, validates the server identity according to its trust store, and then sends HTTP messages through the protected channel. Certificate validation is a client-side check; merely seeing a certificate in a trace does not prove that the browser accepted it.
TLS 1.3 uses a handshake to agree cryptographic parameters and establish traffic keys. After that, application records are encrypted and integrity-protected. A network observer can still see connection endpoints, timing and some handshake metadata, but not the protected HTTP body without authorized decryption material.
ALPN chooses the application protocol
Application-Layer Protocol Negotiation (ALPN) lets a TLS client offer application protocol identifiers such as HTTP/1.1 or h2, and the server can select one. This choice affects how HTTP is framed after TLS. HTTP/3 uses QUIC and its own TLS integration rather than an HTTP-over-TCP TLS connection.
An ALPN result can explain why two successful HTTPS connections use different HTTP versions. If TLS succeeds but a request fails, move up to HTTP status, headers, routing and application behavior instead of treating every error as a certificate problem.
What HTTPS does not promise
HTTPS protects data in transit between the TLS endpoints; it does not certify that a page’s content is truthful, that a downloaded file is harmless, or that a server has correct authorization. It also does not make the chosen server invisible to the client’s network.
For a real incident, note whether the capture is before TLS, at a terminating proxy or at an endpoint. Protocol Explorer separates the illustrative HTTPS stages, but it does not validate a live certificate or inspect your browser traffic.
Explore HTTPS interactively
Follow the matching exchange packet by packet. The animation is a scripted teaching model with illustrative timing, not a capture of your network.
Specification and source
For exact protocol requirements, consult the primary document: RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3. This page summarizes selected behavior and is not a substitute for the specification.
Related protocol lessons
Browse all security and access protocols · Compare HTTPS over TCP with HTTP/3 over QUIC