For incident responders, auditors and students who find an unknown hash in a config, database dump or log. You get a short list of likely algorithms based on length and prefix, which tells you what you are dealing with.
Take an online exam and add a verified certificate to your public profile that anyone can check.
You enter
5f4dcc3b5aa765d61d8327deb882cf99
The tool shows
32 hex chars; candidates MD5, MD4, NTLM
You cannot from the string alone: both are 32 hex characters. Context decides, such as where the hash was found (a Windows credential store points to NTLM) or whether a known plaintext reproduces it.
The $2a$, $2b$ and $2y$ prefixes mark bcrypt, a slow salted password hash. The tool also recognises $argon2 (Argon2), $6$ (sha512crypt) and $1$ (md5crypt).
Some values in configs are Base64-encoded text or keys rather than digests. When the input is non-hex, uses the Base64 alphabet and its length is a multiple of 4, the tool flags it so you do not mistake encoding for hashing.
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.
