Check CSR

Free CSR decoder. Paste your Certificate Signing Request to view subject, key type, fingerprint. Decode CSR, copy details. No signup.

Certificate Signing Request (CSR)

CSR must start with "-----BEGIN CERTIFICATE REQUEST-----" and end with "-----END CERTIFICATE REQUEST-----"

What is Check CSR?

Check CSR is a free online tool that decodes and displays the contents of a Certificate Signing Request (CSR). A CSR is a block of encoded text that you generate when requesting an SSL/TLS certificate from a Certificate Authority (CA). The CSR contains information about your organization and the public key that will be included in the certificate. Before submitting a CSR to a CA, or when troubleshooting certificate issues, you may want to verify what is inside. This tool parses the CSR and shows you the subject (Common Name, Organization, Country, etc.), the key type and size, and the SHA-256 fingerprint in a readable format.

The tool accepts a CSR in PEM format, which starts with "-----BEGIN CERTIFICATE REQUEST-----" and ends with "-----END CERTIFICATE REQUEST-----". You paste the entire block into the textarea and click Decode CSR. The tool uses OpenSSL to parse the CSR and extract the subject distinguished name (DN), the public key details, and the fingerprint. The results are displayed in a structured layout: a hero section for the Common Name, summary cards for key type, key size, and fingerprint, a subject details table, and a public key and fingerprint section. You can copy individual fields or use the Copy All button to copy everything at once.

Decoding a CSR is useful when you need to verify the Common Name (CN) matches the domain you intend to secure, when you want to confirm the key size (e.g., 2048 bits for RSA), or when you need to provide the fingerprint to a CA or support team. The tool does not validate the CSR against a CA or check if the certificate was issued. It only decodes and displays the contents. The tool is free, requires no signup, and does not store your CSR. Your private key never leaves your machine; only the CSR (which contains the public key) is pasted into the tool.

Who Benefits from This Tool

System administrators and DevOps engineers benefit when they need to verify a CSR before submitting it to a CA. Typos in the Common Name or Organization can cause certificate issuance to fail or result in a certificate for the wrong domain. Decoding the CSR lets you double-check all fields. The tool also shows the key type and size, which some CAs require to meet minimum standards (e.g., 2048-bit RSA or 256-bit ECC). The SHA-256 fingerprint is useful when you need to identify the CSR in CA systems or support tickets.

Web developers who request SSL certificates for the first time benefit from understanding what is in a CSR. The tool provides a clear breakdown of the subject fields (O, OU, C, ST, L, CN, emailAddress) and what they mean. The Copy All feature lets you quickly share the decoded details with a colleague or support agent. The Sample button loads an example CSR so you can see the output without generating your own. This is helpful for learning and documentation.

Security auditors and compliance teams may use the tool to verify that CSRs generated by their organization contain the correct organizational information. Ensuring consistency between the CSR and internal records is part of certificate lifecycle management. The fingerprint can be used to track which CSR corresponds to which certificate request in ticketing systems.

Support staff at hosting providers or CAs benefit when customers need help verifying their CSR. Instead of walking the customer through command-line OpenSSL, you can direct them to the tool. They paste their CSR, see the decoded output, and can copy the details to share. The tool works in any browser and requires no installation.

Key Features

Subject Details

The tool displays the full subject distinguished name from the CSR. Fields include Common Name (CN), Organization (O), Organizational Unit (OU), Country (C), State/Province (ST), Locality (L), and Email. Not all CSRs contain every field; the tool shows what is present. The Common Name is highlighted in a hero section because it is typically the domain name or hostname for the certificate. The subject details are shown in a table with a Copy button for the Subject Details section as a whole.

Key Type and Size

The tool extracts the public key from the CSR and reports the key type (e.g., RSA or EC) and the key size in bits. For RSA, 2048 bits or higher is recommended; the tool indicates "Secure" for 2048+ and "Use 2048+ bits" for smaller keys. For elliptic curve keys, the bit equivalent is shown. This helps you confirm that your CSR meets minimum security requirements before submission.

SHA-256 Fingerprint

The tool computes the SHA-256 fingerprint of the CSR (the DER-encoded request) and displays it in colon-separated hexadecimal format. This fingerprint uniquely identifies the CSR. CAs and support systems sometimes use it to match requests. You can copy the fingerprint with the section Copy button.

Sample and Copy

The Sample button loads an example CSR and decodes it immediately, so you can see the tool in action without pasting your own. The Copy All button copies all decoded fields (Common Name, Organization, key type, fingerprint, etc.) in a formatted block. Section-level Copy buttons let you copy just the Subject Details or Public Key and Fingerprint. The tool uses SweetAlert2 for copy confirmation toasts.

Error Handling

If the CSR format is invalid (missing BEGIN/END markers) or the content cannot be parsed, the tool displays an error message. Common causes include truncated paste, extra whitespace, or corrupted data. Fix the CSR and try again. The tool does not store failed attempts.

How to Use

  1. Open the Check CSR tool. Navigate to the tool page. You will see a textarea for pasting your CSR.
  2. Obtain your CSR. Generate a CSR on your server using OpenSSL or your hosting control panel. The CSR is a block of base64-encoded text between BEGIN and END lines. Copy the entire block including the markers.
  3. Paste the CSR. Paste the CSR into the textarea. Ensure you have the full content. The CSR must start with "-----BEGIN CERTIFICATE REQUEST-----" and end with "-----END CERTIFICATE REQUEST-----".
  4. Complete the captcha if required. If the site uses reCAPTCHA, complete it. The Sample button bypasses captcha for testing.
  5. Click Decode CSR. The tool parses the CSR and displays the decoded contents. The page scrolls to the results section automatically.
  6. Review the output. Check the Common Name, Organization, and other subject fields. Verify the key type and size. Note the SHA-256 fingerprint if needed.
  7. Copy details if needed. Use the Copy All button to copy everything, or use the section Copy buttons for Subject Details or Public Key and Fingerprint. Paste into your CA form or support ticket.

Common Use Cases

  • Verifying the Common Name in a CSR before submitting to a CA
  • Confirming the key size meets CA requirements (e.g., 2048-bit RSA)
  • Extracting the SHA-256 fingerprint for CA or support identification
  • Checking organizational details (O, OU, C, ST, L) for accuracy
  • Learning what fields are in a CSR for training or documentation
  • Troubleshooting certificate issuance failures by inspecting the CSR
  • Sharing decoded CSR details with colleagues or support agents
  • Auditing CSRs for compliance with internal policies
  • Comparing a CSR to an existing certificate to verify consistency
  • Quick reference when renewing certificates and regenerating CSRs

Tips & Best Practices

Always verify the Common Name before submitting. It should match the domain or hostname you intend to secure. For wildcard certificates, use *.example.com. For multiple domains, you may need a different CSR or SAN (Subject Alternative Name) support; this tool shows the subject only, not SANs.

Use at least 2048-bit RSA or 256-bit ECC for new certificates. The tool flags smaller keys. Many CAs no longer accept 1024-bit RSA. Plan for future compatibility.

Keep your private key secure. The CSR contains only the public key; the private key stays on your server. Never paste your private key into any online tool. This tool only needs the CSR.

If decoding fails, check that you copied the full CSR including the BEGIN and END lines. Some systems add extra blank lines; the tool handles normal whitespace. Ensure no characters were corrupted during copy-paste.

Use the Sample button to test the tool before pasting a real CSR. The sample CSR decodes successfully and shows the expected output format. This helps you understand what to look for in your own results.

Limitations & Notes

The tool decodes the CSR only. It does not validate the CSR with a CA, check if a certificate was issued, or verify the private key matches. It parses and displays the contents. For full validation, use your CA's tools or OpenSSL command-line verification.

The tool does not display Subject Alternative Names (SANs). SANs are often included in the CSR for multi-domain certificates. The OpenSSL functions used may not expose SANs in the same way. For SAN details, you may need to use OpenSSL command-line tools.

The fingerprint is of the CSR itself (the DER-encoded request), not of the certificate. Once the certificate is issued, its fingerprint will differ. Use the CSR fingerprint to identify the request; use the certificate fingerprint to identify the issued cert.

The tool does not store your CSR. Data is processed in memory and discarded. For highly sensitive environments, consider using OpenSSL locally instead of an online tool. The CSR contains your organization name and domain; it does not contain your private key.

FAQs

What is a CSR?

A Certificate Signing Request is a message sent to a Certificate Authority when requesting an SSL/TLS certificate. It contains your organization details and the public key. The CA uses it to issue a certificate. The private key stays on your server.

Is it safe to paste my CSR online?

The CSR contains only public information (organization name, domain, public key). It does not contain your private key. Pasting it into a decoder is generally safe. For maximum paranoia, use OpenSSL locally. The tool does not store your data.

Why did decoding fail?

The CSR may be truncated, malformed, or corrupted. Ensure you copied the full block including BEGIN and END lines. Check for extra characters or encoding issues. Try generating a new CSR if the problem persists.

What is the SHA-256 fingerprint for?

The fingerprint uniquely identifies the CSR. Some CAs use it to match requests. Support teams may ask for it when troubleshooting. It is also useful for your own records when managing multiple certificates.

Can I decode a certificate instead of a CSR?

No. This tool is for CSRs only. Certificates have a different format (BEGIN CERTIFICATE). Use an SSL checker or certificate decoder for certificates.

What key size should I use?

Use at least 2048-bit RSA or 256-bit ECC. The tool indicates "Secure" for 2048+ bits. Many CAs require this minimum. Smaller keys are deprecated.

Does the tool support EC (Elliptic Curve) keys?

Yes. The tool detects RSA and EC key types and displays the key size. EC keys are shown with their bit equivalent (e.g., 256 bits).

Where is the Sample CSR from?

The sample is a pre-generated example CSR for example.com. It is for demonstration only. Do not use it for real certificate requests.

Can I use this for code signing or other certificate types?

The tool parses any valid CSR in PEM format. Code signing and other certificate types use the same CSR format. The subject fields may differ (e.g., different O or OU values), but the tool will decode them.

Is the tool free?

Yes. Check CSR is free to use. No signup required. A captcha may appear depending on site settings. The Sample button bypasses captcha.