Free Online Rijndael-256 (MCRYPT OFB) Decrypt & Encrypt
This tool decrypts — and encrypts — data written by PHP's mcrypt_generic() / mdecrypt_generic() pair using Rijndael-256 in OFB mode, which is what most legacy PHP frameworks (CakePHP, CodeIgniter, older Laravel encoders, custom encryptData() / decryptData() helpers) used for encrypted cookies, API payloads and database fields. You supply the same two values your PHP code supplies — the secret key and the secret IV — plus the base64 data, and the plaintext appears instantly.
It is a faithful re-implementation of libmcrypt's own Rijndael-256 and OFB modules, built from their source and checked against libmcrypt's built-in Rijndael-256 self-test vector, so the output matches PHP byte-for-byte — including the quirks: the key is the 32-character hex string returned by md5($secretKey) used as raw ASCII bytes, the IV is taken as raw bytes, and an IV that is not exactly 32 bytes is zero-padded or truncated rather than rejected.
How To Decrypt Your Encrypted Data
Paste your Secret Key and Secret IV into the two fields at the top, paste the base64 ciphertext into the Input panel, then press Decrypt (or Ctrl+Enter). The plaintext lands in the Output panel, ready to copy.
If the result is binary junk but you know the values are right, tick Swap key/IV roles. It keeps both fields as labelled and only changes the pairing — the Secret IV is hashed with md5() into the cipher key and the Secret Key becomes the IV — which is what legacy helpers do when their fallbacks read encryption_secret_key and encryption_secret_iv in the opposite order.
To go the other way, paste plaintext into Input and press Encrypt (or Alt+Enter) — you get base64 that your PHP code can decrypt with the same key and IV. Use Swap to feed the output back into the input and confirm the round trip. Whitespace and line breaks inside base64 are ignored, exactly like PHP's non-strict base64_decode().
Rijndael-256 Is Not AES-256 — Why Generic Decoders Fail
The name trips people up: mcrypt's rijndael-256 means a 256-bit block size, not a 256-bit key. Rijndael with a 256-bit block runs 14 rounds over eight 32-bit words and has a different ShiftRows pattern from the 128-bit block that became AES. Every mainstream library — Web Crypto, CryptoJS, Node's crypto, OpenSSL — only implements the 128-bit block, so pasting your key into any "AES decrypt" page returns garbage even with the correct key.
The mode is unusual too. libmcrypt's ofb.c is a byte-wise shift-register OFB: the full 32-byte register is block-encrypted for every single input byte, one keystream byte is consumed, then the register is shifted left and that byte is appended. Because OFB is a stream mode here there is no padding at all — ciphertext length always equals plaintext length, and there is never a "bad padding" error to tell you the key was wrong. That is why a wrong key quietly produces binary junk instead of an error; this tool flags it when the result is not valid UTF-8 and shows you the raw hex.
Migrating Off mcrypt (Removed in PHP 7.2)
PHP deleted the mcrypt_* extension in 7.2, so on any modern runtime you cannot call mdecrypt_generic() to read data your old system wrote. Rijndael-256/OFB has no OpenSSL equivalent either, so the usual openssl_decrypt() one-liner does not exist. This page lets you read those values from any browser — useful while migrating a legacy database column, decoding an old encrypted auth cookie, or auditing what a third-party integration actually stored — and then re-encrypt with a modern AEAD cipher.
Private By Design — Keys Never Leave This Page
Everything runs inside your browser tab: the Rijndael-256 core, the OFB chain, the MD5 key derivation and the base64 layer are plain JavaScript modules served with this page. There is no API call, no server-side decrypt endpoint, and no analytics on your content. Unlike ordinary web "decrypters", you never paste a production secret into somebody else's backend.
The data panels are remembered in your own browser between visits, but the Secret Key and Secret IV are never written to storage — close the tab and they are gone. If you decrypt live production secrets, do it on a machine you control and clear the fields when you are done.