hash-check.com: A Third-Party Cryptographic Hash Bank
The Check That Proves Nothing
The standard advice for verifying a download is: get the file, get the hash from the same page, compare them. If they match, the file is intact.
That check only proves the file matches the hash on that page. If an attacker compromises the site and replaces the installer with something malicious, they update the hash displayed next to it, and your verification passes perfectly. You have confirmed the file is exactly what the attacker intended you to download.
This is not a theoretical gap. It is the shape of most supply-chain attacks against small software vendors and, more importantly, against the third-party download sites everyone uses instead of the vendor.
The fix is a hash that lives somewhere other than the file's own host, computed by someone other than the file's publisher. That is what a third-party hash bank is.

What hash-check.com Does
hash-check.com stores cryptographic hashes computed by the site itself, from the file, rather than copied from a vendor's page. At the time of writing that is more than 63,000 recorded checksums.
Practical workflow:
Check one file. Paste a SHA-256, SHA-1, MD5 or SHA-512 value — or the URL you downloaded from — and the site tells you whether that exact file is already known, and what it is.
Browse by product. If you are looking for a specific tool's official hash, you can find it by product rather than hunting the vendor's page.
Watch a URL. This is the feature that matters most for ongoing integrity: point it at a download location and it emails you when the file behind that URL changes. That is how you find out that a link you trusted yesterday now serves something else.
There is also a free Hash Checker tool on this site that computes a file's SHA-256 locally in the browser and looks it up, so you never upload the file itself.
Where It Helps, And Where It Does Not
It helps when you want an independent record of what a download looked like at a point in time, and when you want to know that a file has not silently changed since.
It helps against the compromised-page attack, because the attacker would have to compromise the hash bank too — a much harder target than one vendor's CMS.
It does not help if the file was malicious when it was first recorded. The bank records what a file is, not whether its author meant well. A hash match tells you "this is the same file 4,000 people and a watcher have seen", which is evidence of consistency, not of safety.
It does not help for files nobody has recorded. Absence from the database means nothing; check the project's signed releases instead.
Signatures are still better where available. A GPG signature or an Authenticode signature ties the file to a key the publisher controls, and that is a stronger claim than "this hash matches what we saw". Hashes are the fallback when no signature exists, which is most small software.


Why I Built It
I kept hearing the same story from people who do this properly: they download a file and its hash from the same page, compare, and feel safe. The gap is obvious once you say it out loud, and there was no simple, free place to look a hash up.
It started as a way to learn to code and it has kept going. The scope now is deliberately narrow: record hashes, let people search them, and tell you when a watched file changes. It is not a malware scanner and it does not pretend to be.
Using It Without Fooling Yourself
Three habits that make the tool worth something:
Check the hash of the file you actually received, not the one on the page you downloaded from. Compute it locally.
Prefer the watcher for anything you install repeatedly — drivers, installers, portable tools you keep on a USB stick. A one-off check is a snapshot; a watch is a tripwire.
Treat a mismatch as a stop sign, not a puzzle. A changed hash against a watched URL means either a legitimate update or a substitution. Confirm through the publisher's own channels before you run it.
Don't trust the download button. Trust the hash.
If this was useful, More hands-on tech guides at TechGeek. No pressure — read it whenever it's useful.