CSR Decoder & Inspector
Decode PKCS#10 CSRs, check SANs and signature, and compare with the issued certificate
CSR input
Paste a PEM block that starts with BEGIN CERTIFICATE REQUEST. DER .csr, .der and .req files are converted when uploaded.
Never paste a private key. The CSR and the issued certificate are all this tool needs.
Summary
Details
Related Tools
What the decoder shows
Paste a PEM certificate signing request (BEGIN CERTIFICATE REQUEST or the legacy BEGIN NEW CERTIFICATE REQUEST) or upload a DER .csr, .der or .req file. The decoder shows every subject attribute including emailAddress and unknown OIDs, the public key algorithm, size or curve with SPKI SHA-256 and SHA-1 fingerprints and the public key PEM, requested extensions (Subject Alternative Names grouped by DNS, IP, email and URI, key usage, extended key usage, basic constraints and others as raw values), attributes such as challengePassword (masked) and unstructuredName, and the signature algorithm.
Findings and signature check
Findings flag RSA keys under 2048 bits, SHA-1 or MD5 signatures, a missing SAN, a Common Name that is not in the SANs, wildcard and IP address SANs, unknown critical extensions and an invalid signature. The signature is verified with Web Crypto against the embedded public key: a valid result proves the request was signed by the matching private key, not that a CA will trust or issue it.
Compare a CSR with the issued certificate
Switch to Compare with certificate and paste the certificate your CA returned. The comparison checks that the public keys match by SPKI hash, compares subject attributes, key type and size, lists each requested SAN as issued or missing and SANs the CA added, and compares requested key usage, extended key usage, basic constraints and other extensions with the issued ones.
Privacy
Decoding, signature verification and comparison run locally in your browser. CSRs and certificates are not uploaded, stored or added to the URL. The tool never asks for a private key; if one is pasted, nothing is decoded and the key is not displayed.
Frequently asked questions
- Is my CSR uploaded anywhere?
- No. The CSR and the issued certificate are decoded and checked in your browser with Web Crypto. Nothing is sent to CodingTool servers, stored or added to the URL, and the tool never asks for the private key.
- What does a valid CSR signature mean?
- It means the request was signed by the private key that belongs to the public key inside it, so whoever created the CSR holds that key and the content was not altered. It does not mean a certificate authority trusts or will issue it.
- How do I check that a certificate was issued for my CSR?
- Switch to Compare with certificate and paste the certificate from your CA. The public keys must match by SPKI hash; the comparison also lists each requested SAN as issued or missing, SANs the CA added, and differences in subject attributes and extensions.
