| Purpose | MD5 · Hash text or files up to 256 MiB locally, verify a digest and demonstrate bounded ASCII candidates. Compare downloads against trusted reference checksums. Hashes are one-way. This checks only a chosen ASCII candidate space; finding a match does not recover every possible original. Limits: length 1–6, at most 100,000 attempts and five seconds. No dictionaries, uploads or remote lookup. MD5 and SHA-1 are legacy algorithms and are unsuitable for modern security uses. | SHA-256 · Hash text or files up to 256 MiB locally, verify a digest and demonstrate bounded ASCII candidates. Compare downloads against trusted reference checksums. Hashes are one-way. This checks only a chosen ASCII candidate space; finding a match does not recover every possible original. Limits: length 1–6, at most 100,000 attempts and five seconds. No dictionaries, uploads or remote lookup. |
|---|
| Input | MD5 Hash & Verify: Text uses UTF-8 without normalization. Choose File bytes to hash an original file, including an empty file. The filename and MIME type are not part of the digest. | SHA-256 Hash & Verify: Text uses UTF-8 without normalization. Choose File bytes to hash an original file, including an empty file. The filename and MIME type are not part of the digest. |
|---|
| Output | MD5 Hash & Verify: Clear empties the input, the expected digest, and the result in one step, and the status returns to Ready. Nothing is kept between runs, so a list of identifiers can be checked one after another without leftovers. | SHA-256 Hash & Verify: Clear empties the input, the expected digest, and the result in one step, and the status returns to Ready. Nothing is kept between runs, so a list of identifiers can be checked one after another without leftovers. |
|---|
| Typical use | MD5 Hash & Verify: Legacy system identifiers or quick accidental-corruption checks | SHA-256 Hash & Verify: Verifying downloads and installers against published checksums |
|---|