CSR

CSR Decoder

Decode PKCS#10 CSR subject, SANs, public key, signature, and fingerprints

Security & Auth
πŸ”’ 100% client-side β€” your data never leaves this page
Maintained by ToolsKit Editorial Teamβ€’Updated: August 23, 2026β€’Reviewed: August 23, 2026
PKCS#10 CSR

A valid CSR signature does not prove domain control, requester identity, or CA issuance.

Request summary

Subject, SANs, public key, signature algorithm, and fingerprints will appear here.

About this tool

CSR Decoder parses PEM or binary DER PKCS#10 certificate signing requests and extracts the requested Subject, Common Name, Subject Alternative Names, public-key algorithm and size or curve, signature algorithm, extension count, and attribute OIDs. It verifies the CSR's self-signature and calculates SHA-256 fingerprints for both the complete request and SubjectPublicKeyInfo. Signature validity only proves that the request was signed by the included private key; it does not validate domain control, requester identity, policy compliance, or whether a certificate authority will issue the certificate.

Scenario Recipes

01

Review a CSR before certificate submission

Goal: Catch identity or key mistakes before sending a request to a CA

  1. Open the CSR and confirm its self-signature is valid.
  2. Review Subject, SANs, key parameters, and signature algorithm against the certificate profile.
  3. Record the public-key fingerprint and submit the original CSR through the approved CA workflow.

Result: A locally reviewed request with key identity and requested names documented.

Frequently Asked Questions

Which CSR formats are supported?

You can paste PEM or open PEM and binary DER .csr files up to 2 MB.

Does it show Subject Alternative Names?

Yes. SAN values requested through the extensionRequest attribute are listed by type.

What does Signature valid prove?

It proves the request data matches the signature made by the included public key's corresponding private key.

Does a valid signature prove domain ownership?

No. Domain control, organization identity, policy checks, and authorization are separate CA validation steps.

Why are there two SHA-256 fingerprints?

One identifies the complete CSR bytes; the other identifies its public-key SubjectPublicKeyInfo.

Is the CSR uploaded?

No. ASN.1 parsing, extension extraction, signature verification, and hashing run locally.

Keep browsing