It's not encryption (for it can't be decrypted*) it's a hash. In particular, it has 43 alphanumeric characters, which roughly means its binary representation amounts for 256 bits. (so, 32 bytes). Therefore, I'd says it's SHA-256, but it can also be a bogus string made out of a "roll your own" algorithm.
When you try to recover your password, a random hash is generated and emailed to you and usually it's inserted into a "passwords_resets" table. When you visit the site, the hash you provide in the link is handled (through a webserver rewrite) as a query string argument.
If you present a legit hash, you are presented with a form where you can reset your password (I haven't looked at your link, it's just a common workflow). If the record isn't in the table, or it shows up as used, or its creation time is older than a reasonable threshold, then you aren't presented with said form.
Hashes are just a way to generate a seemingly unique string so that you can't guess a hash out of nowhere. Nowadays there are other ways to generate such a string, because computing power has grown exponentially since the times in which SHA256 was thought to be unbreakable.
Thought it doesn't make sense to talk about denryption for a hash, you can try to find a string whose hash matches the one of your question. Again, with enough computing power you will, eventually.
(I thought sha-256 had 44 chars but I can't find where did I got that notion... maybe it's a padding char?)