Check a password storage record before migrating accounts
Admin ·
Start a login migration by checking the format of a representative stored record. A structured record may carry its version and cost fields. A bare digest usually requires the producer’s configuration or documentation.
Read the stored Argon2id parameters
Choose Load Argon2id example, then Identify format. The result recognizes the public sample from the PHC format specification. Compare the displayed fields with the algorithm label and the version and parameter segments in the input.
The output lists 16 decoded salt bytes and 32 decoded tag bytes. The result reports structure and field lengths. Use the producer’s documented verifier to check whether an actual record is intact.
| Recorded field | Expected result |
|---|---|
| v=19 | Version 19 |
| m=65536 | 65,536 KiB memory cost |
| t=2 | 2 passes |
| p=1 | 1 lane |
C2SP PHC string format and exampleRFC 9106 Argon2 inputs and outputs
Trace an ambiguous hex digest to its source
Choose Load ambiguous example and identify it. The report says Bare hexadecimal · ambiguous and shows 16 decoded bytes. That alphabet and length fit both MD5 and NTLM and can represent unrelated binary bytes.
For a migration, find the application’s hasher settings, prefix conventions and framework version. For example, Django’s PBKDF2 record uses a separate algorithm, iteration, salt and digest field. Use the source application’s expected layout when you plan the import.
0123456789abcdef0123456789abcdefDjango password storage formatlibxcrypt stored password formats
Common questions
Why does a familiar prefix show invalid fields?
The declared algorithm can be recognized while a mandatory field is missing or malformed. Compare delimiters, version, cost fields and salt and tag encodings with the producer’s layout.
Can this confirm the password for a stored record?
This tool reads the encoded structure. Password verification requires the source application’s hasher and its authentication procedure.