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

Do not paste private keys; they are ignored.

For the SAN match check.

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

  1. Paste the certificate (and intermediates) as -----BEGIN CERTIFICATE----- blocks; the leaf certificate first.
  2. 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

InputValue
PEM certificate(s)
-----BEGIN CERTIFICATE-----
MIIBlDCCATmgAwIBAgIFBKGyw9QwCgYIKoZIzj0EAwIwODELMAkGA1UEBhMCVFIx
ETAPBgNVBAoMCE9ybmVrIEFTMRYwFAYDVQQDDA1Pcm5layBUZXN0IENBMB4XDTI2
MDYwMTAwMDAwMFoXDTI3MDYzMDAwMDAwMFowGjEYMBYGA1UEAwwPd3d3LmV4YW1w
bGUuY29tMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEK8NCS68dnBxUmm8rk+QL
81DwaczjsIxsPsfO+u7XorRbKjJ7qAm0iIBXTikCAFdaYj0JdAC8SJNAmCAjSAD7
k6NOMEwwJwYDVR0RBCAwHoIPd3d3LmV4YW1wbGUuY29tggtleGFtcGxlLmNvbTAT
BgNVHSUEDDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMAoGCCqGSM49BAMCA0kA
MEYCIQDCAHg9Y9nmD3zptt+TJboNIB17g7cO8IZJTOj397R1vgIhALeKsNm+q81S
hBblTgfJX/4IJ6UHpny34TjvoM789eA3
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIBdjCCARygAwIBAgICEAEwCgYIKoZIzj0EAwIwODELMAkGA1UEBhMCVFIxETAP
BgNVBAoMCE9ybmVrIEFTMRYwFAYDVQQDDA1Pcm5layBUZXN0IENBMB4XDTI1MDEw
MTAwMDAwMFoXDTM1MDEwMTAwMDAwMFowODELMAkGA1UEBhMCVFIxETAPBgNVBAoM
CE9ybmVrIEFTMRYwFAYDVQQDDA1Pcm5layBUZXN0IENBMFkwEwYHKoZIzj0CAQYI
KoZIzj0DAQcDQgAEcFEAM6lMBdReRDtTwkTnEMEigJYLiZvauL70LoB6sIYBP6dT
qy5LfDMfiu6VauST2nNTdU7ESpqa71l1JJbpgqMWMBQwEgYDVR0TAQH/BAgwBgEB
/wIBADAKBggqhkjOPQQDAgNIADBFAiBYFfvr8xjChjq8Fe7Jz+MtVFSld/oNu+t+
uZALGKa0ZgIhAMQtWRQIUCoy1YmxIm4FmBSw7BIzHdgVOKMJ6AWolKQY
-----END CERTIFICATE-----
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

InputValue
PEM certificate(s)
-----BEGIN CERTIFICATE-----
MIIBsTCCARoCAQcwDQYJKoZIhvcNAQEFBQAwITEfMB0GA1UEAwwWaW50cmFuZXQu
ZXhhbXBsZS5sb2NhbDAeFw0xOTAxMDEwMDAwMDBaFw0yNDAxMDEwMDAwMDBaMCEx
HzAdBgNVBAMMFmludHJhbmV0LmV4YW1wbGUubG9jYWwwgZ8wDQYJKoZIhvcNAQEB
BQADgY0AMIGJAoGBAKNmBAT4B0vYXYYmzfFyIWbygLTvzmpGEU1vP3G+BWgxgGJx
8wZQXtbdihPyI85ovkQD4KTa5Huu404MGszFIQeSGlUIbkM+K5kKoUMqItpn0KPw
GUf2iCHzbh/w/2KAI/RPQNGcXeq9BqS4fYA/7P4acR2E0HhcNGJuLKLXKgS9AgMB
AAEwDQYJKoZIhvcNAQEFBQADgYEATSjfkssPbUzxUf41PHcykO24B4XpIsnwKTs2
Qt0QVvL6Wb97fj1eenEpIq8cahSyq/4sr+wLcw6DWUo1qLtj0DZ2DmtC2PgztkeO
M/r9QFnD8wYyAA7m09aKgTLczWwQ9CEsqvds9l6EZvcEZi7z2PygtRbGlJGRtqk5
0SA0Bug=
-----END CERTIFICATE-----
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

Related service: Web Application Security and WAF

Web online tools · See all online tools