गाइड्स EN
Bramhify Pro

एडवांस टूल्स, अनलिमिटेड इस्तेमाल और प्रायोरिटी सपोर्ट पाएं।

अभी अपग्रेड करें
Encrypted Private Key Decryptor Icon

एन्क्रिप्टेड प्राइवेट की डिक्रिप्टर

New

पासफ़्रेज़ से PKCS#8 और OpenSSL PEM प्राइवेट की को ऑफ़लाइन डिक्रिप्ट करें और पब्लिक की निकालें।

🔐 PKCS#8 Encrypted Key (PBES2 / AES-256)
📜 Legacy OpenSSL PEM (Proc-Type: 4,ENCRYPTED)
नेटिव Web Crypto API के माध्यम से 100% ऑफ़लाइन डिक्रिप्शन। आपकी प्राइवेट की और पासफ़्रेज़ कभी किसी सर्वर पर नहीं जाते।

ऑफ़लाइन अनलॉक करने के लिए अपनी एन्क्रिप्टेड PEM प्राइवेट की और पासफ़्रेज़ दर्ज करें।

पासफ़्रेज़ का उपयोग करके एन्क्रिप्टेड प्राइवेट की ऑफ़लाइन डिक्रिप्ट करें

PHP OpenSSL, Laravel, Symfony, Nginx और Node.js प्रोजेक्ट्स में पासफ़्रेज़-लॉक्ड PEM प्राइवेट की आम हैं। Bramhify का प्राइवेट की डिक्रिप्टर बिना OpenSSL CLI इंस्टॉल किए या किसी सर्वर पर की भेजे सीधे आपके ब्राउज़र में PKCS#8 और OpenSSL PEM कुंजियों को अनलॉक करता है, पब्लिक की निकालता है और JWK एक्सपोर्ट करता है।

Supported Encrypted Private Key Formats

1
PKCS#8 Encrypted PEM (BEGIN ENCRYPTED PRIVATE KEY): Modern RFC 5958 PBES2 containers using PBKDF2 (SHA-1, SHA-256, SHA-384, or SHA-512) with AES-128-CBC, AES-256-CBC, AES-128-GCM, or AES-256-GCM.
2
Legacy OpenSSL PEM (Proc-Type: 4,ENCRYPTED): Traditional PKCS#1 RSA (BEGIN RSA PRIVATE KEY) and SEC1 EC (BEGIN EC PRIVATE KEY) keys encrypted with AES-128-CBC or AES-256-CBC via EVP_BytesToKey — commonly generated by PHP OpenSSL and older tutorials.
3
Public Key Derivation & JWK Export: Once decrypted, Bramhify automatically derives the matching SPKI Public Key (BEGIN PUBLIC KEY), computes its SHA-256 fingerprint, and converts the private key to JWK for immediate use in JWT libraries.

Encrypt (Re-Lock) Unencrypted Keys with a New Passphrase

Need to protect a plaintext PKCS#8, PKCS#1 RSA, or SEC1 EC private key before storing it in CI/CD secrets or a PHP project? Switch to Encrypt Key (Lock) mode, paste your unencrypted private key, enter a strong passphrase, and export an OpenSSL-compatible BEGIN ENCRYPTED PRIVATE KEY block protected with PBKDF2-SHA256 (100,000 iterations) and AES-256-CBC.

Security Guarantee & Known Limitations

All ASN.1 DER parsing, key derivation, and AES decryption run inside your browser's volatile RAM — zero network calls, zero localStorage, and an instant Wipe Memory button. Limitations: OpenSSH private keys (BEGIN OPENSSH PRIVATE KEY) rely on bcrypt-pbkdf, and obsolete 3DES/DES-CBC keys use deprecated ciphers not exposed by browser Web Crypto; convert those locally with ssh-keygen or openssl pkcs8 first. Need a brand-new key pair? Try our Public & Private Key Pair Generator or inspect tokens in our JWT & SD-JWT Decoder.

Frequently Asked Questions

Why does PHP or OpenSSL throw EVP_DecryptFinal_ex:bad decrypt? That error almost always means the passphrase in your .env file does not match the encrypted PEM key (often caused by trailing spaces, unescaped $ characters, or quoting issues). Paste your PEM key and passphrase here to test decryption instantly offline, and compare the derived SHA-256 public key fingerprint against your certificate or JWKS endpoint.

अक्सर पूछे जाने वाले सवाल

Is it safe to paste my encrypted private key and passphrase here?

Yes. All ASN.1 DER parsing, PBKDF2 key derivation, and AES decryption run 100% locally in your browser memory via the Web Crypto API. Zero data is transmitted over the network, nothing is saved to storage, and clicking Wipe Memory clears all fields immediately.

Which encrypted private key formats are supported?

It supports modern PKCS#8 encrypted keys (BEGIN ENCRYPTED PRIVATE KEY using PBES2 / PBKDF2-SHA1/256/384/512 with AES-128/256-CBC or AES-GCM) as well as legacy OpenSSL PEM keys (BEGIN RSA PRIVATE KEY or BEGIN EC PRIVATE KEY with Proc-Type: 4,ENCRYPTED and DEK-Info: AES-128/256-CBC).

Can it also encrypt an unencrypted private key with a passphrase?

Yes. Switch to Encrypt Key (Lock) mode, paste an unencrypted PKCS#8, PKCS#1 RSA, or SEC1 EC private key, provide a passphrase, and export an OpenSSL-compatible BEGIN ENCRYPTED PRIVATE KEY file protected with PBKDF2-SHA256 and AES-256-CBC.

Why does it also output a Derived Public Key?

Deriving the matching SPKI Public Key and SHA-256 fingerprint directly from the decrypted private key mathematically proves that your passphrase unlocked a valid key, and lets you verify it matches your server's public key or certificate.

Why are OpenSSH private keys or 3DES keys not supported?

OpenSSH encrypted keys use bcrypt-pbkdf and legacy 3DES keys use deprecated ciphers that the browser's native Web Crypto API intentionally omits. Convert those locally with ssh-keygen or openssl pkcs8.