Legacy Password Hash Tools

Compute precisely identified obsolete NTLM and legacy database password formats for compatibility work.

0 / 200,000
Advanced Options

How to use

Select NTLM, MySQL/MariaDB mysql_native_password, PostgreSQL legacy MD5, or historical MongoDB MONGODB-CR. PostgreSQL and MongoDB modes require the exact username because it participates in the digest.

Example

Input
Password with NTLM selected
Output
A4F49C406510BDCAB6824EE7C30FD852

Limitations

These are obsolete compatibility schemes, not universal current database formats and not recommendations for password storage. Do not enter production credentials. PostgreSQL SCRAM and modern MongoDB authentication are intentionally not substituted.

Frequently Asked Questions

Does MySQL mode represent every MySQL password?

No. It implements the specifically named mysql_native_password compatibility scheme, also historically used by MariaDB.

Why is a username required for some schemes?

PostgreSQL legacy MD5 includes the username after an inner password digest, while MONGODB-CR includes it in its historical construction.

Should I deploy these formats for a new system?

No. Use the modern password and authentication mechanism documented by that system.