Glossary

SSL/TLS certificate

A file that binds a domain name to a public key, signed by a certificate authority, enabling HTTPS.

In plain English The small file that proves a website is really who it says it is and turns on the padlock (HTTPS).

An SSL/TLS certificate is a small file that lets a website prove its identity and set up an encrypted HTTPS connection. It says “this public key belongs to example.com“, and it is signed by a certificate authority that browsers trust. “SSL” is the old name; current connections use TLS, but the name stuck.

What is inside

FieldExample
Names covered (Subject Alternative Names)example.com, www.example.com
IssuerThe certificate authority, such as Let’s Encrypt
Valid from and untilDates; Let’s Encrypt certificates last 90 days
Public keyUsed to set up the encrypted connection

The matching private key stays on the server and must stay secret. See what a site’s certificate contains:

echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -subject -issuer -dates -ext subjectAltName

Kinds of certificate

  • Single-name, multi-name, or wildcard (*.example.com, covering one level of subdomainsSubdomain A name in front of your domain, like shop.example.com or blog.example.com. It can show a different site from the main one. More about Subdomain →).
  • Domain validated, organisation validated, or extended validation. All give the same encryption and the same padlock; the difference is how much the CA checked.

When certificates go wrong

An expired certificate, one for the wrong name, or a missing intermediate certificate makes browsers show “Your connection is not private”. Free certificates from Let’s Encrypt renew automatically, which avoids the most common problem: forgetting.