Certificate guides

Inspect issuer signatures in a supplied public certificate bundle

·

A certificate issuer name identifies a candidate signer. Checking the signature with that issuer’s public key establishes a stronger relationship than comparing names alone.

X.509 Certificate Inspector

Compare a leaf and issuer together

Load the leaf alone and note its issuer name. Add the issuer certificate to the PEM bundle and inspect again. A matching issuer public key can verify the leaf signature. A different key under the same name will fail that signature check.

IETF RFC 5280 — Internet X.509 Public Key Infrastructure Certificate ProfileIETF RFC 7468 — Textual Encodings of PKIX Structures

Read a local signature result in context

The inspector checks signature links and the recorded CA authorization when applicable. Compare certificate validity separately. A supplied self-signed certificate can verify its own signature without being trusted by any operating system.

IETF RFC 5280 — Internet X.509 Public Key Infrastructure Certificate Profile

Investigate two issuers with the same displayed name

An issuer name can match more than one saved certificate after a key rollover. Inspect the actual signature result with the supplied candidate keys. Matching distinguished names alone cannot show which key signed the leaf.

Record the fingerprint of the candidate used for a successful signature check. Evaluate trust anchors, usage and revocation in the application that makes the trust decision.

Common questions

Does the order of a PEM bundle matter?

Results retain input order. For each certificate the inspector searches all supplied certificates for a matching issuer, independent of its position.

Are revocation and public trust checked?

This reader reports the supplied certificate data. It has no live revocation observations or operating-system trust decisions.

Sources

Put it into practice.

Related guides