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
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. Read each certificate: subject, issuer, names, validity with “expires in …”, key, signature and extensions. 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
-----BEGIN CERTIFICATE----- MIID2TCCA36gAwIBAgIJASNFZ4mrze8BMAoGCCqGSM49BAMCMEQxCzAJBgNVBAYT…
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
| Field | Meaning |
|---|---|
Subject | Who the certificate is for: CN (common name), O (organization), C (country)… |
Issuer | The certificate authority that signed it; the same as the subject on a root |
Names | Subject Alternative Names: the host names and IP addresses it is valid for |
Valid from / until | Outside these times clients reject it |
Key usages | Key usage and extended key usage: what the key may do, such as sign, encrypt, or act as a TLS server or client |
Basic constraints | Whether it is a certificate authority that may sign other certificates |
Fingerprint | A 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
The same check with OpenSSL
| To see | Command |
|---|---|
A certificate | openssl x509 -in cert.pem -noout -text |
A request (CSR) | openssl req -in request.csr -noout -text |
The SHA-256 fingerprint | openssl x509 -in cert.pem -noout -fingerprint -sha256 |
A DER file as PEM | openssl x509 -inform der -in cert.der -out cert.pem |
Certificates inside a .p7b | openssl 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.