This page describes the architecture behind the claim “runs 100% in your browser” so you can check it rather than take it on trust.
Where the randomness comes from
Every generator calls crypto.getRandomValues(), the Web Crypto API that draws from the operating system’s cryptographically secure random pool (the same source browsers use for TLS keys). Integers are produced by rejection sampling so no character is favoured, and shuffles use Fisher–Yates driven by the same source. A build check greps the tool code for Math.random and fails if it finds one.
What runs where
- Hashing: SHA-1, SHA-256, SHA-384, SHA-512 and HMAC use
crypto.subtle. MD5, SHA-3 and bcrypt, which the Web Crypto API does not provide, run in WebAssembly modules from the open-source hash-wasm project, loaded only on pages that need them. - Files are read with the File API in 4 MB slices and hashed incrementally. There is no upload endpoint anywhere on the site.
- Breach checks send only the first five characters of a locally computed SHA-1 hash to Have I Been Pwned’s range API, directly from your browser, with padding enabled. Hashword’s server is not involved.
- QR codes are drawn as SVG by a small vendored library; your Wi-Fi name and password never leave the page.
- Strength estimates use a 10,000-entry common-password list downloaded to your browser and compared locally.
How to verify it yourself
- Open any tool page and press F12 (or Cmd-Option-I) to open DevTools.
- Choose the Network tab and clear it.
- Generate, hash or check something. No new request should appear. (The breach checker is the one exception: you will see a single request to api.pwnedpasswords.com containing five hex characters.)
- Switch to Application → Storage: no cookies or local storage entries from tools, apart from your dark-mode preference if you set one.
What the site itself does
The site is WordPress with the Bricks builder. Tool logic lives in a plugin whose JavaScript is served as plain ES modules, unminified, so you can read it in the Sources tab. Third-party code in the tool bundle is limited to hash-wasm (MIT) and qrcode-generator (MIT), both pinned and served from this domain, never from a CDN. There is no advertising, no tracking pixel and no analytics that records tool inputs or outputs.
Reporting a vulnerability
If you find a flaw in a tool, a way to make a generator predictable, or any data leaving the page that should not, please report it through the contact form with “security” in the subject. You will get an acknowledgement within three days and a fix or a public note within thirty. Please do not test against other users, and please give us the chance to fix an issue before publishing it.
Known limitations
- A compromised browser, extension or operating system can see anything you type on any website, including this one. The tools protect you from Hashword’s servers, not from your own machine.
- Crack-time figures are estimates against stated hardware assumptions and will drift as hardware improves.
- Passwords shown on screen can be photographed or shoulder-surfed. Copy and close.