Keccak-512 Hash Generator

Generate a digest from your input

Start with a known message so you can check the encoding and result format before comparing your own data.

1. Type or paste your message into Input text. Keep any spaces and line breaks that are part of the data.
2. Set Input Encoding: to UTF-8 for text, Hex for hexadecimal bytes, or Base64 for Base64-encoded bytes.
3. Leave Enable HMAC-KECCAK_512 off for an ordinary digest. To calculate a keyed result, enable it and configure HMAC Secret Key and Key Encoding (Search/Type): as described below.
4. Select Hex (lower), Hex (UPPER), or Base64 in the result options.
5. Keep Auto / Live enabled to update the result as you edit the input. Turn it off and click Run for a manual calculation.
6. Read Keccak-512 Hash Result and click Copy. To start again, use Clear where shown or the clear control in a text field; review the mode and encoding settings before the next calculation.

For a quick check, enter abc with Input Encoding: set to UTF-8 and Enable HMAC-KECCAK_512 off. Choose Hex (lower). The result is 18587dc2ea106b9a1563e32b3312421ca164c7f1f07bc922a9c83d77cea3a1e5d0c69910739025372dc14ac9642629379540c17e2a65b19d77aa511a9d00bb96.

Calculate a keyed message authentication code

Use this mode only when your reference expects HMAC-Keccak-512 and you have a test key.

1. Turn on Enable HMAC-KECCAK_512 to reveal the key controls.
2. Enter the test key in HMAC Secret Key. Match its byte representation with Key Encoding (Search/Type):; UTF-8 is appropriate for an ordinary text key.
3. Keep the message in Input text. Read the updated result with Auto / Live enabled, or click Run after setting the key.

With message abc, key key, both encodings set to UTF-8, and Hex (lower) selected, the result is e4f4eee6c36430b8b870fd98ae4cd51a488b11754b1f0123d4743c42fa315e201ad5c21df0bb8dee9009daf93bd9c1a1343a52fef5494810a837edd0b5d95712.

The form sends the message and HMAC key to the calculation API. Use public test data and test keys. Clear also empties the key field; it does not restore the mode or encoding settings.

Match original Keccak rather than standardized SHA-3

Keccak-512 and SHA3-512 both return 64 bytes, but their domain-separation suffixes differ. They produce different results for the same input, so an API labeled SHA3-512 cannot substitute for original Keccak-512.

Choose this variant when a protocol or test fixture explicitly requests Keccak-512. If the reference is a 128-character hexadecimal value, confirm the algorithm as well as its length; SHA-512 also produces 128 hex characters.

The current output contains 64 bytes, written as 128 hexadecimal characters. Hex (lower) and Hex (UPPER) change letter case; Base64 represents the same result bytes.

Input encoding determines the bytes being processed. UTF-8 abc, Hex 616263, and Base64 YWJj represent the same three bytes. Leaving UTF-8 selected for 616263 hashes six text characters instead.