Skip to content
PrimeForgeTools
Theme: system

Securityversion v1.0.0

Hash & Checksum

Compute a digest of exactly the bytes you give it, then check it against a published checksum. Text and files are hashed in this tab — nothing is uploaded, and the byte counter shows precisely what is being hashed, so the answer agrees with sha256sum down to the trailing newline.

Input

5 bytes

Algorithm

SHA-1 is broken for security use: collisions are demonstrated and cheap. Use it only for checksums and legacy compatibility, such as git object ids and older vendor checksums.

MD5 is broken for security use: collisions are trivial. Use it only for checksums and legacy compatibility, such as mirror verification and Content-MD5.

Format
SHA-256 digest—

A whole sha256sum line works too: the first token is compared, case-insensitively, against the hex digest.

All five algorithms

Every digest of the same bytes, in hex — for when a vendor published a checksum without saying which algorithm made it. The endpoint still returns exactly one digest per request.

  • SHA-256unavailable in this browser
  • SHA-384unavailable in this browser
  • SHA-512unavailable in this browser
  • SHA-1unavailable in this browser
  • MD5unavailable in this browser

From the command line

The same URL hashes whatever you pipe into it and answers with the digest alone — no filename column, nothing to strip. Use --data-binary, never -d: -d strips newlines and would silently change the answer. Bodies are capped at 1 MiB; for anything larger, hash it locally with shasum -a 256.

printf 'hello' | curl -fsS --data-binary @- 'https://tools.primeforge.app/hash?algorithm=sha256'
curl -fsS --data-binary @package.json 'https://tools.primeforge.app/hash'