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
Generate HAVAL hashes online. Supports multiple output lengths and computational passes for data integrity verification.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
A hash function maps input to a fixed-length digest; the digest is not ciphertext and has no decryption step. HAVAL is a historical hash design with variable output length and pass count. Here the available output lengths are 128, 160, 192, 224, and 256 bits, and each can be paired with 3, 4, or 5 passes. Record both values: HAVAL-256/5 and HAVAL-256/3 are different variants even though both produce 256-bit outputs. The default is HAVAL-128/3.
Enter text and choose one of the listed variants. The result area displays lowercase and uppercase hexadecimal forms. Hexadecimal is a text representation of bytes: each hex character represents four bits, so a 128-bit digest is 32 hex characters and a 256-bit digest is 64. Changing letter case changes only the display, not the digest value.
This page hashes text rather than accepting a file or a pre-encoded Hex/Base64 input mode. HAVAL source material describes the algorithm's variable-length design; it does not establish that this legacy function is suitable for modern security applications.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Paste or type the content into the text box. Spaces, punctuation, capitalization, and line breaks are part of the input and can change the digest.
Select both the digest length and pass count, such as HAVAL-160/4. Note that complete setting if another system must reproduce the value.
Press the calculate control. HAVAL requests are processed remotely, so do not submit confidential text or secrets.
Copy lowercase or uppercase hexadecimal as required by the receiving system. Compare the full string and the exact variant; do not rely on the Base64 display for byte-level interchange.
For a quick truncation check, divide the selected bit length by four: 128 bits corresponds to 32 hex characters; 160 to 40; 192 to 48; 224 to 56; and 256 to 64. The character count only checks length, not whether the input or algorithm choice matches.
Use cases
See how the tool fits into real work and everyday tasks.
If a legacy system explicitly stores a HAVAL digest, choose its exact output length and pass count and compare the hexadecimal value against a known test record.
Use a non-sensitive sample such as Hello World to see how changing the variant changes the displayed digest. This is an illustration, not a cryptographic-strength test.
Q&A
Find concise answers to common questions and confusing cases.
No. It is a hash digest, not encrypted text; the original input cannot be recovered by decrypting the output.
Check spaces and line breaks in the input, then compare both the output length and pass count. The variant must match exactly.
No. HAVAL here is a fast legacy digest, not a password-storage workflow. NIST guidance calls for a salted, suitable key-derivation function for password verifiers.
Do not assume so. The current display is formed by Base64-encoding the hexadecimal text. Use the hexadecimal result when a system requires the digest, and verify encoding with that system's specification.
Notes
Review scope, result limitations, and important precautions before use.
Do not enter passwords, API keys, private records, or other sensitive text: HAVAL calculation is server-side. Treat HAVAL as a legacy compatibility or educational choice, not a modern security recommendation. Keep the full variant alongside any saved digest, and do not interpret a matching digest as proof of a trusted source.
Related
Discover related tools, collections, and available API capabilities.