File hash lookup
A file hash is a fingerprint: identical bytes always produce the same digest. Matching one against a catalogue of known software turns an anonymous binary into a named product and version. That is how you establish whether a file obtained from an untrusted source is a genuine vendor build or something repackaged, because a match proves the bytes are identical to the reference copy.
Run a file hash lookupexample: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
What a result contains
Known product
The product or package the hash belongs to.
Version and build
Which release the file was taken from.
Platform
The operating system the reference build targets.
Catalogue
The reference dataset the match came from.
How to read the result
- A match proves the file is byte-identical to a known build. That is strong provenance evidence, not a guarantee the file is safe to execute.
- Absence from the catalogue means the file is unknown, which is normal for anything custom or newly compiled. It is not a malware verdict.
Modules queried
- CIRCL hashlookup
- NSRL
Each row in a result set names the module it came from, so findings stay traceable.