X.509 Certificate Parser
Decode a PEM or DER certificate to see subject, issuer, validity, key, SANs, key usage, OCSP and CRL URLs, and SHA-256 fingerprints, parsed in your browser.
The interactive tool loads here when JavaScript runs.
About this toolWhat is X.509 Certificate Parser?
The X.509 Certificate Parser decodes a certificate the way openssl x509 -text does, but in a readable layout. Paste a PEM block or upload a .pem, .crt, .cer or binary .der file and it shows the version, serial number, signature algorithm, subject and issuer names, validity dates with days remaining, public key type and size, and the common v3 extensions.
Extensions shown include Subject Alternative Names (DNS, IP, email and URI), Key Usage, Extended Key Usage, Basic Constraints, Subject and Authority Key Identifiers, Certificate Policies (with DV, OV and EV policy OIDs named), OCSP and CA Issuers URLs from Authority Information Access, and CRL Distribution Points. Every extension is also listed by name with its critical flag. SHA-256 and SHA-1 fingerprints are calculated with Web Crypto and match openssl x509 -fingerprint.
Parsing is done by a small DER decoder in the page, so the certificate is not uploaded. If you paste a chain, the first certificate is shown and the tool tells you how many it found. The parser reads fields; it does not verify the signature or check revocation.
- Real DER decoding of X.509 v1 to v3 certificates
- PEM paste, PEM file or binary DER upload
- SANs, key usage, EKU, basic constraints, AKI and SKI, policies, OCSP, CRL
- SHA-256 and SHA-1 fingerprints via Web Crypto
- Validity status with days remaining; nothing uploaded
Updated
How to use X.509 Certificate Parser
- Paste a PEM certificate into Certificate Input, or click Upload File and choose a .pem, .crt, .cer or .der file.
- Click Parse Certificate. Uploads and the Sample Certificate button parse straight away.
- Read Basic Information, Subject, Issuer and Validity Period, including the days left or days since expiry.
- Check the Extensions section for SANs, key usage and the URLs a client would use for OCSP and CRL checks, then copy the fingerprints if you need to compare or pin.
Worked example
The sample certificate
Input
Sample Certificate (www.example.com, issued by Example Test Root CA)
Output
Serial 0A:1B:2C:3D:4E:5F; RSA 2048, exponent 65537; ecdsa-with-SHA256; valid 2026-01-01 to 2027-01-01; SANs DNS:www.example.com, DNS:example.com, IP:192.0.2.10; SHA-256 DF:6E:7E:B2:54:7F:ED:B0:...:8E:EA
The key is RSA but the signature is ECDSA, because the issuing CA has an EC key. Key Usage is Digital Signature and Key Encipherment, Extended Key Usage is Server and Client Authentication, and Basic Constraints is CA:FALSE.
Background and insight
X.509 v3 certificates are defined in RFC 5280 and encoded in DER, a strict binary form of ASN.1. A PEM file is just that DER encoded in Base64 between -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines, which is why the same certificate can arrive as .pem, .crt or .cer with identical content, or as .der in raw binary.
Dates use two formats. UTCTime has a two-digit year, and RFC 5280 says years 50 to 99 mean 19xx and 00 to 49 mean 20xx; dates from 2050 onward must use GeneralizedTime. Both are shown in UTC here, with your local time next to them, which avoids the off-by-hours confusion of reading a certificate in a different timezone.
Fingerprints are hashes of the whole DER certificate, not of the key. Renewing a certificate with the same key gives a new fingerprint but the same Subject Key Identifier, which is useful when tracing certificate pinning problems.
Common use cases
Checking a certificate before installing it
Confirm the SANs, dates and key size of a newly issued certificate match the order you placed.
Debugging mutual TLS
Check that a client certificate has Client Authentication in its Extended Key Usage and the issuer the server expects.
Certificate pinning and inventory
Get SHA-256 fingerprints and key identifiers for pin lists or an asset inventory.
Reading certificates from other tools
Decode the x5c value of a JWK or a certificate embedded in SAML metadata after wrapping it in PEM lines.
Tips and limitations
- Paste only the BEGIN/END block. Text such as "subject=" lines from openssl output is ignored automatically.
- A certificate whose issuer equals its subject is self-issued: either a root CA or a self-signed test certificate.
- Browsers ignore the CN for hostname matching; what matters is the Subject Alternative Name list.
- To check a whole chain from a live server (order, missing intermediates, hostname), use the SSL Certificate Checker.
- Base64 inside a PEM block must be intact. A missing line or an extra character produces a DER length error rather than wrong fields.
Sources and further reading
- RFC 5280: Internet X.509 Public Key Infrastructure Certificate and CRL Profile, IETF. Fields, extensions and the UTCTime and GeneralizedTime rules
- RFC 7468: Textual Encodings of PKIX, PKCS, and CMS Structures, IETF. The PEM BEGIN and END format
- X.690: ASN.1 encoding rules (BER, CER and DER), International Telecommunication Union. The DER encoding certificates use
Frequently asked questions
How do I read the contents of a .crt or .pem certificate file?
Upload it with Upload File or paste its text into the input box. The parser decodes the DER inside and lists the subject, issuer, validity, public key, extensions and fingerprints, which is the same information openssl x509 -in cert.pem -noout -text prints.
What is the difference between PEM and DER certificate files?
DER is the binary encoding of the certificate; PEM is the same bytes in Base64 with BEGIN and END lines. The extension (.crt, .cer, .pem) does not tell you which one you have. This parser accepts both and converts uploaded DER files to PEM text.
Why is the SHA-1 fingerprint still shown if SHA-1 is broken?
Because some systems still identify certificates by SHA-1 thumbprint, including the Windows certificate store and older pinning configs. A fingerprint is only used to look a certificate up, so it is less exposed than a SHA-1 signature, but SHA-256 is the better choice for anything new.
What does Basic Constraints CA:TRUE mean?
It marks the certificate as a certificate authority that may sign other certificates. Server and client certificates should have CA:FALSE. An optional path length limits how many intermediate CAs may follow it in a chain.
Can this parser tell me if a certificate is revoked?
No. It shows the OCSP responder and CRL Distribution Point URLs from the certificate, but it does not contact them. Use openssl ocsp or your platform's tooling to query revocation status.
Why does the certificate show a different date than my server logs?
Certificate times are stored in UTC. The parser shows the UTC timestamp first and your local time in brackets, so a certificate that expires at midnight UTC can appear to expire in the evening of the previous day in the Americas.
Is there an in-depth guide to X.509 Certificate Parser?
Yes. “How to Read an X.509 Certificate and Debug a TLS Chain” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.