CSR (Certificate Signing Request) Decoder
Decode and inspect PEM-encoded Certificate Signing Requests (CSR) to verify Common Name, Organization, and SANs.
| Common Name (CN) | |
| Subject Alternative Names (SANs) | |
| Organization (O) | |
| Country (C) / Location | |
| Public Key Algorithm & Size |
1 How to Use the CSR (Certificate Signing Request) Decoder
Paste your CSR beginning with '-----BEGIN CERTIFICATE REQUEST-----' into the input box.
The parser extracts ASN.1 structures and decoded subject attributes.
Review Common Name (CN), Organization (O), Country (C), Key Size, and Subject Alternative Names (SANs).
Verify all details match your domain before submitting to your Certificate Authority (CA).
2 Technical Specifications
| Specification | Details & Capabilities |
|---|---|
| Format | PKCS #10 PEM formatted Certificate Signing Request |
| Attributes Parsed | CN, O, OU, L, ST, C, SANs, Public Key Algorithm, Bit Length |
| Engine | Client-side ASN.1 Parser |
| Privacy Guarantee | CSR processed entirely in browser memory |
Trust and Privacy
100% Client-Side Privacy Guarantee
All calculations run directly in your local browser memory. Zero data is ever transmitted, logged, or stored on remote servers.
4 Frequently Asked Questions
Q. Does a CSR contain my private key?
No! A CSR only contains your Public Key and identity details. Your private key stays securely on your server and should never be shared.
Q. What are SANs (Subject Alternative Names)?
SANs allow a single SSL certificate to secure multiple domains or subdomains (e.g., example.com, www.example.com, api.example.com).