What Is an SSL Certificate Chain? How It Works and Common Certificate Errors
An SSL certificate chain connects your website's certificate to a root the browser already trusts. Here is how the check works, why it fails on some devices only, and what the usual error codes mean.

An SSL certificate chain is the ordered set of certificates that connects your website's own certificate to a root certificate the visitor's browser already trusts. Your server sends its certificate together with one or more intermediate certificates, the browser checks each signature in turn, and if every link holds, the page loads without complaint. If a link is missing, out of date or issued for a different name, the visitor gets a full-page warning instead of your site.
The name is a leftover. Let's Encrypt's glossary describes SSL as an older name for TLS, the protocol HTTPS uses to encrypt and authenticate visits to a web page, and notes that the old name is still in common use. Hosting companies sell "SSL certificates"; the technology underneath is TLS.
The three kinds of certificate in a chain
A certificate is a file holding a public key plus data about how that key may be used. A chain is built from three kinds:
- The leaf, or end-entity, certificate is the one issued for your site. It is valid for a set of domain names and cannot sign other certificates.
- An intermediate certificate is signed by a root or by another intermediate and can sign certificates itself. Authorities use intermediates to sign leaf certificates so that the root's private key can stay offline.
- The root certificate is self-signed, controlled by the certificate authority and included in certificate stores.
The roots are the part you never handle. Operating systems and browsers keep a certificate store, a list of trusted roots, and a browser without its own store uses the one in the operating system. Each store is governed by a root programme: the policies that decide which certificate authorities get in. An authority that is missing from the store on a visitor's device is, for that visitor, untrusted.
Let's Encrypt is a convenient example because it publishes its whole hierarchy. Its certificates page (updated November 2026) lists ISRG Root X1 and ISRG Root X2 as its roots in trust stores, states that the root key material is kept offline, and names the intermediates that sign subscribers' certificates day to day.
How a browser checks the chain
The order is set out in the TLS 1.3 specification, RFC 8446. The server's own certificate must come first in the list, and each certificate after it should directly certify the one before. The root may be left out, because a browser that trusts it already has a copy.
The browser then works up the list. The validation rules in RFC 5280 require that:
- the issuer named on each certificate is the subject of the next one up;
- each signature can be verified with the issuer's public key;
- the current time falls inside every certificate's validity period;
- no certificate in the path has been revoked;
- the path starts from a trust anchor, meaning a root the device already holds.
One failed check is enough. If the browser cannot build an acceptable chain from what it was sent and what it already holds, it can abandon the connection, and that is the moment a customer sees a warning page.
Why a site can work in one browser and fail in another
The classic chain fault is a server that sends only the leaf certificate. The nginx documentation describes the result: some browsers complain about a certificate from a well-known authority while others accept it, because the intermediate that signed it is not in the certificate base shipped with that particular browser. Browsers in heavy daily use may already hold the intermediate and stay quiet.
Firefox goes further. Mozilla wrote in November 2020 that desktop Firefox downloads the trusted intermediates in advance, a list of more than two thousand entries, to cut the errors users met when servers were not configured with the right intermediates.
So your own laptop is a poor test device. A florist's site can look fine in the office and still throw a warning in a different browser on a customer's phone.
Common SSL certificate errors and their causes
Chrome reports certificate problems with short codes defined in the Chromium source code. The explanations below come from the comments in that list of network errors.
| Error code | What the browser found | Causes named in the Chromium list |
|---|---|---|
| ERR_CERT_AUTHORITY_INVALID | The certificate is signed by an authority the browser does not trust | A self-signed certificate; a legitimate authority the device does not know; a substitute certificate from an attacker |
| ERR_CERT_DATE_INVALID | By the device's clock, the certificate has expired or is not yet valid | A misconfigured server; a wrong clock on the visitor's device; an attacker reusing an old certificate |
| ERR_CERT_COMMON_NAME_INVALID | The name on the certificate does not match the host name | Server misconfiguration; a Wi-Fi login page intercepting the connection; traffic redirected by an attacker |
Two of these are easy to cause yourself. The name mismatch appears when a certificate covers www.example.co.uk and a visitor types example.co.uk: the Subject Alternative Name field lists the domains a certificate is valid for, and a name the field does not cover fails. The date error appears as soon as a certificate passes its expiry time without being renewed.
In Firefox, a missing intermediate tends to surface as an "unknown issuer" error. The certificate is genuine, but the browser cannot connect it to a root.
How to check and fix your chain
You can see what your server sends with one OpenSSL command, run from any computer that has OpenSSL installed:
openssl s_client -connect www.example.co.uk:443 -showcerts
The OpenSSL manual says the -showcerts option displays the certificates the server sent, in the order it sent them, and warns that this is not a verified chain. In the output the server's certificate is numbered 0 and the intermediates follow. The nginx documentation notes that if no bundle has been added, only certificate 0 is shown. That single entry is the diagnosis.
The repair depends on who runs the server:
- On a website builder or managed hosting, the host installs the certificate. Send support the address and the error code and ask them to install the full chain.
- On your own server, install the certificate file that includes the intermediates. For nginx the server certificate must come first in the combined file, followed by the chained certificates; in the wrong order nginx fails to start and reports a key mismatch.
- With an automated client, use the chain file it produces and avoid copying one particular intermediate into your configuration by hand. Let's Encrypt keeps several intermediates in rotation and says its backup ones can start issuing at any time without warning.
Keeping the chain valid: renewals and cost
Every certificate in the chain has an end date. Let's Encrypt's FAQ (2025) gives 90 days as the default lifetime of its certificates, with an optional six-day certificate, and says it charges no fee, though a hosting provider may add an administrative charge. It issues domain-validated certificates only.
Lifetimes across the industry are falling. In April 2025 the CA/Browser Forum, whose members vote as certificate issuers and certificate consumers, passed ballot SC-081v3. It cuts the maximum validity of a publicly trusted TLS certificate from 398 days to 47 days, in reductions starting in March 2026 and ending in March 2029.
Renewing by hand once a year was manageable; renewing every few weeks is a job for software. Ask your host whether renewal is automatic, and put the check on your website maintenance list next to the domain name renewal, since a certificate is only valid for the names written into it.
Questions
Do I need to install the root certificate on my server?
No. RFC 8446 allows a certificate that specifies a trust anchor to be omitted, on the basis that the other side already holds it. The server needs the leaf certificate and the intermediates, and the root sits in the visitor's browser or operating system.
Why does my SSL certificate error appear on some devices only?
A common reason is a server that does not send an intermediate certificate. Devices that happen to hold that intermediate accept the site, and devices without it cannot link your certificate to a trusted root.
How long does an SSL certificate last?
It depends on the issuer. Let's Encrypt certificates run for 90 days by default, a figure it has said will fall to 64 days in February 2027 and 45 days in February 2028. The CA/Browser Forum has voted to bring the maximum for publicly trusted certificates down from 398 days to 47 days by March 2029.
Sources
Read next
What Is a Call to Action? Examples and How to Write One
A call to action is the wording, usually on a button or link, that tells a reader what to do next. Examples for small businesses, a way to …
Website Copywriting: How to Write Pages Customers Understand
Website copywriting is writing your pages so a visitor quickly sees what you offer and what to do next. Here is a working method, with befo…
How to Choose a Domain Name for a Small Business
Pick the name customers already use, the ending that matches where you sell, and a registrar with two-step verification. A practical guide …


