Verify a certificate

To verify a SecureAuthor certificate, open the Authenticity tab in the web app or the Chrome extension and upload the original file together with the certificate PDF or its receipt ID. SecureAuthor recalculates the SHA-256 hash and shows whether it matches the registered one. You can also check the blockchain transaction on Polygonscan.

Verify a certificate

Upload the file and its receipt

What verification proves

A match proves that the file in front of you is exactly the file registered at the time shown on the certificate — not a single byte changed.

Three ways to verify

Verification always compares one file with one receipt:

  1. File + certificate PDF — the usual way.
  2. File + receipt ID — when you only have the ID (for example from an e-mail).
  3. File + a receipt from My Receipts — when you are signed in and the receipt is in your history.

To check whether two files are identical, calculate the SHA-256 of each with the free SHA-256 tool and compare the hashes.

Verify it yourself, step by step

You can check every link of the chain with standard tools and a public blockchain explorer.

1. Hash the file. Calculate the file's SHA-256:

  • Windows: certutil -hashfile yourfile.png SHA256
  • macOS: shasum -a 256 yourfile.png
  • Linux: sha256sum yourfile.png

Compare it with the SHA-256 line on the certificate. If they differ, stop: this is not the registered file.

2. Open the blockchain record. Click the Link to the blockchain record on the certificate. It opens the Polygon transaction on Polygonscan. Check that:

3. Read what was written. On Polygonscan, open More details → Input Data and choose View Input As → UTF-8. You will see a short JSON record:

{
  "periodStart": "2026-08-16T12:00:00.027Z",
  "periodEnd": "2026-10-17T12:00:00.028Z",
  "periodHash": "f555a2889c47833725d6091b49a3d0288ef19e8dff3b0595267a0251d3f4a03c",
  "linkToCheck": "https://api.secureauthor.com/api/daily-hash/f555a288…"
}
  • your certificate's timestamp must be earlier than periodEnd (usually it lies between periodStart and periodEnd);
  • periodHash must equal the Summary hash printed on your certificate.

4. Find your file in the batch. Open linkToCheck. It returns the batch list: every receipt anchored in this transaction, with its ID, SHA-256 hash and timestamp. Your receipt ID and your file's hash must be in the list.

5. Check that the batch list is genuine. The period hash is simply the SHA-256 of the batch list exactly as linkToCheck returns it. Save the response to a file without changing it and hash it:

curl -s "https://api.secureauthor.com/api/daily-hash/<periodHash>" -o batch.json
sha256sum batch.json          # macOS: shasum -a 256 batch.json
                              # Windows: certutil -hashfile batch.json SHA256

The result must equal periodHash in the transaction. Because the transaction cannot be changed, nobody can add, remove or alter a receipt in the batch without the hashes no longer matching. Keep batch.json next to your certificate.

That is the whole chain: your file → its SHA-256 → the batch list → its SHA-256 = the period hash → a Polygon transaction with a block time nobody can change.

Example transaction on Polygonscan

If the hashes do not match

  • Did you re-save, export or compress the file? Look for the original export.
  • Was it sent through a messenger or social network? They often recompress images and video. Use the file from your own device or cloud backup.
  • Is it the right version? Each version of a file has its own certificate.

Frequently asked questions

Who can verify a certificate?

Anyone who has the original file and the certificate or its receipt ID — a client, a platform, a lawyer or a court expert. Verification does not require the author's help.

The result says 'Files are different'. Why?

The file is not byte-for-byte the one that was registered. Re-saving, compressing, resizing, converting or editing a file changes its hash — even if it looks the same. Find the exact original.

Can I verify without the SecureAuthor app?

Yes. Calculate the file's SHA-256 and compare it with the certificate. Open the Polygon transaction on Polygonscan and read its input data as UTF-8. Download the batch list from linkToCheck, find your hash in it, and check that the SHA-256 of the downloaded list equals the periodHash in the transaction.

What is written on the blockchain?

A small JSON record: the start and end of the period, the period hash that summarises all receipts of that period, and a link to the list of those receipts. Files and their names are not written on-chain.

Can I compare two files directly?

Not in SecureAuthor: it compares a file with a receipt, not two files with each other. To check whether two files are identical, calculate the SHA-256 of each with the free SHA-256 tool and compare the two hashes.

Updated:

Protect your next file in seconds

Free proof of authorship: SHA-256 hash, UTC timestamp and a Polygon blockchain record. Your file is not stored.

Add to ChromeProtect a file