Examinations
How do you authenticate emails in court, and what does a forensic examiner check?
An email is authenticated in a US court by evidence sufficient to support a finding that it is what the party offering it claims, under Rule 901(a). Courts accept testimony of the sender or recipient, distinctive characteristics such as the address, nickname and content, and comparison with emails already authenticated. When authorship or alteration is disputed, an examiner reads the headers, the server trace and any DKIM signature in the native message file.

What does Rule 901 require to authenticate an email?
Evidence sufficient to support a finding that the email is what the proponent claims it is. The judge asks whether a jury could reasonably find the email genuine, and the jury then decides how much weight it gets.
Rule 901(a) of the Federal Rules of Evidence states that "the proponent must produce evidence sufficient to support a finding that the item is what the proponent claims it is." Rule 901(b) lists examples, among them "Testimony that an item is what it is claimed to be" (901(b)(1)) and "Evidence describing a process or system and showing that it produces an accurate result" (901(b)(9)). No rule written only for email exists; the same examples apply to a message, a letter or a photograph.
In United States v. Safavian, 435 F. Supp. 2d 36 (D.D.C. 2006), Judge Paul L. Friedman ruled on approximately 260 emails that the government sought to admit. He wrote that "[t]he threshold for the Court's determination of authenticity is not high." The question is whether the proponent has "offered a foundation from which the jury could reasonably find that the evidence is what the proponent says it is." The court does not have to find that the emails are genuine; it decides whether a jury could.
Authentication is one of several hurdles. In Lorraine v. Markel American Insurance Co., 241 F.R.D. 534 (D. Md. 2007), Chief Magistrate Judge Paul W. Grimm listed five questions for electronically stored information: relevance under Rule 401, authenticity under Rule 901, hearsay under Rules 801, 803, 804 and 807, the original writing rule under Rules 1001 to 1008, and the balance of probative value against unfair prejudice under Rule 403.
What happens if emails are simply attached to a motion?
The court may refuse to consider them. In Lorraine both sides attached unauthenticated emails to cross-motions for summary judgment, and the court denied both motions without prejudice and allowed resubmission with proper evidentiary support.
In Lorraine the plaintiffs and the insurer, Markel, filed cross-motions for summary judgment. The court found that neither side supported its motion with admissible evidence: "none of the documentary evidence presented is authenticated by affidavit or otherwise." The emails were "not authenticated, but instead were simply attached to the parties' motions as exhibits."
A letter order of February 7, 2007 denied both motions without prejudice and allowed the parties to resubmit them with proper support. The opinion of May 4, 2007 explains that ruling and sets out how electronically stored information can be authenticated.
A party preparing a motion can attach a declaration from a witness with knowledge, such as the sender, the recipient or the custodian of the mailbox, stating what the email is and how the copy was made. The declaration supplies the testimony that Rule 901(b)(1) describes.
Who can testify that an email is genuine?
A witness with personal knowledge: the author, the recipient, or a person who saw the email written, sent or received. Authors writing on digital evidence add that production of an email in discovery may itself authenticate it.
Rule 901(b)(1) covers testimony that an item is what it is claimed to be. In "Authenticating Digital Evidence", published in the Baylor Law Review, volume 69 (2017), United States District Judge Paul W. Grimm, Professor Daniel J. Capra, Reporter to the Judicial Conference Advisory Committee on Evidence Rules, and Gregory P. Joseph list examples of such witnesses: the author of the email, a witness who saw the email authored or received, and a recipient who confirms that the chain of messages accurately represents the conversation.
The same authors note that production of an email in response to a sufficiently descriptive discovery request "may serve in itself to authenticate the email." They also list a certification by a custodian under Rules 902(11) or (12) for business records, with the warning that emails, even of a business, "do not automatically qualify as business records."
When the author denies writing the message or the recipient is the opposing party, a cooperative witness with knowledge may not exist, and the proponent turns to circumstantial evidence under Rule 901(b)(4).
Which details authenticate an email when no witness saw it written?
Rule 901(b)(4) accepts appearance, contents, substance, internal patterns and other distinctive characteristics taken together with the circumstances. Courts have relied on the sender's address, a nickname, details the sender would have known and follow-up phone calls.
In United States v. Siddiqui, No. 98-6994, decided by the Eleventh Circuit on December 15, 2000, the case arose from Mohamed Siddiqui's conduct regarding the National Science Foundation's Waterman Award and the NSF investigation of it. Emails asked one colleague to "please tell good words about me" if the NSF called and asked another to tell the NSF that Siddiqui had permission to use his name. On appeal Siddiqui challenged the ruling that the emails were authenticated.
The court listed the facts that tied the emails to him. Each bore his email address, and when one recipient, von Gunten, replied, the reply function of von Gunten's own mail system automatically entered Siddiqui's address. The content showed the author "to have been someone who would have known the very details" of the award matter and the NSF investigation. The emails referred to the author as "Mo," a nickname both recipients recognized as Siddiqui's. Both recipients testified that Siddiqui phoned them soon after the emails arrived and made the same requests. The court held that the district court "did not abuse its discretion in ruling that the documents were adequately authenticated."
In Safavian the court relied on similar features. "The e-mails in question have many distinctive characteristics, including the actual e-mail addresses containing the '@' symbol," most of which contained the name of the person connected to the address. Names appeared in signature blocks, and the messages discussed identifiable matters that tied them to the sender and recipient.
Can a jury compare a disputed email with emails already authenticated?
Yes. In Safavian the court held that emails whose source was unclear could be authenticated under Rule 901(b)(3) by comparison with emails already authenticated through their distinctive characteristics.
Some messages in Safavian carried an address that did not show a name. The court held that such emails "can be authenticated under Rule 901(b)(3)" by comparing them with emails already authenticated under Rule 901(b)(4). Its example was an address that the jury could connect to the defendant by comparing it with an email that carried his signature block.
Grimm, Capra and Joseph describe the same method: the authenticity of an email "can be determined by the trier of fact by comparing the email in question" with emails already authenticated. For a party with a large production, this means a few emails proved through a witness can carry many others that share the same address, signature block or thread.
Comparison works only on the features that the copies preserve. A printout shows the display name and the address the mail program chose to show; the native file also holds the full headers, which an examiner can compare across messages.
Does the possibility that an email was altered keep it out of evidence?
No. In Safavian the court held that the possibility of alteration cannot be the basis for excluding emails. Absent specific evidence of alteration, the argument goes to the weight the jury gives the evidence.
The defendant in Safavian argued that the trustworthiness of the emails could not be shown, particularly of emails embedded within other emails. The court accepted that earlier emails included in a chain may be altered and answered that "[t]he defendant's argument is more appropriately directed to the weight the jury should give the evidence, not to its authenticity."
The court added that "[t]he possibility of alteration does not and cannot be the basis for excluding e-mails," and that, "[a]bsent specific evidence showing alteration," it would not exclude embedded emails because of that possibility.
The phrase "specific evidence showing alteration" defines the task for the opposing side. A general statement that emails can be faked does not exclude a message. A report that compares the printout with the native file, reads the headers and checks the signature of the sending domain can supply specific evidence, or it can find none.
What does an examiner read in the headers of an email?
The trace lines that each mail server adds on receipt, with the sending host and the date and time, plus the metadata of the message file. Lorraine treats metadata as a distinctive characteristic under Rule 901(b)(4).
RFC 5321, Simple Mail Transfer Protocol (J. Klensin, October 2008), requires a server that receives a message for delivery or further processing to "insert trace ('time stamp' or 'Received') information at the beginning of the message content." The trace record indicates the identity of the host that sent the message, the host that received it and the date and time of receipt. The standard states: "An Internet mail program MUST NOT change or delete a Received: line that was previously added to the message header section."
Each server on the route adds its own line above the earlier ones, so the headers of a delivered message hold a chain of hosts and timestamps. An examiner compares that chain with the date shown in the body of the message, with the logs of the servers involved and with copies of the same message held by other recipients.
In Lorraine Judge Grimm wrote that "metadata is a distinctive characteristic of all electronic evidence that can be used to authenticate it under Rule 901(b)(4)" and cautioned that metadata is not conclusive. Grimm, Capra and Joseph list among the circumstances that support authorship "an email's hash values" and "testimony from a forensic witness that an email issued from a particular device at a particular time."
Can a DKIM signature prove that an email was not changed?
A valid DKIM signature means that the signed headers and body have not changed since the sending domain signed them. It identifies the domain, not the person, and a failed check can come from changes made in transit.
RFC 6376, DomainKeys Identified Mail (DKIM) Signatures (Internet Standard STD 76, September 2011), permits "a person, role, or organization that owns the signing domain to claim some responsibility for a message." A verifier checks the signature by querying the signer's domain for the public key.
The signature carries tags that an examiner records. The d= tag names the signing domain, bh= is "the hash of the canonicalized body part of the message," h= lists the header fields presented to the signing algorithm, and t= is "the time that this signature was created." Section 1.5 states the limit: "Verifying the signature asserts that the hashed content has not changed since it was signed and asserts nothing else."
A failed check is not proof of forgery. Section 3.4 notes that "Some mail systems modify email in transit, potentially invalidating a signature," and section 5.3 warns that conversion to 7-bit form will break DKIM signatures. A passing check ties the message to the domain that signed it, which still leaves open who in that organization used the account; that question returns to Rule 901(b)(4) and the witnesses.
Can an email be self-authenticated with a hash certificate?
A copy can. Rule 902(14) makes data copied from a device, storage medium or file self-authenticating when a qualified person certifies a process of digital identification, after written notice. The certificate does not settle authorship.
Rule 902(14) covers "Data copied from an electronic device, storage medium, or file, if authenticated by a process of digital identification," as shown by a certification of a qualified person. The proponent must meet the notice requirements of Rule 902(11): before the trial or hearing, the proponent "must give an adverse party reasonable written notice" and must make the record and certification available for inspection.
The 2017 committee note explains the hash method: "If the hash values for the original and copy are the same," then "it is highly improbable that the original and copy are not identical." A certificate under Rule 902(14) therefore proves that the mailbox export or message file produced in court is the same data that was collected.
The note also sets the limit. "A certification under this Rule can only establish that the proffered item is authentic," and "The opponent remains free to object to admissibility of the proffered item on other grounds." Its example concerns a hard drive: the defendant "can still challenge whether the information on the hard drive was placed there by the defendant." For an email, a hash certificate proves the integrity of the copy, and the question of who wrote the message stays with Rule 901.
How do you get emails in a form an examiner can check?
Request them in native form. Rule 34 lets the requesting party specify the form of electronically stored information, and the 2006 committee note bars conversion that makes the information harder to use or strips its electronic searchability.
Rule 34(a)(1)(A) of the Federal Rules of Civil Procedure reaches "any designated documents or electronically stored information," and Rule 34(b)(1)(C) provides that the request "may specify the form or forms in which electronically stored information is to be produced." If the request names no form, Rule 34(b)(2)(E)(ii) requires production "in a form or forms in which it is ordinarily maintained or in a reasonably usable form or forms."
The 2006 committee note limits conversion. The option to produce in a reasonably usable form "does not mean that a responding party is free to convert electronically stored information from the form in which it is ordinarily maintained to a different form that makes it more difficult or burdensome for the requesting party to use the information efficiently in the litigation." Information kept in a searchable form "should not be produced in a form that removes or significantly degrades this feature."
A PDF printout of an email shows what the mail program displayed. The native message file or mailbox export also holds the full headers, the trace lines and any DKIM signature. A request that names native format with full headers, and the mailbox export where the account itself is in question, gives the examiner the material needed for the checks described above.
Does authentication make an email admissible?
No. An authenticated email offered for its truth still faces the hearsay rule. A party's own email comes in as an opposing party's statement under Rule 801(d)(2), and business records status is not automatic.
Rule 801(c) defines hearsay as a statement that the declarant does not make while testifying at the current trial or hearing and that "a party offers in evidence to prove the truth of the matter asserted in the statement." Under Rule 801(d)(2)(A) a statement offered against a party that "was made by the party in an individual or representative capacity" is not hearsay, and under 801(d)(2)(B) the same holds for a statement "the party manifested that it adopted or believed to be true."
Safavian applied both. "The statements attributed directly to Mr. Safavian come in as admissions by a party opponent under Rule 801(d)(2)(A)." Some forwarded emails came in as adoptive admissions where the defendant manifested an adoption of the forwarded statements; other forwarded emails did not show that adoption and were not admitted on that basis.
Grimm, Capra and Joseph caution that emails, "even of a business, do not automatically qualify as business records." The 902(14) committee note makes the same separation from the other side: a certificate settles authenticity and leaves the opponent free to raise hearsay and other objections.
What does IAE do when emails or electronic documents are disputed in a US case?
An IAE examiner prepares a digital forensics report on the client's questions about messages, documents and files, or reviews the opposing forensic report. The document is issued in up to 5 business days.
The IAE digital forensics page covers three groups of questions. For messages, the examiner extracts the messaging database from the phone or computer and compares screenshots with it: sender, timestamps, deleted and edited messages, attachments. For documents and files, the examiner establishes creation and modification dates from document and file system metadata, looks for traces of editing in PDFs and images, and compares a copy with the original by hash value. For software and devices, the examiner looks at event logs, browser history and traces of connected USB drives.
For a review of the opposing report the examiner checks whether another examiner could repeat the work from the report: whether the image and the source have matching hash values, which tool and version extracted the data, whether timestamps were read in the right time zone and whether each conclusion follows from the data, since Rule 702(d) requires a reliable application of the method to the case.
IAE confirms the questions, the devices and how the data reach the examiner before work starts. The format, cost, deadline and the specialist from the public IAE registry are confirmed within one business day, and the client approves the candidate and the CV. The signed document is issued in up to 5 business days, with a 48-hour rush for tight deadlines. IAE is not a law firm; whether an email is admitted is decided by the court.
Sources
- Federal Rules of Evidence, Rule 901, Authenticating or Identifying Evidence (Cornell LII)
- Federal Rules of Evidence, Rule 902, Evidence That Is Self-Authenticating, with 2017 committee notes (Cornell LII)
- Federal Rules of Evidence, Rule 801, Definitions That Apply to This Article; Exclusions from Hearsay (Cornell LII)
- Federal Rules of Civil Procedure, Rule 34, with 2006 committee note (Cornell LII)
- United States v. Siddiqui, No. 98-6994, 235 F.3d 1318 (11th Cir. Dec. 15, 2000), opinion (U.S. Court of Appeals for the Eleventh Circuit)
- United States v. Safavian, 435 F. Supp. 2d 36 (D.D.C. 2006), opinion text
- Lorraine v. Markel American Insurance Co., 241 F.R.D. 534 (D. Md. 2007), opinion text
- Grimm P. W., Capra D. J., Joseph G. P. Authenticating Digital Evidence. Baylor Law Review, vol. 69, 2017 (U.S. District Court, S.D. Tex.)
- RFC 5321, Simple Mail Transfer Protocol, J. Klensin, October 2008 (RFC Editor)
- RFC 6376, DomainKeys Identified Mail (DKIM) Signatures, STD 76, September 2011 (RFC Editor)
Read also
All articles
Electronic signature disputed: how do you prove who signed, and what does a forensic examiner check?
An electronic signature has legal effect, but the party that relies on it must show that it was the act of the person named. In Fabian v. Renovate
How do you authenticate social media posts for court, and what does a forensic examiner add when the account is disputed?
A printout of a social media page proves that the page existed. It does not prove who wrote the post. In 2014 the Second Circuit vacated a conviction
Spyware on a phone: how does a forensic examiner find it, and what can the evidence be used for?
A forensic examination for spyware establishes whether a monitoring app is on the phone, when it appeared, what it collected and where it sentExpert examinations
Ready to discuss your case?
Send the materials: the secretariat will confirm the format, cost, deadline and the specialist within one business day.

