Identify legacy algorithms and suggest modern replacements.
| Item | Value | Guidance |
|---|---|---|
| MD5 | Migrate | Use SHA-256+ for integrity; use a password KDF for passwords. |
| SHA-1 | Migrate | Use SHA-256+ for modern cryptographic applications. |
| 3DES | Migrate | Use AES with an authenticated mode. |
| RC4 | Migrate | Use modern authenticated encryption. |
| AES-ECB | Migrate | Use an authenticated mode such as AES-GCM. |
| RSA PKCS#1 v1.5 encryption | Migrate | Use RSA-OAEP where RSA encryption is required. |
| Custom crypto | Replace | Use established libraries/primitives. |
Review the available algorithms, properties, key sizes, compatibility notes, and recommended use cases shown on the page. Match the guidance to your protocol, threat model, and current platform support rather than selecting an algorithm by name alone.
The cryptography result or reference describes the encoding, key, digest, entropy, or algorithm selected and the input supplied. Encoding is not encryption, and a generated value is only as secure as the randomness, implementation, and handling behind it.
Use this for learning, format conversion, or preliminary cryptographic planning. Verify algorithms and key sizes against current security guidance; never expose private keys, production secrets, or live credentials in an untrusted tool.