HashyTools is maintained by Jorge. It is a collection of browser tools for developers who need to inspect data, reproduce cryptographic results, and check small examples without uploading their working inputs.
The main workflow connects AES-GCM encryption, a payload inspector, fixed test vectors, and a working browser, Node.js and Python example. Hashing, Base64 and JWT tools support related debugging tasks.
Examples state their input, expected output and limits. Random values such as salts, IVs, UUIDs and passwords change on every run; deterministic test vectors make cross-runtime comparison possible.
For the AES guide, automated checks encrypt in a browser and decrypt in Node.js and Python. They also test altered ciphertext, tags, passwords and AAD. Other checks cover hashing, JWT signatures, XML and page navigation. Passing these checks is not an independent security audit.
The AES JSON envelope is a HashyTools format built on standard primitives. It is not a universal format accepted by every AES tool. The guide specifies its exact parameters and links to the underlying standards.
Text, file and cryptography transformations run in your browser. IP lookup is an exception: it contacts external providers only after you start a disclosed lookup. Optional analytics and advertising are controlled separately. Read the privacy policy for details.
A browser tool cannot establish that your device is trustworthy, manage production keys, validate application permissions, or replace a review of your security design. Use public test data when following examples.
For a reproducible tool issue, email contact@hashytools.com with the page URL, browser, harmless sample input, expected result and actual result. Do not include passwords, tokens, personal data or confidential files.
For privacy or security concerns, use the same contact: contact@hashytools.com. Do not send live credentials.
Content and tool-behavior review: September 21, 2026.