Integrity

Correctness last checked 2026-11-13. You can verify both privacy and output without trusting a slogan.

Verify privacy in DevTools

  1. Open a tool such as htpasswd or bcrypt.
  2. Open developer tools → Network.
  3. Paste something distinctive and run the tool.
  4. You should see the page and its scripts — and no request that carries what you typed.
  5. Optionally open Sources / Debugger and inspect the client modules that implement the tool.

There is no public git remote published yet. Until there is, the shipped JavaScript in your browser is the source of truth — inspect it in DevTools.

Run the test suite

From the app directory:

npm test
npm run typecheck

Tests cover empty input, known-good vectors, and malformed input for the tool logic modules.

Sample vectors

These match the automated tests. Use them to spot-check the live pages.

Base64 (UTF-8)

Input:  ToolDeck
Output: VG9vbERlY2s=

JWT decode (unsigned example header.payload)

Token:  eyJhbGciOiJub25lIn0.eyJzdWIiOiIxMjMifQ.
Header: {"alg":"none"}
Payload: {"sub":"123"}
Signature is not checked.

MD5 checksum (not a password hash)

Input:  ToolDeck
MD5:    e7a587de2ffb50d87d4301c53a6ea822

MD5 and SHA-1 pages are labelled weak for passwords. bcrypt and htpasswd hashing happen entirely in the browser via vendored client libraries.

What we refuse

See About — what we refuse: no DNS/whois/fetch-URL tools, no JWT signing, no content mill.