What does this PEM & CSR decoder inspect?
This tool decodes PEM-armored Base64 Certificate Signing Requests (CSRs) and X.509 certificate blocks locally using atob() and the browser Web Crypto API (crypto.subtle.digest('SHA-256')). It reports each block label, exact DER byte length, uppercase colon-delimited SHA-256 fingerprint, and up to 25 readable ASCII strings (such as Common Name and SAN domains) with zero server uploads.
How to decode a PEM or CSR file online
- Paste PEM text or upload a .csr / .pem file. Paste one or more -----BEGIN ...----- blocks into the editor or choose a .pem, .csr, .crt, or .cer file from disk.
- Click Decode PEM / CSR. Your browser decodes each Base64 armor block into raw DER bytes and hashes them with Web Crypto SHA-256.
- Inspect or export the JSON output. Review block types, DER byte sizes, SHA-256 fingerprints, and extracted ASCII strings, then copy or download pem-decoded.json.
What details are output per PEM block
- PEM Block Type: Label extracted from
-----BEGIN <LABEL>-----(such asCERTIFICATE REQUESTorCERTIFICATE). - DER Byte Length: Exact binary length of the decoded ASN.1 DER payload.
- SHA-256 Fingerprint: Colon-separated hex digest computed via
crypto.subtle.digest. - Extracted ASCII Strings: Up to 25 unique printable subject, issuer, OCSP, and SAN strings.
Supported PEM inputs and chain handling
Inputs: Multi-block PEM bundles (.pem, .csr, .crt, .cer) containing matching BEGIN and END headers.
Outputs: Formatted JSON array with one object per PEM block.
Why CSRs and private PEM files stay local
Certificate chains and internal hostnames reveal infrastructure topology, and accidentally pasted private keys must never reach a third-party server. EasyExtract performs Base64 decoding and SHA-256 hashing solely inside local browser RAM.
What this tool does not do
- It does not parse full ASN.1 OID trees: For full X.509 Issuer, Subject, Valid-From/To dates, and SAN extension parsing, use our dedicated SSL certificate parser.
- It does not verify CA signatures or private keys: Signature chain validation against root stores requires OpenSSL or your OS trust store.
When to use the PEM & CSR decoder
- Verifying CSR fingerprints: Confirm a certificate request SHA-256 matches your issued certificate or build log.
- Checking multi-cert PEM chains: Count how many PEM blocks are bundled in a
fullchain.pemfile before deploying to Nginx or Apache.
PEM & CSR Decoder compared with SSL Certificate Parser
Use this decoder when you need DER byte counts, SHA-256 fingerprints, and block counts across CSRs and PEM bundles. For full X.509 certificate expiration dates and SAN lists, use our SSL certificate parser, or read OpenSSL read PEM certificate and view PEM files online.
Frequently asked questions
Is it safe to paste my CSR or certificate here?
Yes. Everything runs 100% locally in your browser using Web Crypto API with zero data transmitted.
Can it decode multiple PEM blocks at once?
Yes. Paste a full certificate chain and it decodes each PEM block into its own JSON entry.
What happens if a PEM block has invalid Base64?
The decoder catches malformed Base64 characters and displays a clear warning instead of failing silently.