Tool to generate, decode and verify an NTLM hash (NT hash) online from a Windows password, compatible with MD4 and UTF-16LE, ideal for security testing and Active Directory auditing.
NTLM Hash - dCode
Tag(s) : Modern Cryptography, Informatics
dCode is free and its tools are a valuable help in games, maths, geocaching, puzzles and problems to solve every day!
A suggestion ? a feedback ? a bug ? an idea ? Write to dCode!
An NTLM hash (or NT hash) is a 128-bit (16-byte) cryptographic fingerprint. NTLM (NT LAN Manager) is a remnant (still very much present) of the Windows ecosystem. Although Microsoft is now pushing towards Kerberos, NTLM hashing remains central to many network and security operations.
Example: 31D6CFE0D16AE931B73C59D7E0C089C0 is an NTLM hash
To calculate an NTLM hash: encode the password in UTF-16LE and then apply the MD4 algorithm to this string. The result is a 128-bit hash (32 hexadecimal characters).
Example: password is encoded as 700061007300730077006f0072006400 in UTF-16LE hexadecimal and produces the MD4 hash 8846f7eaee8fb117ad06bdd830b7586c
Often, the hexadecimal string representing an NTLM hash is displayed with uppercase characters.
A hash cannot be decoded: a hash function like MD4 is designed to be one-way; there is no algorithm that can directly recover the password from its hash.
However, it is possible to use a dictionary attack, which consists of testing a set of likely passwords until one is found that produces the same hash.
dCode uses a dictionary of several million passwords, but if the password is not in the dictionary, the search will fail.
Historically, the LAN Manager (LM) hash was the first standard; this older DES-based algorithm is now considered obsolete and extremely vulnerable.
Subsequently, it was superseded by the NTLM hash, which uses MD4 and introduces case sensitivity. While it represents a more secure step than the LM format, it remains vulnerable to modern brute-force and pass-the-hash attacks.
Currently, the standard is Kerberos, a modern protocol that breaks with previous methods by using encrypted tickets. Unlike its predecessors, it establishes mutual authentication and strong encryption, with the critical advantage of never transmitting a hash over the network during the transaction.
NTLM hashes are stored:
— On a local machine: in the SAM file (%SystemRoot%\System32\config\SAM), accessible only with SYSTEM privileges.
— In an Active Directory domain: in the NTDS.dit database on domain controllers, as well as in the memory of the LSASS.exe process.
dCode retains ownership of the "NTLM Hash" source code. Any algorithm for the "NTLM Hash" algorithm, applet or snippet or script (converter, solver, encryption / decryption, encoding / decoding, ciphering / deciphering, breaker, translator), or any "NTLM Hash" functions (calculate, convert, solve, decrypt / encrypt, decipher / cipher, decode / encode, translate) written in any informatic language (Python, Java, PHP, C#, Javascript, Matlab, etc.) or any database download or API access for "NTLM Hash" or any other element are not public (except explicit open source licence). Same with the download for offline use on PC, mobile, tablet, iPhone or Android app.
Reminder: dCode is an educational and teaching resource, accessible online for free and for everyone.
The content of the page "NTLM Hash" and its results may be freely copied and reused, including for commercial purposes, provided that dCode.fr is cited as the source (Creative Commons CC-BY free distribution license).
Exporting the results is free and can be done simply by clicking on the export icons ⤓ (.csv or .txt format) or ⧉ (copy and paste).
To cite dCode.fr on another website, use the link:
In a scientific article or book, the recommended bibliographic citation is: NTLM Hash on dCode.fr [online website], retrieved on 2026-02-22,