I doubt that's actually a hash. It looks like base64 to me, which is an encoding. It's a slight technicality, but encoding's can be reversed easily, hash's can't.
EDIT: Running it through a base64 decoder, it's binary data (if it is infact a base64 encoded string). I believe it is though, the '=' on the end is a giveaway, and the rest of the string conforms to base64 too.
I doubt that's actually a hash. It looks like base64 to me, which is an encoding. It's a slight technicality, but encoding's can be reversed easily, hash's can't.
EDIT: Running it through a base64 decoder, it's binary data (if it is infact a base64 encoded string). I believe it is though, the '=' on the end is a giveaway, and the rest of the string conforms to base64 too.
Doesn't look like hash to me. It's a base64-encoding of 26 bytes of data:
It's no hash. It's Base64 encoding. The trailing
=
is usually a good indicator that it's Base64.The contents of the decoded text are pretty much gibberish, though.