03.04 · Short-concept
TLS
Describe what the handshake establishes and what a certificate actually proves.
TLS turns an untrusted connection into an encrypted channel tied to a verified server identity. The handshake agrees symmetric keys and checks that the peer controls the private key for a certificate matching the requested hostname. It protects confidentiality and integrity, but it does not prove the site is trustworthy.
What this lesson answers
- what does the TLS handshake establish
- what does a TLS certificate prove
- does TLS prove a website is legitimate
Notes
TLS — TLS exists to turn an untrusted network connection into an authenticated, encrypted channel; without it, intermediaries can read traffic, modify bytes in transit, or impersonate servers during connection setup.
Key Concepts: - A TLS handshake establishes shared symmetric keys, commonly using ephemeral Diffie-Hellman such as ECDHE, where both sides derive the same secret without sending it directly: . - A certificate proves that a public key is bound to a domain name, for example `api.example.com`, because a trusted Certificate Authority signed that binding.
References
Common questions
- What does the TLS handshake actually do?
- The handshake lets client and server agree on shared symmetric keys without sending the final secret across the network. It also authenticates the server by checking its certificate and related handshake data. After that, application traffic uses faster symmetric encryption with integrity checks.
- What does a certificate prove in TLS?
- A certificate proves that a public key is bound to a hostname because a trusted certificate authority signed that claim. The client still has to verify the chain, the hostname, validity period, signatures and revocation signals. It proves key control for that name, not honesty or business legitimacy.
- Is TLS still end-to-end behind a load balancer?
- Not necessarily. If a proxy, ingress controller, CDN or load balancer terminates TLS, the encrypted connection ends there. The next hop to the backend may use a separate TLS connection or plain HTTP, depending on configuration. Operationally, that changes where traffic is decrypted and which certificate is being verified.
Short definition: what is TLS?