Verify a file
Drop a file below to confirm it matches a previously recorded ProofLedger fingerprint.
Option 1: Verify by file
Upload the file. We’ll hash it and check for a matching proof.
Option 2: Verify by SHA-256 hash
Paste a 64-character SHA-256 hash to check for a matching proof.
ProofLedger verifies that a SHA-256 hash was recorded at a specific time. It does not establish authorship, ownership, intent, or legal rights.
Verification result
No result
No verification run yet.
Submit a file or SHA-256 hash to see if there is a matching ProofLedger record.
Canonical verification:
This page is ProofLedger’s canonical authority surface for verification. It confirms whether the SHA-256 fingerprint shown matches an immutable ProofLedger evidence record and displays the recorded timestamps for that record. Proof certificates are derived artifacts and do not override this verification page.
What is fixed: Once recorded, the SHA-256 fingerprint and the record creation timestamp are not edited or overwritten. Later review states, disputes, or administrative notes do not change the original hash or timestamp.
Record status meaning:
APPROVED — Procedural review is complete. Displayed timestamps and any listed anchors are final.
PENDING — The record exists and is immutable, but procedural review and/or anchoring is not yet complete.
CONTESTED — The record is final, with an additive dispute or administrative annotation. Original data is unchanged.
DENIED — The submission did not meet procedural requirements. The submission event remains recorded and auditable.
What this does not verify: authorship, ownership, intent, permission, liability, legal rights, or identity of the creator. ProofLedger does not adjudicate disputes.
Independent checks: Recompute the SHA-256 hash locally and compare it to the fingerprint shown. If on-chain references are listed, confirm them using public blockchain explorers. On-chain anchoring is an independent reference; its absence does not imply the record is edited or deleted.
What is fixed: Once recorded, the SHA-256 fingerprint and the record creation timestamp are not edited or overwritten. Later review states, disputes, or administrative notes do not change the original hash or timestamp.
Record status meaning:
APPROVED — Procedural review is complete. Displayed timestamps and any listed anchors are final.
PENDING — The record exists and is immutable, but procedural review and/or anchoring is not yet complete.
CONTESTED — The record is final, with an additive dispute or administrative annotation. Original data is unchanged.
DENIED — The submission did not meet procedural requirements. The submission event remains recorded and auditable.
What this does not verify: authorship, ownership, intent, permission, liability, legal rights, or identity of the creator. ProofLedger does not adjudicate disputes.
Independent checks: Recompute the SHA-256 hash locally and compare it to the fingerprint shown. If on-chain references are listed, confirm them using public blockchain explorers. On-chain anchoring is an independent reference; its absence does not imply the record is edited or deleted.
1. Compute the SHA-256 fingerprint of the file you want to validate (any standard hashing tool works).
2. Verify that the SHA-256 fingerprint exactly matches the value shown in the verification results.
3. Confirm anchoring using public chain data: use the Polygon and/or Bitcoin transaction links to validate the on-chain references. For Bitcoin batches, verify the Merkle root references the batch that includes this proof.