X.509 Certificate Decoder for PEM Files

Paste a PEM certificate to read its subject, issuer, validity dates, Subject Alternative Names, key usage and fingerprints. Parsing uses the @peculiar/x509 library. Decoding shows what a certificate says about itself; it does not prove the certificate is trusted.

Runs in your browser: your files and text are not uploaded. Free, no account needed.

Last updated: · Reviewed by the QuickTooly Team

Reading the decoded fields

  • Subject and Issuer: distinguished names such as CN=example.com, O=Example Ltd, C=US. When both are the same, the certificate is self-signed: a root CA or a certificate made for testing.
  • Serial Number: hex number set by the issuing CA. Revocation lists and support requests refer to a certificate by issuer plus serial.
  • Valid From / Valid To: shown in UTC. Browsers reject the certificate outside this window.
  • Public Key Algo and Signature Algo: the type of key in the certificate (RSA or EC) and the algorithm the issuer used to sign it.
  • SHA-256 and SHA-1 Fingerprint: hashes of the whole certificate, in colon-separated hex. Use them to confirm two copies are the same certificate or to pin it. They are not stored inside the certificate.
  • Subject Alternative Names: the host names and IP addresses the certificate covers, each prefixed with its type, for example dns: www.example.com. Browsers match the host name against this list, not against the CN.
  • Key Usage and Extended Key Usage: what the key may do. "Certificate Signing" marks a CA certificate. A normal website certificate has "TLS Web Server Authentication". OIDs the tool does not know are shown as raw numbers.

What the date badge does not check

The badge says Not yet valid before the Valid From date, Expired after the Valid To date, and Valid (dates only) in between. It checks only those two dates. It does not check:

  • whether a trusted CA signed the certificate (the chain is not built or verified)
  • whether the certificate has been revoked
  • whether the host name you care about is in the SAN list

A self-signed or forged certificate within its dates still shows Valid (dates only). To test what a live server presents, including the chain, use a TLS checker or openssl s_client -connect example.com:443 -servername example.com.

Frequently Asked Questions

I pasted a full chain but only one certificate is shown. Why?

The tool decodes only the first certificate in the text. To inspect the intermediate or root, paste each BEGIN CERTIFICATE ... END CERTIFICATE block on its own.

Why do I get "Invalid certificate"?

The text is not an X.509 certificate. A private key (BEGIN PRIVATE KEY), a certificate signing request (BEGIN CERTIFICATE REQUEST) or a PKCS#12 file all fail. Text without the BEGIN/END lines is accepted when it is the certificate in Base64 or hex.

How do I get the certificate of a website?

Click the padlock in your browser and export the certificate as PEM, or run openssl s_client with -showcerts and copy the BEGIN CERTIFICATE block.

Related Tools

  • SSL Checker - connects to a live host and checks the certificate it serves, which this decoder does not.
  • File Hash Calculator - hash a downloaded .crt or .pem file to compare it with a published checksum.
  • DNS Lookup - check that the names in the SAN list resolve to the server you expect.