Certificate analyser

Validate an X.509 trust chain

Supply a Root CA, any number of Intermediate CAs, and the server certificate. Validation runs locally in your browser.

Local onlyNo uploads or telemetry
Trust model: this tool can validate a path against the Root CA you supply. It cannot inspect the operating-system or browser trust store from a normal GitHub Pages application.

Guided chain

Certificates

Trust-path order: Root → Intermediate(s) → Server
1

Root CA

Required

Paste the PEM trust anchor. Multiple Root CA certificates are accepted for alternative-path testing.

No fixed chain depth is assumed. One intermediate is shown by default because it is the common case.
3

Server Certificate

Required

The end-entity/leaf certificate presented by your TLS service.

Identity check

Hostname / SAN

Checks DNS/IP Subject Alternative Names. Common Name fallback is reported only as legacy behaviour.

Deployment check

Existing server bundle

Paste an existing fullchain.pem to check its order

The normal TLS bundle should contain the leaf first, followed by intermediates. The Root CA is normally omitted.