SSL (Secure Sockets Layer)
SSL is the historical predecessor of TLS. When people refer to an SSL certificate or SSL encryption today, they generally mean TLS. With HTTPS, TLS protects the connection between client and server against straightforward eavesdropping and unnoticed modification and authenticates the requested host through a digital certificate.
A valid certificate does not prove that a company is trustworthy or that a website contains no malicious code. It primarily confirms control relating to the names in the certificate and enables a protected connection. Secure operation requires current protocols, correct certificate chains, automatic renewal, HTTPS redirects, secure cookies, and protection of the application itself.
- TLS rather than SSL is used technically today
- HTTPS protects data during transmission
- Certificates authenticate the requested host
- Not proof of trustworthy or safe content
- Monitor renewal and configuration
Frequently asked questions
The common term now usually refers to a TLS certificate used to authenticate a host and establish an encrypted HTTPS connection.
No. HTTPS protects data in transit. Vulnerabilities in the application, accounts, server, or content require separate protection.
