// admin tools · 23
Certificate decoder
Paste a PEM certificate, a whole chain or a CSR — or drop a .crt, .der or .p7b — and read subject, SANs, expiry, key, extensions and fingerprints, with chain order and signatures checked.
// decoding runs locally — nothing is uploaded · --fetch asks our server to open the TLS connection
Sends the hostname and port to likeapro.dev/tools/fetch.php, which opens a TLS connection and returns the certificates the server presents. Private and internal addresses are refused. Nothing is stored.
How it works
What it does
This decoder reads X.509 certificates, PKCS#10 certificate signing requests and PKCS#7 bundles with a DER/ASN.1 parser written from scratch — no libraries, and nothing is uploaded. It shows the subject and issuer, every Subject Alternative Name, the validity window with days remaining, serial number, key type and size, signature algorithm and each extension in plain language. SHA-256 and SHA-1 fingerprints and an SPKI pin are computed with WebCrypto.
How to use it
- Paste one or more
-----BEGIN CERTIFICATE-----blocks, a CSR, or drop a binary.der/.ceror.p7bfile. - Paste a full chain, leaf first, to check that each certificate is issued by the next. The tool compares issuer and subject names and key identifiers, then verifies each signature with the next certificate's public key.
- Open ASN.1 tree to see the raw structure with byte offsets — handy when a tool rejects a certificate and you need to know why.
- --fetch pulls the chain a live server presents, which is the quickest way to spot a missing intermediate.
What the fields mean
- SAN
- The hostnames and IPs the certificate is valid for. Browsers ignore the Common Name and match only these.
- Key Usage / EKU
- What the key may do. TLS servers need
serverAuth; CAs needkeyCertSign. - Basic Constraints
CA:TRUEmarks an issuing CA;pathlenlimits how many CAs may sit beneath it.- AKI / SKI
- Key identifiers that link a certificate to the key that signed it — the most reliable way to match chain links.
- AIA
- Where to download the issuer certificate and the OCSP responder used for revocation checks.
- SCTs
- Signed Certificate Timestamps prove the certificate was logged in Certificate Transparency. Chrome and Safari require them.
- Policies
- CA/Browser Forum OIDs show the validation level: DV, OV or EV.
FAQ
Is it safe to paste a certificate here?
Yes. Certificates and CSRs are public by design, and decoding happens in your browser. If you paste a private key by mistake, the tool refuses to read it — treat that key as exposed anyway if it was ever shared.
Why does my chain show "out of order"?
TLS servers must send the leaf certificate first, then each intermediate up towards the root. Concatenate your files in that order (for nginx, cat leaf.crt intermediate.crt > fullchain.pem). Sending the root is optional.
What does the SPKI pin mean?
It is the base64 SHA-256 of the public key structure, the format used by certificate pinning in mobile apps and by curl --pinnedpubkey. It stays the same when you renew with the same key.
What does --fetch send?
Only the hostname and port, to our fetch.php endpoint on likeapro.dev. It returns the presented chain, protocol and cipher; the certificates are then decoded in your browser.