Example
The text hello has this SHA-256 hash:
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
Change it to Hello and the hash is completely different. That sensitivity is what makes
a hash work as proof.
Why hashes are used as proof
- Integrity: a matching hash proves the file has not been altered.
- Privacy: you can publish the hash without publishing the file.
- Efficiency: a 64-character value represents a file of any size.
SecureAuthor records the SHA-256 hash of your file with a timestamp and anchors it on the blockchain. How it works →
Calculate a SHA-256 hash yourself
| System | Command |
|---|---|
| Windows | certutil -hashfile "C:\path\file.png" SHA256 |
| Windows PowerShell | Get-FileHash "C:\path\file.png" -Algorithm SHA256 |
| macOS | shasum -a 256 /path/file.png |
| Linux | sha256sum /path/file.png |
Compare the result with the SHA-256 line on your SecureAuthor certificate.
Things that change a hash (and surprise people)
- Re-saving or exporting an image, even at the same quality.
- Sending through WhatsApp, Telegram, Instagram or Facebook (they recompress).
- Removing or editing metadata (EXIF, author fields).
- Converting a document to another format, e.g. DOCX → PDF.
Keep the exact registered file.