We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Provides TripleDES encryption and decryption features, supporting common modes like CBC/ECB and PKCS padding to protect sensitive data.
Please enter content and click Encrypt/Decrypt.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Triple DES, also called 3DES or TDEA, applies the DES block cipher in repeated stages. This page can encrypt or decrypt text using a selected key size, cipher mode and padding, with input and output represented as Base64 or hexadecimal. The supported modes are ECB, CBC, CFB and OFB; CBC and the other non-ECB modes require an initialization vector (IV). The default settings are CBC, PKCS7 padding and a 192-bit key.
Decryption only works when the settings match the system that produced the ciphertext: key bytes, mode, padding, IV and ciphertext encoding must agree. An IV is separate from the key and is needed to reproduce the original operation. For interoperability, confirm whether a source format stores or transmits it separately and how it encodes the ciphertext.
NIST withdrew its TDEA recommendation effective January 1, 2024. It states that TDEA is no longer an approved block cipher for applying new cryptographic protection after December 31, 2023, while legacy decryption and certain verification operations for already-protected data remain permitted under its transition guidance. Treat this utility as a compatibility aid for authorized legacy data, not as a way to protect new information.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Select encryption or decryption. For decryption, identify whether the supplied ciphertext is Base64 or hexadecimal and paste it in that representation.
Set the key using the same key size and encoding expected by the source, then match the mode and padding. Choose ECB only if the legacy system actually used it; otherwise provide the corresponding IV in its expected format.
Run the operation and compare the result with a known test vector or trusted output from the authorized system. If decryption produces unreadable text or an error, recheck the format, key, IV, mode and padding rather than assuming the cipher recovered valid plaintext.
Use cases
See how the tool fits into real work and everyday tasks.
A developer or administrator with permission to access archived data can reproduce the original settings to decode a small, known ciphertext sample while planning a supported migration.
An engineer can use matching key, IV, mode, padding and encoding values to investigate why two legacy systems produce different output, then move new protection to a current approved design.
Q&A
Find concise answers to common questions and confusing cases.
Usually one or more parameters differ from the original operation: key, mode, IV, padding or ciphertext encoding. Confirm all of them against the system that created the data and test with a known sample.
Do not use TDEA to apply new protection. NIST disallowed that use after December 31, 2023, while retaining limited legacy decryption allowance for already-protected data.
An IV is required for CBC, CFB and OFB in this tool; ECB does not use one. For a match, the IV value and its representation must be the same as those used by the original encryption.
Notes
Review scope, result limitations, and important precautions before use.
This tool does not make 3DES suitable for current security requirements, and its output is not authenticated ciphertext. A successful decryption does not verify who created a message or whether it was altered. Never paste production secrets, credentials or regulated data into a tool unless your organization has approved that handling path. Preserve source data and use a vetted migration process for any system that still depends on TDEA.
Related
Discover related tools, collections, and available API capabilities.