Skip to main content
WizTools123
Free Online Tools

Tool Categories


Security Tools New Tool

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.

Free Forever Nothing Uploaded Certificates And CSRs Nothing Uploaded
Free Online Certificate, CSR, PEM and DER Decoder
Share this tool
Advertisement Slot (Top Banner) Google AdSense Unit • Responsive Banner
Certificate Decoder Everything happens in this tab. Nothing you paste is sent anywhere.
Your certificate
What is inside it
Show

Buy Us A Coffee

Enjoying WizTools123? Help keep our server infrastructure 100% free and open for everyone.

Buy Us A Coffee
Sponsored Content (Below Tool) Google AdSense Placement

How to Use Certificate Decoder

Step by step, start to finish.

1
Paste whatever you have

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.

2
Read the summary

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.

3
Compare the fingerprints

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.

4
Drop into the tree when something is odd

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.

Certificates and CSRs

X.509 certificates and PKCS10 requests, with the subject, dates and extensions.

Format detected

PEM, bare base64 or hex, and the structure identified from its own shape.

Expiry in days

A plain verdict on whether it is valid now, and how long is left if it is.

Alternative names

Every DNS name, IP address, email and URI in the SAN extension, listed out.

The ASN.1 tree

Every tag, length and value at the depth you choose, for any DER at all.

Both fingerprints

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.

No. It decodes what the certificate says about itself: names, dates, extensions, fingerprints. Checking the signature against an issuer, building a chain to a trusted root and looking at revocation all need a trust store and network access, neither of which a page like this has. For trust, use a browser or openssl verify.

A PEM with the BEGIN and END lines, a bare base64 blob with no envelope, or hex with or without spaces, colons or a 0x prefix. The page strips whatever wrapper it finds and reads the DER underneath, so a certificate copied out of a config file or a log usually works as it is.

Check which certificate you are looking at. A browser shows the fingerprint of the leaf certificate it was served, and a PEM file often holds the whole chain, in which case this page decodes the first one in the file. Also check you are comparing the same hash: SHA-256 and SHA-1 are both shown here.

Yes. A PKCS10 request decodes with its subject, its public key and any extensions it asks for, which is usually the subject alternative names. That is the usual way to check that a CSR actually contains the names you meant before you send it to a certificate authority.

No. The DER parsing is done in the page and the fingerprints are hashed by the browser own cryptography, with no request made. There is also no history and no saved setup here, so nothing is written to browser storage either.
Advertisement Slot (Bottom Banner) Google AdSense Unit • Responsive Banner