So, it looks like the answer does not match:
From comments in ASP.Net identity source code
Version 0: PBKDF2 with HMAC-SHA1, 128-bit salt, 256-bit subdivision, 1000 iterations.
See also: SDL v5.1 Cryptography Guide, Part III)
Format: {0x00, salt, subsection}
Ultimately, the hash algorithm is SHA1, but it is not a simple SHA1 hash of a password or even a SHA1 + hash.
It is worth noting that SHA1 is considered βbrokenβ for digital signatures due to a mathematical attack, which reduces the computational effort to generate a collision to practically acceptable levels.
This does not apply to hashed passwords.
Links for further reading.
Is SHA-1 protected for password storage?
https://www.schneier.com/blog/archives/2005/02/sha1_broken.html
https://en.wikipedia.org/wiki/PBKDF2
https://www.owasp.org/index.php/Password_Storage_Cheat_Sheet
Rfc2898DeriveBytes and HMACSHA1
source share