For security reviewers and admins who need to confirm that a value has not been altered or to compare a string against a published checksum. You get MD5, SHA-1, SHA-256, SHA-384 and SHA-512 digests side by side.
Take an online exam and add a verified certificate to your public profile that anyone can check.
You enter
hello
The tool shows
SHA-256: 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824, plus the MD5, SHA-1, SHA-384 and SHA-512 lines
Hash the file with a local tool such as sha256sum or Get-FileHash and compare the result with the checksum on the vendor site; they must match exactly. This page hashes pasted text, so use it to compare short values, manifests or a checksum line itself.
Practical collision attacks exist for both, so two different inputs can be crafted to share a digest. Use SHA-256 or stronger when the hash protects integrity, and keep MD5 only for legacy lookups.
No. A hash is one-way and the same input always gives the same digest, so plain SHA-256 is too fast for storing passwords. Password storage should use a slow, salted algorithm such as bcrypt or Argon2.
Yes. It is free, needs no sign-up and runs entirely in your browser, so what you type is not uploaded. You only sign in if you want to email a result to yourself or save it to your CareerByteCode profile.
