January 1999
TLS 1.0 standardized
RFC 2246 defined TLSTransport Layer Security — encryption that protects data in transit on the web and networks. 1.0 in January 1999 — the IETFInternet Engineering Task Force — develops RFC standards for TCP/IP, HTTP, DNS, and other internet protocols. standard that succeeded SSL for encrypted web and application traffic.
What it was for
TLSTransport Layer Security — encryption that protects data in transit on the web and networks. wraps TCPTransmission Control Protocol — a reliable, connection-oriented protocol used on the internet. connections with encryption and identity verification — the padlock in your browser, `https://` APIs, and secure database links. Handshakes negotiate ciphers; certificates prove server identity. Every modern site, mobile app backend, and microservice mesh depends on TLSTransport Layer Security — encryption that protects data in transit on the web and networks. or its successors.
Companies
- IETF
Why it's here
TLSTransport Layer Security — encryption that protects data in transit on the web and networks. 1.0 gave the internet a vendor-neutral standard for transport security after proprietary SSL wars.
Why it mattered
It made encrypted HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages. practical at scale and underpins e-commerce and APIApplication programming interface — a defined way for programs to talk to each other or to a service. security today.
What it solved
Proprietary SSL implementations fragmented; the web needed one auditable protocol for privacy on the wire.
Media
- ImageHTTPS
IETF HTTP Working Group (HTTPbis), Public domain, via Wikimedia Commons
Related
- HTTP/1.1 standardizedJanuary 1997
- Netscape Navigator 2.0 shippedMarch 18, 1996
- OAuth 2.0 standardizedOctober 2012
- Let's Encrypt public beta launchedDecember 3, 2015