How to use
- 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. - Subject, issuer, expiry, SAN domains, key type and fingerprints appear immediately. Days remaining are computed from this browser’s current clock.
- 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.
- Type a name such as
www.example.cominto 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.comcovers one label such aswww.example.com, nota.b.example.comand notexample.comitself. - 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.