Is my data private when using CSR (Certificate Signing Request) Inspector?

Yes. Code Station operates completely client-side without external telemetry, uploads, or server proxies. Your data never leaves your device.

Can AI agents use CSR (Certificate Signing Request) Inspector?

Yes. CSR (Certificate Signing Request) Inspector supports browser-native WebMCP (Web Model Context Protocol) and local stdio MCP servers via codestation-mcp for automated workflows.

WebPKI & Advanced Cryptography

CSR (Certificate Signing Request) Inspector

Keep this tool in your workbenchReport a problem

🔒100% In-Browser Cryptography. Operations execute locally using Web Crypto API. Private keys and passphrases never leave your browser.

PKCS#10 Certificate Signing RequestASN.1 DER Parser

CSR Input (PEM format or Base64 DER)

Loading WebPKI & Cryptography controls…

Browse the WebPKI & Advanced Cryptography station →

What does this tool do?

CSR (Certificate Signing Request) Inspector: pkcs#10 pem or base64 der → subject distinguished name (dn), subject alternative names (sans), public key algorithm & modulus, cryptographic self-signature validity, parsed asn.1 structure. Process locally in your browser. Inputs: PKCS#10 PEM or Base64 DER. Outputs: Subject Distinguished Name (DN), Subject Alternative Names (SANs), Public Key Algorithm & Modulus, Cryptographic Self-Signature Validity, Parsed ASN.1 Structure.

How to use it?

Provide the listed input and choose Inspect CSR. Review the result, then copy or download where available. Clear removes inputs and results.

Browser-local processing. No uploads, content logging, persistence or remote resource loading. Generated markup is inert text; files are treated as untrusted data.

100% in-browser cryptographic processing using Web Crypto API. Private keys, passphrases, AES-GCM payloads, and certificate requests are calculated client-side and never sent to any server.