What Is an SSL Certificate?

Learn how SSL/TLS certificates encrypt internet traffic, how the chain of trust works, the difference between DV, OV, and EV certificates, and why TLS replaced SSL.

What Is an SSL Certificate?

An SSL certificate is a digital certificate that authenticates a server's identity and enables encrypted communication between clients and servers using the TLS (Transport Layer Security) protocol. Although the industry moved from SSL to TLS over two decades ago, the term "SSL certificate" persists in common usage.

TLS vs. SSL

SSL (Secure Sockets Layer) was the original encryption protocol for the web, developed by Netscape in the 1990s. It was replaced by TLS, which is more secure and actively maintained:

  • SSL 2.0 and 3.0 are deprecated and considered insecure (RFC 6176, RFC 7568).
  • TLS 1.0 and 1.1 are deprecated as of RFC 8996.
  • TLS 1.2 remains widely used and considered secure.
  • TLS 1.3 (RFC 8446) is the current standard, offering improved performance and security.

When you see "SSL certificate," it almost always means a certificate used with TLS.

How Certificates Enable Encryption

When a client (browser, mail client, API consumer) connects to a server over HTTPS or STARTTLS:

  1. TLS handshake begins. The client sends a ClientHello message specifying supported TLS versions and cipher suites.
  2. Server presents certificate. The server responds with its certificate, which contains the server's public key, the domain name(s) it covers, the issuing certificate authority (CA), and a validity period.
  3. Client validates certificate. The client checks that the certificate is signed by a trusted CA, is not expired, and matches the requested domain.
  4. Key exchange. The client and server negotiate a symmetric session key using the certificate's public key (or an ephemeral key exchange like ECDHE).
  5. Encrypted communication. All subsequent data is encrypted with the session key.

Certificate Authorities and Chain of Trust

Certificates are issued by Certificate Authorities (CAs), organizations trusted by browsers and operating systems. The trust model is hierarchical:

  • Root CAs have self-signed certificates embedded in browser and OS trust stores.
  • Intermediate CAs are signed by root CAs and issue end-entity (server) certificates.
  • The chain of trust runs from your server's certificate, through the intermediate CA, up to the root CA.

Major CAs include Let's Encrypt (free, automated), DigiCert, Sectigo, and GlobalSign.

Certificate Types

Type Validation Use Case
DV (Domain Validation) Proves you control the domain (via DNS or HTTP challenge). Issued in minutes. Blogs, personal sites, APIs, most web applications.
OV (Organization Validation) Verifies the organization's legal existence. Takes days. Business websites where organizational identity matters.
EV (Extended Validation) Rigorous vetting of the organization. Takes weeks. Financial institutions, e-commerce (though browsers no longer display the green bar).

For most use cases, DV certificates (especially from Let's Encrypt) provide the same encryption strength as OV and EV at zero cost.

Certificates and Email

TLS certificates secure email in two contexts: encrypting SMTP connections between mail servers (STARTTLS on port 25, implicit TLS on port 465) and encrypting IMAP/POP3 connections between mail clients and servers. A missing or expired certificate on your mail server can cause delivery failures when sending servers enforce TLS. Check your domain's DNS and mail configuration with our DNS lookup tool.


Stay on top of your email infrastructure. Sign up for the InboxTooling newsletter for deliverability tips, tool updates, and best practices.