Skip to content
AdminKit

Certificate chain

What is Certificate chain?

A certificate chain is the ordered sequence of certificates, per RFC 5280's path-validation rules, linking a server's TLS certificate up through one or more intermediate certificates to a root a client already trusts. AdminKit's SSL/TLS check inspects whether a server actually sends every certificate in that chain, since a missing intermediate breaks validation for clients that won't fetch it themselves.

By AdminKit team, Netbase JSC · Updated

A server’s TLS certificate (its leaf certificate) is almost never signed directly by a root a browser or operating system trusts — certificate authorities keep that root key offline and sign through one or more intermediate certificates instead. RFC 5280 (document record at the IETF Datatracker) defines certification path validation as building this entire sequence, leaf up to a trusted root, checking that each certificate is correctly signed by the next one up; the chain a server sends during the TLS handshake has to include every intermediate in that path. A chain can be individually valid at every link and still fail validation if even one intermediate is missing from what the server actually sent. Some browsers cache or fetch a missing intermediate automatically; many others, including common command-line tools and mail servers, validate only what the server provides, with no fallback. nginx’s HTTPS configuration guide explains the inconsistency — browsers usually store intermediates they have already received, so one in active use may not complain about a missing chain — and has administrators concatenate the CA’s intermediate bundle after the server certificate. Let’s Encrypt’s own chain-of-trust documentation shows the same structure from an issuing certificate authority’s side: a complete chain bundles the leaf with its required intermediates so a client never has to fetch one separately.

Certificate chain is part of AdminKit’s machine protocols cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

Can a certificate chain be valid at every individual link and still fail?

Yes -- RFC 5280 requires the entire sequence from leaf to trusted root, so a chain missing even one intermediate the server should have sent fails validation even though every certificate it provided is genuinely valid.

Why does a missing intermediate certificate break some clients but not others?

Some browsers cache or fetch a missing intermediate automatically, but many command-line tools and mail servers validate only what the server actually sends, with no fallback to fetch anything else.

Who is responsible for sending the full certificate chain?

The server -- RFC 5280's path-validation rules assume the server bundles its leaf certificate with every required intermediate, since a client correctly trusts only the root, not the intermediates on their own.

Does a root certificate ever need to be sent by the server?

No -- clients already trust the root locally, so a complete chain only needs the leaf plus its intermediates, which is exactly what Let's Encrypt's own chain-of-trust documentation shows from the issuing side.