They specified an invalid SHA512 algorithm instead of SHA256.
This looks like a typo. Although it does not do honor to such a site.
I rechecked the hash with the SHA256 algorithm and it is really correct:
Meh, in fact it was predictable that all situation will resolve itselfe in such way (though i bet that this was because OP hashed seed as a string)