1. Home
  2. Developer
  3. SSL Certificate Viewer

SSL Certificate Viewer

Decode a PEM certificate: expiry, domains, key info and chain order.

Runs in your browser · No upload
Paste several certificates in a row to read a chain. A bare base64 block without the BEGIN line works too.

Certificates are public data, but what you paste is still parsed only in this browser and never sent to a server. You do not need to paste a private key (PRIVATE KEY) here.

Chain order looks right: each certificate is issued by the next one in the list.

1. leaf.example.test | End-entity certificate

Subject
C=KR, O=Toolulah Test, CN=leaf.example.test
Issuer
C=KR, O=Toolulah Test, CN=Test Intermediate CA
Serial number
4c:19:e1:87:85:3e:b2:83:56:2f:9b:3a:b6:2a:fa:2f:f9:0a:79:a4
Version
v3
Not before
2026-10-18 02:51:48 UTC
Not after
2036-10-15 02:51:48 UTC
Validity period
Signature algorithm
ecdsa-with-SHA256
Public key
EC, curve prime256v1 (P-256)
Subject Alternative Names
DNS: leaf.example.test
DNS: www.leaf.example.test
Basic constraints
Not a CA (end-entity)
Key usage
digitalSignature
Extended key usage
serverAuth
Subject key ID
A5:7B:C8:52:48:08:8C:72:98:80:5A:C3:FB:E9:0E:6B:DF:E7:0D:CE
Authority key ID
9D:8E:53:89:00:EB:24:8D:15:F7:33:C8:CE:C0:BD:DC:A5:4F:04:43
SHA-256 fingerprint
E3:2E:3F:F5:57:A0:78:7B:AD:50:C7:EF:5B:39:35:C4:ED:13:D2:19:16:1F:62:CB:BE:06:C9:22:74:81:31:DB
SHA-1 fingerprint
C7:3D:D6:5D:1F:0C:5E:2B:CB:F4:AA:A0:19:5E:66:B7:F5:77:85:2B

2. Test Intermediate CA | CA certificate

Subject
C=KR, O=Toolulah Test, CN=Test Intermediate CA
Issuer
C=KR, O=Toolulah Test, CN=Test Root CA
Serial number
6b:99:37:d4:f7:dd:a0:4a:1e:61:51:4b:d8:b8:18:c4:c0:9b:50:a8
Version
v3
Not before
2026-10-18 02:51:48 UTC
Not after
2040-06-26 02:51:48 UTC
Validity period
Signature algorithm
ecdsa-with-SHA384
Public key
EC, curve prime256v1 (P-256)
Basic constraints
CA certificate (max path length 0), critical
Key usage
keyCertSign, cRLSign
Subject key ID
9D:8E:53:89:00:EB:24:8D:15:F7:33:C8:CE:C0:BD:DC:A5:4F:04:43
Authority key ID
3E:5C:7F:C8:75:6F:03:82:95:38:5B:5E:4A:84:56:B9:51:7E:A8:88
SHA-256 fingerprint
26:94:D2:BC:07:65:05:AE:26:E5:C3:AB:26:F5:6E:24:D2:FB:8F:71:F2:E0:0D:41:24:F3:72:C1:FC:1A:07:27
SHA-1 fingerprint
5B:56:39:D0:14:21:BD:B7:92:9B:5B:CC:5B:95:2F:0D:9D:12:33:B1

3. Test Root CA | Self-signed (root)

Subject
C=KR, O=Toolulah Test, CN=Test Root CA
Issuer
C=KR, O=Toolulah Test, CN=Test Root CA
Serial number
25:8f:a9:a5:93:44:69:cb:a0:63:0a:9a:a9:df:0a:5d:e3:ce:cc:bd
Version
v3
Not before
2026-10-18 02:51:47 UTC
Not after
2046-10-13 02:51:47 UTC
Validity period
Signature algorithm
ecdsa-with-SHA256
Public key
EC, curve prime256v1 (P-256)
Basic constraints
CA certificate, critical
Key usage
keyCertSign, cRLSign
Subject key ID
3E:5C:7F:C8:75:6F:03:82:95:38:5B:5E:4A:84:56:B9:51:7E:A8:88
Authority key ID
3E:5C:7F:C8:75:6F:03:82:95:38:5B:5E:4A:84:56:B9:51:7E:A8:88
SHA-256 fingerprint
3D:FF:1B:E7:13:A3:EB:29:42:F5:51:32:72:A4:85:D1:E1:E5:96:5E:AF:E8:26:C1:89:33:98:3E:DA:F8:76:74
SHA-1 fingerprint
0B:9C:37:48:56:B8:1B:5B:A7:F1:C6:52:73:D5:77:82:84:D1:AB:E0

How to use

  1. Open your certificate file (.crt, .cer, .pem) in a text editor, copy everything from -----BEGIN CERTIFICATE----- to -----END CERTIFICATE-----, and paste it into the box. Clear the pre-filled sample first.
  2. Subject, issuer, expiry, SAN domains, key type and fingerprints appear immediately. Days remaining are computed from this browser’s current clock.
  3. Paste a server certificate followed by its intermediates and the tool reads them as a chain, checking that each certificate’s issuer matches the next certificate’s subject.
  4. Type a name such as www.example.com into the hostname check to see whether it matches the first certificate’s SAN list (or CN when there is no SAN).

What is shown

Field Meaning
Subject Who the certificate belongs to: usually CN (main domain), O (organization), C (country)
Issuer The CA that signed it. Same as the subject for a self-signed certificate
Validity Start and end time (UTC) and days left
SAN Domains, IPs, emails and URLs the certificate is valid for. Browsers check the hostname against the SAN
Key usage, extended key usage Allowed purposes such as signing, key encipherment, serverAuth, clientAuth
Basic constraints CA:TRUE means it can sign other certificates; path length limits how many intermediate CAs may follow
Subject and authority key IDs Identifiers that link a certificate to the one that issued it
SHA-256 and SHA-1 fingerprints Hash of the whole DER certificate, identical to openssl x509 -fingerprint output

Reading the sample

The pre-filled sample is a three-certificate chain issued by a throwaway test CA. The first (leaf.example.test) lists leaf.example.test and www.leaf.example.test in its SAN and is issued for serverAuth. The second, Test Intermediate CA, has CA:TRUE, pathlen:0, so it can only issue end-entity certificates. The third, Test Root CA, is a self-signed root whose issuer equals its subject. The leaf’s authority key ID equals the intermediate’s subject key ID, which is another way to confirm the link.

Common things to watch for

  • Expiry: browsers refuse an expired certificate. With fewer than 30 days left the status turns into a warning.
  • Missing SAN: a certificate with only a CN is not accepted for a hostname by current browsers.
  • Wildcards: *.example.com covers one label such as www.example.com, not a.b.example.com and not example.com itself.
  • SHA-1 or MD5 signatures and RSA under 2048 bits are flagged as weak.
  • Chain order: configure the server with the leaf first, then intermediates in order. The order check here compares names only and does not verify signatures.

Private key caution

A certificate is public information and safe to paste, but a private key (PRIVATE KEY) must never be shared. This tool never needs one: if a key block is mixed into the text it is ignored and you get a warning. Do not paste a production private key into any website; process it on your server with openssl. To check that a certificate and a key belong together, use the certificate and key matcher.

FAQ

How do I check when a certificate expires?

Paste the PEM and the “Not after” row shows the UTC time while the banner shows the days left. On the command line, openssl x509 -in cert.pem -noout -enddate gives the same value.

Can I look at the certificate a live site is using?

This tool only reads text you paste. Export the certificate from the browser’s padlock dialog, or open the .crt or .pem file from your server config, and paste it. It does not connect to any domain.

My .crt or .cer file looks like garbage. What now?

It is probably DER (binary). Convert it to PEM with the certificate converter, or paste the base64 text of the DER file directly, which is also accepted.

How do I read a file with several certificates?

Paste the whole fullchain.pem; each certificate is shown separately. To split the bundle into individual files, use the bundle split in the certificate converter.

What is a fingerprint used for?

It identifies one specific certificate: comparing two copies, pinning, or adding a certificate to a trust list. The SHA-256 value matches openssl x509 -fingerprint -sha256. For hashing arbitrary text or files, use the hash generator.

What you paste is processed only in your browser and never sent to a server.

Can't find the tool you need?

Tell us what you want to do. We build the most requested tools first.