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
Perform DES encryption and decryption online. Supports Text, Hex, and Base64 formats.
Please enter content and click Encrypt/Decrypt.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This page encrypts or decrypts text or encoded data with the Data Encryption Standard (DES), using a 64-bit key setting that provides 56 effective key bits. You can select ECB, CBC, CFB, or OFB mode and a supported padding option; CBC is the default. Key input can be text, hexadecimal, or Base64. For modes that require an initialization vector, supply or generate an IV in hexadecimal or Base64. Output is available in Base64 and hexadecimal.
DES is obsolete for protecting new sensitive information. NIST withdrew FIPS 46-3 in 2005 because DES no longer provided the security needed for federal information and directed users toward AES as a stronger replacement. NIST’s withdrawal notice · FIPS 46-3 status.
Decryption succeeds only when the algorithm, key bytes, key encoding, mode, padding, and IV agree with those used to create the ciphertext. A text key is interpreted as UTF-8 bytes; hexadecimal and Base64 inputs are decoded before use. The tool checks the key length for DES, so a visually similar key written in another format may not represent the same bytes.
ECB does not use an IV. CBC, CFB, and OFB require an IV in this tool. The selected padding also matters, especially for block-aligned data. Ciphertext is commonly carried as Base64 or hex text; select the format that matches the data you were given.
DES encryption alone does not show whether a message has been altered or came from a trusted sender. The tool’s DES configuration does not add a message authentication code or an authenticated-encryption check. A successful decryption therefore does not prove that the plaintext is authentic, complete, or safe to act on.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
For encryption, enter text or encoded input. For decryption, provide ciphertext in Base64 or hexadecimal and select that input format.
Choose Text, Hex, or Base64 and enter the key in that representation. DES uses a 64-bit key setting with 56 effective key bits; the entered value must decode to the required byte length.
Select the same mode and padding as the system that created the ciphertext. For CBC, CFB, or OFB, enter the matching IV or generate one only when encrypting new compatible data. ECB has no IV field.
Run the operation, then copy the Base64 or hex result needed by the receiving system. When decrypting, verify the plaintext independently and do not interpret successful output as proof of integrity.
For a legacy interchange, record the key encoding, mode, padding, IV, and ciphertext encoding used by the other endpoint. An IV is not a replacement for a key and must match during decryption. If any setting is unknown, test only with non-sensitive sample data while determining the original format.
Use cases
See how the tool fits into real work and everyday tasks.
A developer has a non-sensitive test vector and its original key, IV, mode, and padding. They select matching settings and compare the decrypted bytes with the expected sample while diagnosing an older integration.
A team verifies that a replacement system can read a controlled legacy fixture, then plans migration to a current approved design. Test output is not used to protect new production information.
A learner changes a setting with harmless example text to observe that ciphertext depends on the mode, padding, key, and IV. The exercise demonstrates compatibility requirements, not modern security.
Q&A
Find concise answers to common questions and confusing cases.
No. DES is obsolete; NIST withdrew its standard because it no longer provided the needed protection. Use an appropriately reviewed modern cryptographic design for new systems.
Check the key bytes and format, ciphertext encoding, mode, padding, and IV. All settings must match the original encryption, and decrypted bytes may not be ordinary text.
ECB does not use one. CBC, CFB, and OFB require an IV in this tool. For decryption, use the IV associated with the ciphertext.
No. This DES workflow does not authenticate the ciphertext. Unreadable or plausible-looking output cannot establish integrity or sender identity.
Notes
Review scope, result limitations, and important precautions before use.
Use this page only for learning or controlled legacy compatibility with non-sensitive data. DES must not be used to protect new sensitive information. NIST’s 2005 withdrawal notice explains that DES no longer provides the security needed for federal information and identifies AES as a stronger replacement.
Related
Discover related tools, collections, and available API capabilities.