SSL Certificate Checker and Decoder
By MinniHost Guides Editorial Team Posted
This tool reads a certificate you paste. It decodes the X.509 structure (RFC 5280) in your browser and shows who it was issued to and by, the names it covers, when it starts and ends, how many days remain, the key type and size, and whether the pasted chain links together in order. It does not connect to any website, check revocation or trust stores, or verify signatures, so it cannot say that a live site's certificate is valid or trusted. Never paste a private key.
Paste a certificate
How the checker works
The page parses the certificate's ASN.1 DER encoding with a small hand-written reader and compares its fields with a few published rules. No library is loaded from the internet and no request is made.
days remaining = floor( (notAfter − now) ÷ 86 400 s ) validity length = ceil( (notAfter − notBefore) ÷ 86 400 s ) maximum length by issue date (BR 6.3.2): before 2026-03-15 398 d; to 2027-03-15 200 d; to 2029-03-15 100 d; after 47 d RSA key warning if modulus < 2048 bits (BR 6.1.5) hostname covered if a SAN dNSName equals it, or is "*.rest" and the name has exactly one label before "rest" (RFC 9525) chain link i → i+1 if issuer name of certificate i equals subject name of certificate i+1 (byte comparison of the DER Name)
- now
- your device clock
- issue date
- the certificate's notBefore date (an approximation)
Worked example
Given: a certificate with notBefore 2026-11-17 and notAfter 2027-02-15 (90 days); today is 2027-01-15, at the same time of day.
- Days remaining:
(2027-02-15 − 2027-01-15) = 31 days - Cap for issue date 2026-11-17 (on or after 2026-03-15, before 2027-03-15):
200 days
Answer: 31 days remain and the 90-day lifetime is under the 200-day cap, so there is no validity warning.
| Issued | Maximum validity |
|---|---|
| Before 2026-03-15 | 398 days |
| 2026-03-15 to before 2027-03-15 | 200 days |
| 2027-03-15 to before 2029-03-15 | 100 days |
| 2029-03-15 onward | 47 days |
Source 2. Check the current version of the Baseline Requirements before relying on these dates.
Assumptions and limits
- The tool does not verify signatures, revocation (CRL/OCSP), Certificate Transparency or trust anchors, and gives no grade or score.
- Warnings are hints. Private CAs and internal certificates may legitimately differ from public rules.
- Dates use your device clock and are shown in UTC.
- Unusual encodings may fail to parse; the tool then says so instead of guessing.
Your questions answered
Is my certificate sent to a server?
No. The page runs entirely in your browser and makes no network request with what you paste. Certificates are public documents, but the tool treats them as private anyway.
Can I paste my private key?
Never. A private key is a secret; anyone who has it can impersonate your site. The tool refuses any text containing PRIVATE KEY and asks you to remove it. Treat any key you pasted anywhere as compromised and replace it.
Does it tell me whether my live site's certificate is valid?
No. It does not connect to your site, so it cannot see what your server actually sends. To check a live site, fetch the chain from the server (for example with OpenSSL, as described in our guides) and paste that.
Why does it say a certificate is expired when my site works?
The tool compares the dates with your device clock. If the certificate pasted is an old copy, or your clock is wrong, the answer differs from what the server serves now.
What does "chain order" mean?
A server should send its own (leaf) certificate first, then the intermediate that issued it, and so on. The tool checks that each certificate's issuer name matches the next certificate's subject name. It does not verify the signatures, so a match is a hint, not proof.
Why is there a validity-length warning?
The Baseline Requirements cap how long publicly trusted TLS certificates may last, by issue date. The warning appears when the certificate's notBefore date and lifetime exceed the cap for that date. It does not apply to private CAs, and the notBefore date is used as the issue date.
Which formats work?
PEM text (-----BEGIN CERTIFICATE-----), one or several certificates, up to 10. DER files and PKCS#12 bundles must be converted to PEM first, for example with OpenSSL.
Where this comes from
- IETF RFC 5280, Internet X.509 Public Key Infrastructure Certificate and CRL Profile (rfc-editor.org) Certificate structure, names, validity, extensions.
- CA/Browser Forum, Baseline Requirements for TLS Server Certificates, v2.3.1 (4 Oct 2026): 6.3.2 validity periods and 6.1.5 key sizes (cabforum.org) Opened 2026-11-17.
- IETF RFC 9525, Service Identity in TLS (rfc-editor.org) Hostname matching and wildcard rules.
- IETF RFC 8446, The Transport Layer Security (TLS) Protocol Version 1.3, section 4.4.2 (rfc-editor.org) The sender's certificate comes first in the list; each following certificate should certify the one before it; a trust anchor may be omitted.