NT hash
Compute a Windows NT hash (MD4 of UTF-16LE) from a password, on your device. Unsalted and trivially cracked, this is a forensics tool, not a way to protect anything.
Runs on your device. The file is never uploaded.
NT hash takes a password typed into the option box, encodes it as UTF-16LE and prints the bare 32 character MD4 digest, with no label and no file name. An empty password is allowed and gives a value seen often in dumps. No salt is applied, so two accounts sharing a password also share a digest.
Questions
What is an NT hash?
The Windows password hash: MD4 of the password encoded as UTF-16LE. That is the whole construction. There is no salt, no iteration count and no work factor, so it is extremely fast to compute, which means guessing it at scale is cheap. Treat it as a forensics and analysis value, not as a way to protect a password.
Can I use it to store passwords?
No. Being unsalted means identical passwords give identical hashes, so precomputed tables apply directly and one cracked hash reveals every account that shared the password. If you are storing passwords, use Argon2id hash or bcrypt hash on this site instead: both salt and both are deliberately slow.
Why is the empty password allowed?
Because NT of the empty string is a real value you meet in the field. The password option can be left empty, and UTF-16LE of an empty string is empty, so the result is MD4 of zero bytes: 31d6cfe0d16ae931b73c59d7e0c089c0. Seeing that value in a dump usually means the account has no password set.
Can it also do the LM hash?
No. Only the NT half is here. The LM hash needs DES, which this site does not ship, so there is no tool for it. If you are working through an old dump that has both columns, this page covers the NT column only.
What does the output look like?
The bare 32-character hex digest, with no label and no filename, since there is no file involved and the password comes from an option box. That is the form you normally see in a hash dump, so it can be compared against one directly. MD4 produces 16 bytes, which is why the string is 32 characters long.
Does the password get sent anywhere?
No. hash-wasm runs as WebAssembly in a Web Worker in this tab and the password stays in the page. Nothing is uploaded and nothing is stored between runs. Given how weak an NT hash is once it exists, keeping the computation local is the only sensible way to do it.