Validate a blockchain-signed document
Did you receive a signed document and want to verify it is authentic? Validate its SHA-256 hash against the Avalanche blockchain in seconds. Free, no account, no downloads — the document is verified directly against a public, decentralized network.
How do I verify that a document was signed in Validocus?
Verification is public, free, and requires no account. There are two modes:
Validation by file
Upload the PDF to the public validator and the system computes the SHA-256 hash locally in your browser (the file is never uploaded to any server) and then queries the Avalanche blockchain to check whether that hash is registered.
Validation by hash
If you already have the document's SHA-256 hash (from the evidence certificate that ships with each signature), paste it directly. Useful for programmatic integrations and audits that need to reproduce verification without having the PDF on hand.
What information validation returns
When the hash exists on the chain, you get a panel with full traceability: the exact timestamp when the hash was registered on the Avalanche blockchain; the list of contract signers with email and role; the date and time each signer completed their signature; the contract status (completed, partially signed, expired, rejected); the blockchain transaction hash (clickable to open the public explorer and inspect the record independently); the final version of the signed document (not the initial version, but the PDF with all signatures embedded).
Public verification on the Avalanche blockchain
The Validocus validation is simply a friendly interface on top of a public record on the Avalanche blockchain. Anyone can verify the hash independently without going through our platform:
You compute the SHA-256 of the PDF with any tool (sha256sum on Linux, CertUtil on Windows, openssl dgst on Mac), look up that hash in a public Avalanche explorer (SnowTrace or others), and check the block, timestamp, and transaction where it was registered. This means the proof survives Validocus: even if the company disappears, the record remains immutable on a decentralized network we do not control. That is the difference between evidence custodied by a third party (vulnerable) and decentralized evidence (irrefutable).
Use cases
Banks and financial institutions
Verification of deduction authorizations, electronic promissory notes, and signed credit contracts. The bank confirms the authorization is authentic and untampered before processing the debit or disbursement.
Human Resources validating candidates
A new employer can validate the employment certification presented by a candidate without contacting the previous employer. The public blockchain verification confirms authenticity in seconds.
Court proceedings and forensic experts
Attorneys, judges, and experts validate documents submitted as documentary evidence. The evidence chain (hash + blockchain + video + timestamp) facilitates admissibility under the General Procedure Code.
B2B integrations and compliance
Platforms that receive signed contracts from external partners can validate programmatically via API that the document is authentic before enabling access to resources or disbursing payments.
How does it work?
- 1
Obtain the signed PDF or its SHA-256 hash (you'll find it on the evidence certificate that ships with every signed document).
- 2
Go to the Validocus public validator (validocus.com/en/#validator) — free and no account.
- 3
Upload the PDF or paste the hash. The browser computes the hash locally; the file is never uploaded to any server.
- 4
Validocus queries the Avalanche blockchain and returns the associated record (signers, timestamp, transaction) or tells you the hash isn't registered.
- 5
If you want independent verification, copy the tx hash and check it directly on a public Avalanche explorer.
Frequently asked questions
How do I validate a document signed in Validocus?
You have two options. By file: go to the validator at validocus.com/en/#validator, upload the PDF, and the system computes its SHA-256 hash and looks it up on the Avalanche blockchain. By hash: if you already have the document's hash (for example, copied from the evidence certificate), paste it directly and get the result. Validation is free and requires no account — anyone can verify the authenticity of a signed document.
What information does validation return?
If the document is registered: the exact registration timestamp, the list of signers with email, when each one signed, the Avalanche blockchain transaction hash (clickable to open the public explorer), the document version, and the contract status (signed, partial, expired). If the document is not registered: the system informs you that the hash isn't on the chain — either it wasn't signed in Validocus or the file was modified after signing.
What does it mean if verification fails?
Two main scenarios. One: the document you're validating differs from the original signed file — even by a byte (an added comment, a metadata change, an added page), so the SHA-256 hash no longer matches the blockchain record. This is exactly what the system detects: any post-signature modification. Two: the document never went through Validocus, was signed on another platform, or wasn't signed electronically at all.
Can I verify the document without Validocus, directly on blockchain?
Yes — and that is precisely the guarantee of the system. The hash is recorded on the public Avalanche blockchain, accessible to anyone via an explorer (snowtrace.io or others). Validocus is not the custodian of the proof: the record lives on a decentralized network that we do not control. If Validocus disappeared tomorrow, the registered hashes would remain publicly verifiable forever.
How reliable is the Avalanche blockchain for this?
Avalanche is a public blockchain with Snowman++ consensus, validated by thousands of independent nodes worldwide. To reverse a record, someone would need to coordinate a majority of validators, which is economically unfeasible. The document's SHA-256 hash is written on Avalanche's C-Chain with an immutable timestamp. The probability of reversing a post-confirmation timestamp is essentially zero.
Who uses this validation in practice?
Anyone who receives a signed document and wants to confirm it before acting on it. Typical cases: banks verifying deduction authorizations, new employers verifying a candidate's employment certifications, attorneys validating disputed contracts, judges accepting electronic documentary evidence, B2B integrators confirming a signed contract before enabling access to a service.
Validate a document free now
No signup, no card, no downloads. Direct verification against blockchain.
Go to the public validator