CSR kya hai aur usme kya hota hai?

Ek PKCS#10 certificate signing request: aapki public key, claim ki gayi identity (subject aur SANs), aur aapki private key se bana self-signature jo prove karta hai ki wo aapke paas hai. CA verify karke certificate issue karta hai — private key kabhi aapka server nahin chhodti.

SANs CN se zyada kyun matter karte hain?

Browsers hostnames sirf SAN list ke against validate karte hain; CN legacy decoration hai. Bina SAN wala CSR aisa certificate deta hai jise koi bhi browser kisi domain ke liye accept nahin karta — sabse common CSR mistake.

Signature verification kya prove karta hai?

Ki request internally consistent hai: embedded public key CSR ke apne signature ko verify karti hai, matlab bytes exactly wahi hain jo key-holder ne produce kiye. Failure lagbhag hamesha truncated paste matlab hota hai, cryptographic attack nahin.

Kya browser tool mein CSR paste karna safe hai?

Design se CSR sirf public information rakhta hai — aur ye decoder ise bina kisi upload ke aapke device par parse karta hai. Saath generate hui private key alag baat hai: wo kabhi kahin nahin jaati.

CSR Decoder

CA ko bhejne se pehle PKCS#10 certificate signing request decode karein: subject, requested SANs, key size, algorithm aur signature verification.

CSR Decoder poori tarah aapke browser mein chalta hai. Requests device par decode hoti hain aur kabhi upload nahin hotin.

X.509 Certificate Decoder kholein

CSR Decoder ke baare mein

CSR Decoder exactly wo dikhata hai jo ek certificate signing request maangta hai, isse pehle ki aap ise kisi certificate authority ko bhejein. PEM block paste karein aur subject ka distinguished name field-by-field padhein, requested subject alternative names — wo hissa jo actually decide karta hai ki certificate kaunse hostnames secure karega, kyunki browsers CN ko ignore karte hain — public key ka type-size, aur signature algorithm. Decoder CSR ke apne signature ko bhi verify karta hai — classic failure pakadne ka fastest tareeka: ek request jo generating server aur paste hone wale form ke beech truncate ya alter ho gayi. Warnings un cheezon par fire hoti hain jo CAs bounce karte hain: 2048 bits se neeche ka RSA aur missing SAN.

Features

Poora subject DN labelled fields mein
Requested subject alternative names — DNS, IP, email
Key type aur size: RSA, curve ke saath EC, Ed25519
Signature algorithm naam se, sirf OID nahin
Self-signature verification truncated pastes pakadta hai
Galti se paste hue certificates aur private keys detect karta hai

CSR Decoder kaise use karein

CSR PEM paste karein ya sample load karein
Subject aur especially SAN list check karein
Key size aur algorithm CA ki bar se milaayein
Green signature badge matlab paste intact aaya

Example

Input

CSR for example.com

Output

CN=example.com · SANs: example.com, www.example.com · RSA 2048 · SHA256withRSA · signature verifies

SAN list hi wo hai jo certificate actually secure karega.

Common errors aur troubleshooting

Signature verify nahin ho raha. — Generation ke baad bytes badal gaye — usually truncated copy, lines rewrap karne wala editor, ya document ke smart quotes. Original generating machine ki original file se directly re-copy karein.
CN mein domain hai phir bhi SANs nahin dikh rahe. — Browsers saalon se CN ignore karte hain; SAN-less CSR se issue hua certificate kuch bhi secure nahin karta. Har hostname (www variant sahit) wale subjectAltName extension ke saath regenerate karein.
Decoder kehta hai paste kiya gaya certificate hai, CSR nahin. — BEGIN CERTIFICATE aur BEGIN CERTIFICATE REQUEST alag objects hain. Issued certificates ke liye X.509 decoder use karein; ye tool issuance se pehle wali request padhta hai.

Aksar pooche jaane wale sawaal

CSR kya hai aur usme kya hota hai?: Ek PKCS#10 certificate signing request: aapki public key, claim ki gayi identity (subject aur SANs), aur aapki private key se bana self-signature jo prove karta hai ki wo aapke paas hai. CA verify karke certificate issue karta hai — private key kabhi aapka server nahin chhodti.
SANs CN se zyada kyun matter karte hain?: Browsers hostnames sirf SAN list ke against validate karte hain; CN legacy decoration hai. Bina SAN wala CSR aisa certificate deta hai jise koi bhi browser kisi domain ke liye accept nahin karta — sabse common CSR mistake.
Signature verification kya prove karta hai?: Ki request internally consistent hai: embedded public key CSR ke apne signature ko verify karti hai, matlab bytes exactly wahi hain jo key-holder ne produce kiye. Failure lagbhag hamesha truncated paste matlab hota hai, cryptographic attack nahin.
Kya browser tool mein CSR paste karna safe hai?: Design se CSR sirf public information rakhta hai — aur ye decoder ise bina kisi upload ke aapke device par parse karta hai. Saath generate hui private key alag baat hai: wo kabhi kahin nahin jaati.

Related tools

X.509 Certificate Decoder — Ek PEM ya DER certificate ko subject, issuer, validity, SANs aur fingerprints mein decode karein.
Certificate & Private Key Matcher — Check karein ki koi SSL certificate aur private key ek saath belong karte hain ya nahi, seedhe aapke browser mein.
SSH Key Generator — Ed25519, RSA ya ECDSA SSH key pairs aapke browser mein generate karein aur download karein.
PFX to PEM Extractor — Ek password-protected .pfx/.p12 file ko certificate, chain aur private-key PEM blocks mein split karein.
PPK ↔ PEM Converter — SSH private keys ko PuTTY .ppk aur OpenSSH/PEM (RSA & Ed25519) ke beech aapke browser mein locally convert karein.
Hash Generator — Web Crypto API ke through SHA-256 / SHA-1 / SHA-384 / SHA-512.