Article
Why a Hash Needs a Certificate to Be Useful in Court
A bare hash — a 64-character hex string sitting in an email — means very little to a court. Nobody can see, from the string alone, which file it belongs to, which algorithm produced it, when it was computed or who computed it. A certificate supplies exactly that context. It ties the hash to a specific file, records the method (the algorithm), fixes the time it was computed, and names the person responsible. When that certificate is signed and timestamped, any later alteration becomes detectable. This is why an evidence integrity certificate is the natural companion to a hash: it converts a meaningless string into reviewable, defensible documentation. How any such document is then tendered and weighed remains for the court.
P26 (formerly Section 65B of the Indian Evidence Act). This is general information and not legal advice.
What does a hash value actually prove?
A cryptographic hash proves integrity: that a file is bit-for-bit identical to a previously recorded state.
If the recomputed hash matches the recorded value, the file is unchanged. A hash does not prove who created
the file, where it came from, when it was made, or that its contents are truthful. Those questions are
answered by witnesses, metadata, acquisition records and chain of custody, not by the hash itself.
Does a hash value need a certificate to be useful in court?
Generally yes. A bare hash string means little to a court without context. A certificate ties the hash to a
specific file, records the algorithm used, the time it was computed and the person who computed it, and
ideally is signed and timestamped. That binding is what turns a long hex string into reviewable, defensible
documentation. How any such document is tendered and weighed remains for the court to decide.
How is a hash value related to Section 63 BSA or Section 65B?
Section 63 of the BSA 2023 (formerly Section 65B of the Indian Evidence Act) sets out the certificate
requirement for electronic records in India. A hash value is one part of the integrity story that supports
such a record; the statutory certificate captures device, acquisition and deponent details around it. The
hash corroborates that the record is unaltered, but it does not replace the certificate or any other
statutory requirement.
How can I make hash-based evidence more defensible?
Record the algorithm used, compute the hash at the moment of collection, sign and timestamp the result,
keep a documented chain of custody, and allow independent re-verification by a third party. e-Dex produces
a signed, timestamped integrity certificate offline and exposes a free public verifier so anyone can
recompute and check the hash. Following good practice strengthens the integrity story but does not by
itself guarantee admissibility, which is for the court to decide.
Conclusion
So, are hash values admissible as evidence? A hash is powerful proof of integrity — that a file is unchanged — but it is not, by itself, proof of authorship, origin or truth, and it is the court that decides what is admitted. Used well, a hash sits inside a larger structure: computed at collection, wrapped in a signed and timestamped certificate, backed by a chain of custody, and open to independent re-verification. That is the difference between a string nobody can interpret and documentation a court can actually weigh. You can produce a signed, timestamped, independently verifiable integrity certificate in minutes, offline, on a single Windows machine with e-Dex — the free Digital Evidence Integrity Suite. Download it here. This article is general information and not legal advice; for any specific matter, take advice from qualified counsel.