SHA-3, cSHAKE & KMAC
SHA-3, Keccak, SHAKE and SP 800-185 hashes. TupleHash takes a JSON array of strings.
FAQ
Where is data processed?
In your browser. Inputs are not uploaded.
What is supported?
Keccak/SHA-3 use their fixed digest sizes; SHAKE and SP 800-185 use Output bytes. TupleHash uses the ordered JSON array, not uploaded files. Fixed customization UTF-8; KMAC keys use hex. File inputs are limited to 8 MiB.
Other Languages
References
How we make sure
We check this tool with the automated test suites linked below. Example checks are shown in their original language.
- Verification method
- Compare SHA-3/SHAKE with Node crypto and Keccak/cSHAKE/KMAC/TupleHash/ParallelHash, including XOF variants, with stored Python fixtures. Python separately constructs SP800-185 framing for the XOF and ParallelHash cases. TupleHash also compares equivalent UTF-8, Hex and Base64 JSON tuple inputs.
- Comparison reference
- Node.js 24.22.1 crypto (OpenSSL 3.5.9); PyCryptodome 4.3.0 stored fixtures with independent SP800-185 framing in scripts/generate-completion-fixtures.py.
- Verification scope
- Keccak/SHA-3 use their fixed digest sizes; SHAKE and SP 800-185 use Output bytes. TupleHash uses the ordered JSON array, not uploaded files. Fixed customization UTF-8; KMAC keys use hex. File inputs are limited to 8 MiB.
Test source and cases (select a file to read it)
-
completion-tools.test.js
- sha3-extensions: PyCryptodome customization fixtures and Node SHA3 SHAKE
- TupleHash parses the JSON array before applying Hex or Base64 to each item
- Secret fields start empty and fixed vectors are confined to the explicit example action
These checks cover the listed examples and boundaries, not every possible input. Round trips and checks using the same library are not independent verification.