THE TOOLBOX / PKI & TLS SECURITY
Decode X.509 certificates
and verify thumbprints.
Inspect PEM-encoded X.509 v3 certificates, ASN.1 Distinguished Names, validity windows, signature OIDs, and SHA-256 thumbprints locally in your browser.
THE DETAILS
RFC 5280 X.509 PKI structure, ASN.1 DER decoding, and OpenSSL equivalents.
1. Step-by-Step Workflow
Paste a Base64-armored -----BEGIN CERTIFICATE----- PEM block into the left editor—or click Load example. The ASN.1 parser immediately extracts the Subject and Issuer Distinguished Names, notBefore / notAfter UTC timestamps, hex serial number, signature algorithm, and SHA-256 thumbprint.
2. IETF RFC 5280 & ITU-T X.690 ASN.1 DER
Per IETF RFC 5280, an X.509 v3 certificate is an ASN.1 SEQUENCE containing three fields: tbsCertificate (to-be-signed certificate data), signatureAlgorithm, and signatureValue, encoded in binary Distinguished Encoding Rules (ITU-T X.690 DER) and wrapped in RFC 7468 PEM armor.
3. Cryptographic Thumbprint Verification
A certificate’s SHA-256 fingerprint is NOT stored inside the ASN.1 structure; it is the SHA-256 digest of the entire binary DER byte array computed via window.crypto.subtle.digest. Use it to verify mTLS client certificates, SAML IDP signing certs, and TLS pinning hashes.
4. Private PKI Inspection & Related Tools
Internal CA certificates, Kubernetes webhook certs, and staging TLS chains never leave your browser tab. Need to generate ECDSA/RSA keypairs, inspect JWTs, or calculate CIDR blocks? Try the Web Crypto playground, JWT decoder, and CIDR subnet calculator.
ASN.1 Object Identifiers (OIDs) & OpenSSL CLI Matrix
| X.509 Field / OID | ASN.1 OID / Meaning | OpenSSL CLI Command |
|---|
| Full Certificate Text | TBSCertificate + Signature | openssl x509 -in cert.pem -text -noout |
| Subject & Issuer DN | 2.5.4.3 (CN), 2.5.4.10 (O), 2.5.4.6 (C) | openssl x509 -in cert.pem -subject -issuer -noout |
| Validity Window | UTCTime (0x17) / GeneralizedTime (0x18) | openssl x509 -in cert.pem -dates -noout |
| SHA-256 Fingerprint | SHA-256 over binary DER bytes | openssl x509 -in cert.pem -fingerprint -sha256 -noout |
Common SSL/TLS Certificate Pitfalls
Leaf vs. Intermediate Certificate Order
In a fullchain PEM bundle (fullchain.pem), the server’s leaf certificate must appear first, followed by intermediate CA certificates in order up to the root.
UTCTime 2050 Rollover (RFC 5280)
ASN.1 UTCTime uses a 2-digit year (interpreted as 1950–2049), whereas certificates valid in or after 2050 must use 4-digit GeneralizedTime. Both tags are decoded automatically.
398-Day Maximum TLS Lifetime
Publicly trusted TLS certificates issued after September 2020 are capped at a maximum validity period of 398 days (and moving toward 47–90 days for automated ACME renewal).
Corrupted Base64 Line Breaks
Copying a certificate into an environment variable or JSON string without preserving PEM headers can strip required Base64 padding. Ensure both BEGIN and END lines are intact.
Frequently Asked Questions
Is it safe to decode internal mTLS or staging certificates in this tool?
Yes. All Base64 PEM de-armoring, ASN.1 DER sequence parsing, and SHA-256/SHA-1 thumbprint calculations run 100% locally in your browser. Zero certificates or internal domain names ever leave your device.
How do I compare a certificate’s SHA-256 fingerprint with OpenSSL?
Run openssl x509 -in cert.pem -noout -fingerprint -sha256 in your terminal. It hashes the binary DER bytes of the certificate and outputs the exact same colon-separated uppercase hexadecimal SHA-256 thumbprint shown in the right panel.
What is the difference between Subject CN and Subject Alternative Names (SAN)?
Historically, TLS clients matched the server hostname against the Subject Common Name (CN, OID 2.5.4.3). Under IETF RFC 6125 and CA/Browser Forum Baseline Requirements, modern browsers require hostnames and IP addresses to be listed in the Subject Alternative Name (SAN, OID 2.5.29.17) extension.
Does decoding an X.509 certificate verify its CA trust chain or OCSP revocation?
No. This tool decodes the ASN.1 DER structure and calculates cryptographic fingerprints locally without making network calls to OCSP responders, CRL distribution points, or operating-system root stores.
Why does my PEM file fail to parse if it contains a private key instead of a certificate?
An X.509 certificate PEM begins with -----BEGIN CERTIFICATE----- (RFC 7468), whereas a private key begins with -----BEGIN PRIVATE KEY-----. Paste only the certificate block when inspecting X.509 fields.