Certificate Decoder
Paste a PEM certificate or key block.
About this tool
The fingerprint covers the decoded body of the block.
This is not a full X.509 path check. Subject and issuer names are not reconstructed beyond the PEM label.
How to use it
- Open this page and provide the input it asks for.
- Set the options that are visible, then use Read certificate.
- Read the result in the panel. Copy it or download it when a file is offered. The input stays in this browser.
Limitations
- This is not a full X.509 path check. Subject and issuer names are not reconstructed beyond the PEM label.
PEM label, length, and a SHA-256 fingerprint
What is read
The page looks for a PEM armor block: a BEGIN line with a label, a body, and an END line. The label is captured and printed. The body is stripped of whitespace and decoded as base64 into bytes. Those bytes are hashed with SHA-256, and the digest is printed as colon-separated lowercase hex octets, along with the byte count. The status of the parse is that the page covered the wrapper and the fingerprint. It does not claim to understand the ASN.1 inside.
The body is base64, which is an encoding. The fingerprint is a hash of the decoded bytes. Neither one is a signature check on the certificate, and neither one is encryption. Anyone with the same PEM computes the same fingerprint. That is useful for comparing two pastes, or for comparing against a fingerprint you received on a trusted channel. It does not build trust by itself.
What is not validated
There is no path builder, no trust anchor, and no check of the signature inside the certificate. Not-before and not-after are not read. Subject and issuer names are not decoded. Key usage, SANs, and basic constraints are not listed. A PEM that is a private key, or a certificate request, or a bare public key, still matches the armor pattern if the BEGIN and END lines are there. You will get a label, a length, and a fingerprint of those bytes, not a statement that the block is a certificate or that it is safe to install. An untrusted chain does not become trusted because the fingerprint printed.
How bad input fails
If the BEGIN and END pattern does not match, the page asks you to paste a PEM block. It does not try to parse DER that lacks armor. Bad base64 in the body throws from the decoder. The hash is over the decoded body bytes, not over the armor text, so a change in line wrapping inside the body does not change the fingerprint, and a change in the label does not change it either. A change in the decoded bytes does. This is the wrong page for a full TLS inspection, and it is the wrong page for hiding a key. A private key pasted here is still a private key, now with a hash beside it.
Privacy
Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.

