Web and SSL Certificates · #65
Online PEM Certificate Decoder
Decodes the PEM certificate you paste in your browser only; it does not connect to any server.
- Data is processed in your browser and not sent to a server
Tool
What does this tool do?
Checking that a new certificate has the right names (SAN), a sufficient key and correct chain order before installation is far easier than debugging afterwards. The tool decodes each certificate in the PEM text, lists warnings per certificate and checks chain order. No live TLS connection is made; the chain is not validated against a root store.
How to use it
- Paste the certificate (and intermediates) as
-----BEGIN CERTIFICATE-----blocks; the leaf certificate first. - Optionally enter the host name it will be used for; press Run.
Fields
- PEM certificate(s)
- Do not paste private keys; they are ignored.
- Host name (optional)
- For the SAN match check.
Worked example
| Input | Value |
|---|---|
| PEM certificate(s) | |
| Host name (optional) | www.example.com |
Expected result: Leaf certificate www.example.com (EC P-256, ecdsa-with-SHA256, SAN: www.example.com and example.com, 1 June 2026 – 30 June 2027) followed by its issuer Ornek Test CA; chain order is correct and the host name matches.
The sample certificates are test certificates created for this page. In a real chain 'self-signed' should appear only on the root CA; the days remaining are calculated from the day you run the tool.
Second scenario
| Input | Value |
|---|---|
| PEM certificate(s) | |
| Host name (optional) | intranet.example.local |
Expected result: intranet.example.local: RSA 1024 bit, sha1WithRSAEncryption, no SAN, self-signed and expired on 1 January 2024; the name matches only the CN, so browsers reject it.
Method and assumptions
PEM blocks are decoded from Base64 to DER and the ASN.1 structure is read (version, serial, signature algorithm, issuer, validity, subject, public key, SAN/EKU/basicConstraints extensions). The fingerprint is SHA-256 over DER.
Chain: each certificate's issuer must be the next certificate's subject. Name matching follows RFC 6125 using SAN; a wildcard covers only the leftmost label.
Using the result and troubleshooting
Red findings (expired, SHA-1, RSA below 2048 bits, name mismatch) must be fixed before going live. Add the renewal date to the Certificate Inventory tool.
Limits and common mistakes
- Revocation (CRL/OCSP) and trusted root validation are not performed; this tool cannot see which certificate a server actually presents.
Frequently asked questions
Why doesn't it fetch the certificate from my site?
This version deliberately opens no connection to any target. Copy the certificate from the browser's padlock or from openssl s_client -showcerts output.
Related tools and service
- Certificate Inventory and Renewal CalendarSorts certificate expiry dates, marks the renewal window and creates a calendar file.
- CSR DecoderChecks the names and key inside a CSR before you send it to a provider.
- Certificate Fingerprint and File HashCalculates hashes of a file, text or certificate on your device and compares them with an expected value.
Related service: Web Application Security and WAF