HashForge: Uses, Limits and Related Reading

A supporting tool from the Orthogonal blog

HashForge calculates and compares hashes in the browser. It supports the blog's explanations of byte integrity, authenticated references, and HMAC; it does not turn an untrusted download into a trusted one.

When it fits

Generate and compare hashes for text or files.

MD5, SHA-1, SHA-256, SHA-384, SHA-512, HMAC, comparison, hex, and Base64. Files load fully into memory.

Start with a small example

  1. Choose a text or file example and the algorithm required by your documented workflow.
  2. Obtain any expected digest through a separately trusted channel.
  3. Compare the complete digest. Use synthetic inputs, not production secrets, when exploring the HMAC controls.

Limits to understand

Files are loaded into memory. MD5 and SHA-1 are not suitable where collision resistance is required. Matching a checksum establishes a byte comparison against that reference, not the source's identity or safety. HMAC requires correct key handling beyond what an online demonstration page can establish.

Input processing and privacy

Hashing code processes text, file bytes, and HMAC inputs in the browser. Advertising and analytics requests are separate from those inputs.

Local processing is not a promise of zero network requests. Read the privacy policy and use non-sensitive examples unless you have independently reviewed the application.

Related reading

This introduction describes the public tool and its limitations, not an independent security certification. Check the current application for available controls. Return to all blog articles when you are done.