Free certificate chain builder
Paste the certificates you have and get them back in the order a server should send them, leaf first, with each link checked by its signature.
Example report
Pasted chain, illustrative- Issuer not supplied; completeness unconfirmed
- Partial chain
- Public trust not checked
Order you supplied
- 1
Example Issuing CA R1CA
#1, issued by Example Root CA, valid until 2030-02-28
- 2
www.example.comLeaf
#2, issued by Example Issuing CA R1, valid until 2026-11-30
- 3
Example Issuing CA R1Duplicate of #1
#3, issued by Example Root CA, valid until 2030-02-28
Suggested order
- 1
www.example.comLeaf
#2, issued by Example Issuing CA R1, valid until 2026-11-30
Signed by #1: signature verifies
- 2
Example Issuing CA R1Intermediate
#1, issued by Example Root CA, valid until 2030-02-28
Issuer not supplied; completeness unconfirmed.
- 3
Example Issuing CA R1Duplicate of #1
#3, issued by Example Root CA, valid until 2030-02-28
Downloads as partial-chain.pem, labelled as a partial chain.
Findings
Warning#1 Example Issuing CA R1, #3 Example Issuing CA R1
This certificate was supplied more than once. Only one copy belongs in a chain.
Warning#1 Example Issuing CA R1
Issuer not supplied; completeness unconfirmed. The top certificate is not self-signed and its issuer was not among those supplied.
Information
Public trust not checked. This tool orders the certificates you supplied by their signatures; it does not check them against any browser's or operating system's trust store, or for revocation.
What the chain builder looks at
Order
See the order you supplied beside the order the signatures support.
Signatures
Link each certificate to its issuer only when the issuer's key verifies it.
Issuers
Check CA constraints, key usage, path length and name constraints.
Export
Download the selected path as one PEM file, leaf first.
No certificate is fetched from the internet, and public trust and revocation are not checked.
Understand the issue and your next step
Each finding explains what was found in the certificates you supplied, why it matters and what you can change. Start with the errors, then the warnings.
- Paste or add your certificates
- Review the order and findings
- Download the ordered chain
A claimed issuer did not sign this certificateHigh
The certificate names Example Issuing CA R1 as its issuer, and a certificate with that name was supplied, but its public key does not verify the signature. Names alone never link certificates, so the link is shown as invalid and the download is blocked.
Leaf: CN=www.example.com
Claims: CN=Example Issuing CA R1
Supplied issuer with that name: signature does not verifyA certificate with the right name but the wrong key is a different issuer: an old or reissued intermediate, one from another chain, or a forgery. A server that sends it gives clients a chain they cannot verify.
Get the intermediate your certificate authority issued with this certificate (it is usually in the same download), replace the one you have, and build the chain again.
Common chain issues you can put right
Certificates in the wrong orderMedium
A chain file that starts with an intermediate, or lists them top down, can fail in clients that do not reorder it. Use the suggested order: leaf first, each certificate followed by its issuer.
Intermediate missingMedium
When the top certificate is not self-signed and its issuer was not supplied, clients that do not fetch it themselves cannot finish the chain. Add the intermediate from your certificate authority.
Signature does not verifyHigh
A certificate named as the issuer did not sign the one below it. The download is blocked until the right issuer is supplied.
Issuer is not a CAHigh
A certificate that signed another is not marked as a certificate authority, or its key usage or constraints do not allow it to issue.
Expired certificate in the chainHigh
An expired intermediate breaks the chain even when the leaf is current. Replace it with the current intermediate from your certificate authority.
Duplicates and cross-signsLow
The same certificate twice, or two versions of one intermediate, make the chain longer and can lead clients down an old path. Keep the copy in the path you choose.
Keep watch after you've fixed it
Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.
Free during the preview. Domain verification required.
- NewIssue detected
- FixedConfirmed by recheck
- ReopenedDetected again
How the check works
- Reads every certificate you paste or add, as PEM (one or more
CERTIFICATEblocks) or as a binary DER file such as a.ceror.crt. - Links a certificate to its issuer only when the issuer's public key verifies its signature. A matching name alone never makes a link.
- Checks that each issuer may issue: CA basic constraints, key usage, path length and name constraints.
- Flags expired or not-yet-valid certificates, duplicates, cross-signed copies, loops and more than one possible path.
- Builds the path from the leaf up and offers it as one PEM file:
ordered-chain.pemwhen it ends at a self-signed root,partial-chain.pemwhen the top issuer was not supplied.
Reading a result
A server sends its own certificate (the leaf) first, then each intermediate in turn, each one signed by the next. Most servers leave the root out, since clients already hold it. A chain in the wrong order, or with an intermediate missing, can work in one browser and fail in an app, a mail server or an API client.
The suggested order is the path the signatures support, leaf first. When the top certificate is not self-signed and its issuer was not among those you supplied, the result says "Issuer not supplied; completeness unconfirmed": that is often the right file to deploy, but the tool cannot confirm that nothing is missing.
A link whose signature does not verify blocks the download: a certificate with the right issuer name but the wrong key is not that issuer, whatever it says.
What it does not do
- No AIA fetching: a missing intermediate is not downloaded from the address in the certificate. Add it yourself if you have it.
- No trust store: whether a root is trusted by browsers or operating systems is not checked, so every result says "Public trust not checked". The certificate checker does that for a deployed site.
- No revocation: OCSP and CRLs are not queried.
- Private keys are refused, as are PKCS#12 (
.pfx,.p12) and PKCS#7 bundles. At most 20 certificates and 256 KiB at a time.
What happens to what you paste
The certificates you paste or add are sent to Ironfang's tools API to be ordered, and the answer comes straight back. They are not stored or logged, and they never go into the page's address or your browser's storage. Certificates are public, but private keys are not: the page refuses a private key in any form it can recognise before anything is sent.
Guides
A few things worth knowing
- What order should a certificate chain be in?
- Leaf first, then the intermediate that signed it, then the next one up, ending at the intermediate signed by the root. Most servers should not send the root itself. Some servers, such as nginx, take the leaf and intermediates in one file; others take them in separate settings.
- Why does the tool say "Issuer not supplied"?
- The top certificate in the path is not self-signed and none of the certificates you supplied signed it. That is normal for a chain that leaves the root out, so the file may be right; the tool simply cannot confirm the chain is complete. Find the issuer in your certificate authority's documentation if you need it.
- Why are names not enough to link two certificates?
- Anyone can make a certificate with any name. Only the issuer's private key can make a signature its public key verifies, so the tool links certificates by that check alone and reports a same-name certificate that did not sign as a bad signature.
- Is it safe to paste my certificates here?
- Certificates are public: a server sends them to every visitor. They are sent to Ironfang's tools API to be ordered, and are not stored or logged. Never paste a private key; the page refuses one before anything is sent.

