An X.509 certificate contains an identity, public key, validity period, issuer, and extensions encoded in ASN.1 DER. This decoder turns those fields into a readable table so you can investigate a TLS configuration, compare certificate files, or confirm which names and usages a certificate declares.
Decoding is inspection, not trust validation. The tool does not verify the signature, build a trusted chain, check revocation, or decide whether a certificate is valid for a hostname.
How to Use the X.509 Certificate Decoder
Paste a certificate, open a local file, or start with the included test certificate.
- Paste a PEM certificate or Base64 DER into PEM certificate.
- Alternatively, select Open a .pem, .crt or .cer file and choose a PEM or binary DER certificate file.
- Select Load a sample to restore the self-signed
shop.example.comexample. - Review Subject, Issuer, Validity, Public key, Signature algorithm, Serial number, Version, extension rows, SHA-256 fingerprint, and SHA-1 fingerprint.
- Read the status below the controls. It confirms the certificate was decoded, says how many were found in a bundle, and reminds you that the signature and chain are not verified.
PEM, DER, and the Structure of an X.509 Certificate
DER is the binary encoding used for the certificate structure. PEM wraps those DER bytes in Base64 between -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines. The same certificate can therefore appear as binary DER, a PEM block, or unarmored Base64 DER without changing its signed contents.
The text area accepts a PEM certificate or a sufficiently long Base64 DER value. The file picker reads both textual certificate files and binary DER; when a file begins with the expected ASN.1 sequence byte, the tool wraps its bytes as PEM before parsing. File extensions are useful hints, but they do not determine whether the contents are valid.
Certificate bundles need special care. The parser can find multiple PEM certificate blocks, but this page displays only the first and reports how many were present. It does not infer leaf, intermediate, or root roles from their order. Inspect bundle members separately when chain composition matters.
The decoder parses the outer certificate sequence, its to-be-signed fields, public-key information, signature algorithm identifier, and extensions. Unsupported ASN.1 shapes, lengths, or time encodings can produce an error rather than a partial result.
Reading Identity, Validity, Keys, and Extensions
Subject identifies the entity described by the certificate, while Issuer names the entity that issued it. The display renders distinguished-name attributes such as CN, O, OU, C, and recognized identifiers. Matching Subject and Issuer values are labeled self-signed, but that label is only a name comparison; the signature is not cryptographically checked.
Validity shows UTC ISO timestamps for Not before and Not after. The page compares them with the browser's current time and labels the certificate not yet valid, expired, or valid with a rounded count of days left. A warning style appears when fewer than 30 rounded days remain, but operational renewal thresholds should come from your deployment policy.
Public-key output includes the recognized algorithm and, where the parser can determine it, a bit size and elliptic-curve name. Recognized algorithms and curves include common RSA, EC, Ed25519, DSA, and related identifiers, but an unfamiliar object identifier may be shown numerically. The signature algorithm is a separate field: it describes how the issuer signed the certificate, not the subject public key itself.
Recognized extensions are decoded into readable values for subject and issuer alternative names, basic constraints, key usage, extended key usage, key identifiers, authority information access, CRL distribution points, and certificate policies. Other extensions remain visible by name or object identifier with their raw byte length. A critical label means software must understand and process that extension according to X.509 rules; this decoder does not enforce it.
Fingerprints, Hostnames, and Trust Validation
The SHA-256 and SHA-1 fingerprint rows are digests of the exact DER certificate bytes, calculated with the browser's Web Crypto API. A fingerprint can help compare a certificate with a value obtained through another trusted channel. It does not establish trust by itself, and it changes when any encoded part of the certificate changes.
SHA-1 is displayed for compatibility with systems that still present that fingerprint format. Do not confuse a SHA-1 fingerprint used as an identifier with a certificate's signature algorithm. The page may display an older signature algorithm such as sha1WithRSAEncryption, but it does not evaluate whether that algorithm is acceptable under a security policy.
For a TLS hostname, inspect Subject Alternative Name entries rather than relying only on the common name. Even a matching DNS name is insufficient on its own: a client also considers time, key usage, chain signatures, trust anchors, constraints, and possibly revocation information. This page performs none of those decisions.
Common Certificate Inspection Mistakes and Privacy
A frequent mistake is treating “decoded” or “valid” as “trusted.” Here, valid refers only to the browser time falling between the parsed dates. An attacker can create a self-signed certificate with plausible names and dates, and an expired certificate can still have a mathematically correct signature.
Another mistake is assuming a .crt or .cer suffix tells you the encoding. Those extensions may contain PEM or DER. If parsing fails, check whether the file is actually a certificate rather than a private key, certificate request, PKCS#7 bundle, or PKCS#12 archive. This parser is scoped to X.509 certificates and Base64 DER certificate data.
Parsing and fingerprint calculation run locally in the browser, and the selected certificate is not uploaded by this tool. Public certificates are commonly shared, but certificate files can still expose internal hostnames, email addresses, organization details, or infrastructure URLs. Review that metadata before posting results or screenshots.
Never paste a private key into a certificate field. A certificate contains a public key and is not secret in the same way, but the corresponding private key must remain protected. The decoder neither needs nor processes private-key material. For a token rather than a certificate, use the JWT decoder and apply its separate verification requirements.
Frequently Asked Questions
Does this decoder verify a certificate's signature or chain?
No. It parses and displays the first certificate and computes fingerprints, but it does not verify the signature, find issuers, build a chain, or consult a trust store. It also does not check revocation. Use a TLS or PKI validator configured for the intended trust environment.
Why does a certificate say valid but still fail in a browser?
The label only compares the current browser time with Not before and Not after. A browser can still reject the certificate for a hostname mismatch, unknown issuer, broken chain, invalid signature, unsuitable usage, constraints, revocation, or policy requirements. Inspecting dates is only one part of validation.
Can I decode a certificate chain or PEM bundle?
You can paste a bundle, but the page displays only its first certificate and reports the total number it found. It does not connect or reorder the certificates. Separate the PEM blocks and inspect each one when you need to understand the complete chain.
What is the difference between SHA-256 and SHA-1 fingerprints?
Both rows are digests of the complete DER bytes, formatted as colon-separated hexadecimal. SHA-256 is the stronger modern digest, while SHA-1 is included for comparison with older interfaces. A matching fingerprint is meaningful only when the expected value came through a channel you trust.
Does self-signed mean the certificate is unsafe?
Not necessarily, but it does not make the certificate trusted either. This tool labels a certificate self-signed when Subject and Issuer are identical; it does not verify the self-signature. Private systems may deliberately trust a self-signed root, while public clients generally require a chain to a configured trust anchor.
References: RFC 5280: Internet X.509 PKI Certificate Profile · MDN: Web Crypto digest().