Public Dashboard#

The public dashboard shows today’s known-good cryptographic hashes for all tracked software. No account, API key, or login is required.

Open it in any browser:

https://hashwatch.us/

Records are grouped by operating system — All / Windows / Linux / macOS / Android. Tabs with no current records are hidden automatically. Pick a platform, then use the search box to filter by executable name, vendor, or hash value.

Each product row is collapsed by default. Click it to expand the variants (different architectures or package formats for that product).


What the table shows#

ColumnDescription
FileFilename as a direct download link — clicking fetches the exact binary file from the vendor
VersionThe release version (always discovered live — never hardcoded)
ArchCPU architecture (amd64, arm64, arm, x86, universal)
SHA-25664-character hex hash. Click the button to copy the full value
SHA-140-character hex hash — blank if the vendor only publishes SHA-256
MD532-character hex hash — blank if the vendor only publishes SHA-256
SignerAuthenticode subject of the signing certificate. Hover for issuer, serial, and thumbprint. Blank for non-PE formats or manifest-only vendors.
SiteLink to the vendor’s release directory or tag page (the parent path before the file, so you see the source rather than triggering a download)
Verified✓ verified — HashWatch downloaded the binary itself; manifest — taken from the vendor’s published checksum file

Comparing a suspicious file#

  1. Compute the SHA-256 of the file you want to check.

    Windows (PowerShell):

    Get-FileHash -Algorithm SHA256 .\file.exe | Select-Object Hash

    Linux / macOS:

    sha256sum file.exe
  2. Open the dashboard, pick the right OS tab, and search for the executable name.

  3. Click the button next to the SHA-256 and paste it alongside your computed hash to compare.

ResultMeaning
Hashes matchThe file is byte-for-byte identical to the current vendor release
Hashes differThe file does not match — investigate further
Executable not listedHashWatch does not track this software

A matching hash does not guarantee safety. It means the file matches what the vendor distributed. A supply-chain compromise at the vendor level would still produce a matching hash. Treat hash verification as one signal alongside other detections.


When is the data updated?#

HashWatch fetches from vendor sources every day at 02:00 UTC. The dashboard cache has a 1-hour TTL — you may see data up to 1 hour old.


JSON endpoint#

The dashboard data is also available as JSON — no authentication needed:

GET https://api.hashwatch.us/public/hash-of-day
curl https://api.hashwatch.us/public/hash-of-day

Response:

{
  "date": "2026-06-04",
  "generated_at": "2026-06-04T02:14:37Z",
  "cache_hit": true,
  "hashes": [
    {
      "executable_name": "chrome-win64.exe",
      "version": "124.0.6367.82",
      "vendor": "Google LLC",
      "platform": "windows",
      "arch": "amd64",
      "hash_sha256": "b94d27b9934d3e08a52e52d7da7dabfac484efe04294e576e9e7c3e07ccb1e83",
      "hash_sha1": null,
      "hash_md5": null,
      "source_url": "https://dl.google.com/...",
      "download_verified": true,
      "valid_from": "2026-06-04T02:13:01Z",
      "sig_signer": "Google LLC",
      "sig_issuer": "DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1",
      "sig_serial": "0a123456789abcdef...",
      "sig_thumbprint": "1a2b3c4d..."
    }
  ]
}

Add ?date=YYYY-MM-DD to retrieve a specific day’s snapshot:

curl "https://api.hashwatch.us/public/hash-of-day?date=2026-05-01"