Free Online Certificate, CSR, PEM and DER Decoder
Paste a certificate, a certificate request, a key or any DER in PEM, base64 or hex, and read what is inside it: subject and issuer, validity with the days remaining, subject alternative names, key usage, both fingerprints, and the full ASN.1 tree. Nothing is uploaded.
Enjoying WizTools123? Help keep our server infrastructure 100% free and open for everyone.
How to Use Certificate Decoder
Step by step, start to finish.
A PEM with its dashes, a bare base64 blob, or hex with or without spaces and colons. The page works out which, strips the envelope and reads the DER underneath.
The common name, the alternative names, the issuer, the dates and the days remaining, with a plain verdict on whether the certificate is currently valid.
SHA-256 and SHA-1 of the whole certificate, in the colon separated form openssl prints, so you can match what a server or a browser is showing you.
The ASN.1 view shows every tag, its length and its value, at the depth you choose. That is where an unexpected extension or a malformed field becomes visible.
Key Features
What this tool does, and what it does not do.
X.509 certificates and PKCS10 requests, with the subject, dates and extensions.
PEM, bare base64 or hex, and the structure identified from its own shape.
A plain verdict on whether it is valid now, and how long is left if it is.
Every DNS name, IP address, email and URI in the SAN extension, listed out.
Every tag, length and value at the depth you choose, for any DER at all.
SHA-256 and SHA-1 of the whole certificate, in the form openssl prints.
About Certificate Decoder
A certificate is a signed statement: this public key belongs to this name, between these two dates, and here is who says so. All of that is stored as DER, a binary encoding of ASN.1, which is why you cannot read a certificate in a text editor and why a tool like this exists. The decoder here is written from the encoding rules rather than built on a library, because DER is genuinely simple once you see it as a tag, a length and a value repeated.
The page recognises four things, and it does not ask you which you have: an X.509 certificate, a PKCS10 certificate request, a public or private key, and anything else that happens to be valid DER. Recognition is by shape, not by the PEM label, so a certificate in a file marked as a key is still read as a certificate. Where the structure is one it knows, the fields are named and laid out. Where it is not, the ASN.1 tree still works, because walking tags needs no table at all.
The fields worth surfacing are not the ones an ASN.1 dump puts first. People open a certificate to find out when it expires, which names it covers, who issued it, and whether the fingerprint matches what something else is showing them. So the summary view leads with those, including the days remaining counted against your own clock, and the full view and the tree are there underneath for when the question is stranger than that.
What the page does not do is validate. It will not check the signature against an issuer, build a chain, consult a revocation list or ask an OCSP responder, and it has no trust store to check against. Decoding tells you what a certificate claims; only a client with a set of trusted roots can tell you whether those claims should be believed. A self-signed certificate for any domain in the world will decode here without complaint, and saying so plainly is more useful than a reassuring tick.
Frequently Asked Questions
Common questions about this tool.