Skip to content
Sealpaste

Delete all recent work?

This removes the 0 items saved in this browser. Your settings stay.

Stop saving recent work?

New work won't be saved in this browser. The 0 items already saved can stay or go.

SSL Certificate Decoder

Certificate

Paste a certificate to decode it

Decoded
Ready
Runs in your browser. Nothing you paste is uploaded unless you share it.

Decode an SSL/TLS certificate or chain: subject, issuer, SANs, expiry, key, extensions and SHA-256 fingerprints

Paste a certificate, a chain or a CSR to see who it is for, the names it covers, when it expires, its key and its fingerprints. PEM, Base64 and hex DER all work.

How to use it

  1. Paste one or more PEM blocks (from -----BEGIN CERTIFICATE----- to the END line), or DER as Base64 or hex, or open a .pem, .crt, .cer or .der file.
  2. Read each certificate: subject, issuer, names, validity with “expires in …”, key, signature and extensions.
  3. In a chain, each certificate says whether the next one issued it; copy a fingerprint or the public key pin with its button.

Example

Read a server certificate

Input
-----BEGIN CERTIFICATE-----
MIID2TCCA36gAwIBAgIJASNFZ4mrze8BMAoGCCqGSM49BAMCMEQxCzAJBgNVBAYT…
Result
Subject: C=US, ST=California, L=San Francisco, O=Example Inc, CN=example.com
Names: DNS: example.com, DNS: www.example.com, IP: 192.0.2.1, IP: 2001:db8::1
Public key: RSA, 2,048 bits

The page’s sample: a test certificate for example.com and the test root that issued it.

What each field means

Browsers check the names in Subject Alternative Names, not the common name, so a certificate that is missing a host name there fails for that host even when the CN matches.

FieldMeaning
SubjectWho the certificate is for: CN (common name), O (organization), C (country)…
IssuerThe certificate authority that signed it; the same as the subject on a root
NamesSubject Alternative Names: the host names and IP addresses it is valid for
Valid from / untilOutside these times clients reject it
Key usagesKey usage and extended key usage: what the key may do, such as sign, encrypt, or act as a TLS server or client
Basic constraintsWhether it is a certificate authority that may sign other certificates
FingerprintA hash of the whole certificate, to tell two copies apart or match a pinned one

Sources: RFC 5280 §4.1, §4.2

Chains, bundles and DER

A server sends its own certificate first, then the intermediates up to a root. Paste the whole bundle and each certificate is read in order. Each link is checked by its signature: the certificate’s signature against the next one’s public key (RSA, RSA-PSS, ECDSA on P-256, P-384 and P-521, and Ed25519 where the browser has it; other algorithms fall back to key identifiers and names).

A Chain section above the certificates says what is off: the server’s certificate isn’t first, a certificate is issued by one further down instead of the next, an intermediate is missing, a certificate belongs to no chain here, or a name matches but the signature doesn’t. It also says where the chain ends. Trust stores and revocation aren’t checked: they need the server connection or the CA.

Under each certificate, ASN.1 structure opens the raw DER as a tree, with each element’s byte offset, header and length, and object identifiers named, as openssl asn1parse prints it.

DER is the same certificate as binary. Paste it as Base64 without the BEGIN/END lines, or as hex from a dump. A .p7b (PKCS #7) bundle is named, with the OpenSSL command that prints the certificates inside.

The same check with OpenSSL

On a machine with OpenSSL, these commands print what this page shows. The page also reads a whole chain at once and works where OpenSSL isn’t installed.

To seeCommand
A certificateopenssl x509 -in cert.pem -noout -text
A request (CSR)openssl req -in request.csr -noout -text
The SHA-256 fingerprintopenssl x509 -in cert.pem -noout -fingerprint -sha256
A DER file as PEMopenssl x509 -inform der -in cert.der -out cert.pem
Certificates inside a .p7bopenssl pkcs7 -in bundle.p7b -print_certs

Sources: OpenSSL x509 manual

Questions

Is the certificate uploaded?
No. Everything runs in your browser, so your certificates stay on your device. Nothing you paste is uploaded unless you share a result, which is locked with your password first. Certificates are public, but bundles often sit next to private keys and internal host names.
What is the difference between a certificate and a CSR?
A CSR (certificate signing request) is what you send a certificate authority: your names and public key, signed by your private key. The certificate is what the authority sends back: the same names and key, with its signature, an issuer and validity dates.
Does it check that the certificate is trusted?
Not fully. It checks each signature against the next certificate in what you paste, so a chain that is out of order, missing a link or altered shows up. Whether a browser trusts it also depends on a root in its own store and on revocation, which need the server connection or the CA.
Which fingerprint should I compare?
SHA-256, as browsers show it in the certificate viewer. SHA-1 fingerprints are still shown by older tools. The public key pin (pin-sha256) is the Base64 SHA-256 of the public key, which stays the same when a certificate is renewed with the same key.
Why does it say “weak”?
An RSA key under 2,048 bits, a DSA key or an uncommon curve, or a signature with SHA-1 or MD5. Certificate authorities no longer issue either for the public web, and browsers reject SHA-1 certificates.
Can I paste a private key here?
The page names a private key block when it finds one and doesn’t read it. A private key never needs to leave the server it belongs to, so keep it out of chats, tickets and websites.

Related tools