P26-electronic-evidence-certificate.html" target="_blank" style="color:#3D61D2; text-decoration:underline;">Section 63 BSA / Section 65B electronic-evidence certificate (or a dedicated Email Forensics certificate) that records the source mailbox, the export method and the integrity hashes, with an explicit MATCH verification against each exhibit. The output follows the familiar Part A / Part B Schedule form — Part A describing the electronic record and how it was produced, Part B listing the source and the hash values — so it reads the way a court expects. If you want to see the structure first, this Section 65B certificate format with an example is a useful reference, and you can read more about what an evidence integrity certificate contains.

Step 6 — Sign and Timestamp

Finally, make the certificate tamper-evident. e-Dex can apply a PAdES digital signature using a Digital Signature Certificate (DSC) on a USB token, binding the signer's identity to the document so any later edit is detectable. It can also attach an RFC-3161 trusted timestamp from a Time-Stamping Authority, providing independent proof that the certificate existed in that exact form at that moment. Both steps run from your own Windows machine; only the timestamp touches the internet, and everything else stays fully offline.

P26 replaced the Indian Evidence Act 1872 and came into force on 1 July 2024; Section 63 BSA is the successor to Section 65B of the old Act, and both require a certificate for electronic records. In Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal (2020) the Supreme Court held that a Section 65B(4) certificate is a mandatory pre-requisite for admitting secondary electronic evidence, while recognising relief where a party genuinely cannot obtain it because the device or record is in someone else's possession. That is general information and the law continues to evolve under the BSA, so you must verify the current position. e-Dex helps you produce a well-structured, integrity-backed certificate; it is a tool, not legal advice and not a substitute for counsel. Who must depose to the certificate, how the email was lawfully obtained, and exactly how it is tendered all depend on the facts of your matter and on the text of the provision as it stands. For a broader walkthrough, this guide to electronic-evidence certificates in India is a good starting point. Always read the current provision and take advice where the stakes warrant it — e-Dex does not guarantee that any record will be admitted, because that is for the court to decide.

Frequently Asked Questions

Are emails admissible as evidence in India?
Emails are electronic records, so under Section 63 of the Bharatiya Sakshya Adhiniyam 2023 (the successor to Section 65B of the Indian Evidence Act) they generally need to be accompanied by a certificate to be admitted. They are not automatically admissible just because they are printed out. e-Dex helps you produce a well-structured certificate, but admissibility is ultimately for the court to decide on the facts.

Is an email printout or screenshot enough for court?
Usually not on its own. A printout or screenshot is secondary evidence that can be edited and carries no proof of the sender, the routing or the timestamps. Indian courts generally expect electronic records to be supported by a certificate. A stronger approach is to export the original message with its full headers, hash it and certify the resulting file.

How do I get a Section 65B / 63 certificate for an email?
Preserve the mailbox, export the original message with full headers as a .eml or .msg file, record the account and parties, hash the file with a tool such as e-Dex, and then generate a Section 63 BSA / Section 65B electronic-evidence certificate recording the source mailbox and the integrity hashes with a MATCH verification. You can then sign it with a Digital Signature Certificate and apply a trusted timestamp.

What are email headers and why do they matter as evidence?
Email headers are the hidden technical lines at the top of a message. They record the sender and recipient addresses, the Received hops as the mail travelled between servers, the date and time, and authentication results such as SPF, DKIM and DMARC. They are what tie a message to a real route and a real account, which is why a header-less printout is far weaker evidence.

Can emails be forged or altered?
Yes. The visible body and even the From address can be spoofed or edited, and a printout can be retyped entirely. That is why headers and integrity hashing matter. Hashing the exported .eml or .msg does not by itself prove the message is genuine, but it fingerprints the exact bytes so anyone can confirm the file has not changed since it was certified, and the headers help an examiner assess authenticity.

Conclusion

An email can decide a case — but only if you present it as more than a printout. Preserve the mailbox, export the original message with its headers, record the particulars, hash the file and wrap it in a signed, timestamped Section 63 certificate, and you give the court something it can actually verify. Let your mail client or a forensic examiner produce the export, then let e-Dex — the Digital Evidence Integrity Suite hash the exhibits, capture the details and generate a court-ready certificate on your own Windows machine, fully offline and free to try.