
The short answer
A TLS certificate (still often called an SSL certificate) is your website’s passport. It is a small signed file that says "this public key belongs to this domain", issued by a certificate authority (CA) that browsers already trust. The padlock in the address bar means the browser checked that file and was satisfied.
What is inside a certificate
The format is X.509, defined in RFC 5280. The fields that matter day to day are:
- The names it covers. These are the domain names in the Subject Alternative Name extension, such as
example.comandwww.example.com. Browsers ignore the old Common Name field for this. - A public key. Its private half stays on your server and is never shared.
- The issuer. This is the CA that signed it, for example Let’s Encrypt, DigiCert or Sectigo.
- The validity dates. It is valid from one date until another. Since 15 March 2026 a public certificate can last at most 200 days, and that limit keeps falling, as we explain in certificate lifetimes are falling to 200, 100 and 47 days.
- The CA's signature over all of the above. Change one byte and the signature no longer matches, so nobody can forge or edit a certificate without the CA’s key.
What happens when someone visits your site
In a TLS 1.3 handshake (RFC 8446), the steps are:
- The browser connects and says which site it wants.
- Your server sends its certificate plus one or more intermediate certificates. An intermediate is the CA’s own certificate that vouches for yours.
- The browser checks that the name matches the site, the certificate is in date and the chain of signatures leads to a root certificate already in its trust store.
- The server signs part of the handshake with its private key. This proves it holds the key that belongs to the certificate rather than a copy of a public file.
- Both sides agree fresh session keys, and the encrypted conversation starts.
If any check fails, the visitor sees a full-page warning instead of your site.
Why certificate warnings happen
Three causes account for most of the warnings we see:
- Expired. The renewal did not happen, or it happened but the new certificate never reached the server that answers traffic. We cover that second case in how to stop certificate expiry outages.
- Wrong name. The certificate covers
www.example.combut someone visitedexample.com, or a new hostname was added behind the load balancer and nobody updated the certificate. - Missing intermediate. The server sends only its own certificate. Some browsers cope by fetching or caching the intermediate, and others, along with most API clients, fail. It works on your laptop and breaks for a customer.
What to do about it
- Serve the full chain: your certificate plus its intermediates, but not the root.
- Make sure each certificate names every hostname that actually points at it.
- Renew well before the expiry date, then check what the endpoint really serves, not just the file on disk.
- Keep an inventory. You cannot renew a certificate you do not know about, which is why we start with discovering every certificate on your network.
With lifetimes shrinking toward 47 days, renewing by hand stops being realistic. Certificate lifecycle management means automating that loop from discovery to verification. You can see how clm.mt does it in the live demo.
Want to know where your own site stands? The free certificate health check shows what your domain serves today and every public certificate issued for it.