Authenticating Email Evidence
Issues and solutions in email evidence.
To authenticate an email, a forensic examiner matches it against independent records and analyzes its technical data. Redundancy checks compare the sender’s copy, the recipient’s copy, and mail server records. Header and DKIM (DomainKeys Identified Mail) analysis traces the message’s transmission path and evaluates whether the message was authenticated by the sending domain. Together, that evidence supports authentication under Federal Rule of Evidence 901.
Email evidence can prove valuable to a case. However, it is important to thoroughly authenticate emails used in litigation. Failure to prove the validity of an email item could render a crucial piece of evidence inadmissible in court.
Can an Email Be Altered Without Detection?
Email content quoted inside a reply or forward chain is only a copy, and it is the easiest part of an email to challenge. It is easy for any user to modify content included within a reply or forward chain. This content is replicated with each reply but not preserved, allowing anyone in the chain to change the email content in their copy before forwarding it along. A reply or forward also creates a new email with its own header information. Much of the original message’s forensic metadata—such as routing information, authentication results, and other server-generated header data—is not preserved in the new message. As a result, the original email from the sender’s or recipient’s mailbox generally provides stronger evidence than the quoted content in a reply or forward chain.
A forwarded chain may also raise hearsay objections, which are a separate question from authenticity.
How Does Redundancy Prove an Email Is Authentic?
A single email can be validated based on confirmation from other email sources. When an email message is successfully sent, related records may exist in the sender’s mailbox, the recipient’s mailbox, and on the email servers and security systems through which the message traveled. Comparing these independent records can help confirm that the email was transmitted and that all important information and metadata (recipient, sender, attached files, email format) are consistent across available sources and align with corresponding records maintained by other custodians or other devices. Attachments carry their own metadata as well; see whether metadata remains in email attachments.
Deleted emails can provide another source of evidence that may be compared with copies maintained by another custodian or email system. Even after an email is deleted from a computer, portions of the message may remain within the local email database, such as an OST or PST file, and may be recoverable using forensic tools. As additional email activity occurs, however, the database may reuse or overwrite the space previously occupied by deleted records, reducing the likelihood of recovery over time.
Forensic examination may also identify older copies of the email database that predate the deletion. Depending on the computer and its configuration, these may exist in system snapshots, Volume Shadow Copies, backups, or other historical data. In some cases, an earlier copy of the OST or PST may contain the email in its original, undeleted state.
Analysis of a forensic image of a device can therefore reveal both remnants of deleted email and historical copies of email data that may not be available through examination of a live email account alone.
The use of email applications on mobile devices is common with the adoption of BYOD (Bring Your Own Device) policies. Email copies maintained on these devices can provide an additional source of corroborative email evidence.
How Do You Prove Who Sent an Email?
One tactic used to undermine email evidence is to question the true author of the message. Anyone with the email password or access to a logged-in device can send a message from someone else’s account. Techniques such as email spoofing might give an email the appearance of having been sent from one address when it is actually sent from another address for malicious purposes.
What Does Email Header Analysis Reveal?
Authorship must be demonstrated through both the email header metadata and the content of the email itself. Email header analysis helps determine where a message originated, how it traveled, and whether available authentication information is consistent with the purported sender. Examiners evaluate fields such as Received, Sender, Return-Path, Message-ID, Content-Type, and the authentication results to reconstruct the message’s transmission path and identify inconsistencies or other relevant evidence.
An email header commonly contains a DKIM signature. DKIM uses cryptography to authenticate that an email from a domain was authorized to come from that source. The sending server signs selected header fields and a hash of the message body. A receiving server, or an examiner, can retrieve the domain’s public key from DNS (Domain Name System) and uses it to verify the signature if the signature validates, the signed content has not changed since the DKIM signature was created and the message was sent.
Emails must be examined contextually within the chain of a conversation and the system on which they were generated. By obtaining a forensic image of the device from which an email was sent, data indicating login times, internet behavior, and credentials used might be retrieved to compare with expected user behavior.
Can Email Headers Be Faked?
Some can. A sender can forge the visible From address and certain header fields created before a message leaves their control. Fields added later by receiving servers, DKIM signatures, and server logs held by third parties are much harder to fake. DKIM signatures, routing information, and available server logs can help determine whether a message was authenticated and whether it changed during transmission. For this reason, an examiner evaluates the header as a whole and, when possible, compares it with independent records from other systems.
What Federal Rules of Evidence Apply to Email?
The legal framework surrounding email authentication is nuanced. The rules below come up most often in federal court. Many states have adopted similar rules.
| Rule | What it covers | How it applies to email |
| FRE 901(a) | The proponent must show the item is what they claim it is | The baseline test for every email exhibit |
| FRE 901(b)(4) | Authentication by distinctive characteristics and circumstances | Content, signature blocks, context and reply patterns that tie an email to its author |
| FRE 901(b)(9) | Authentication by evidence of a process or system that produces an accurate result | Testimony explaining how mail servers, headers and DKIM records work |
| FRE 902(13) | Self-authentication of records generated by an electronic process, by certification of a qualified person | System-generated records, such as server logs, without live testimony |
| FRE 902(14) | Self-authentication of data copied from a device or file, verified by digital identification such as a hash value | Forensically collected email, with a certification from the examiner |
| FRE 803(6) | The business records exception to the hearsay rule | Can allow an email’s contents to be admitted for their truth. It is a hearsay question, separate from authentication. |
For example, FRE Rule 803(6) provides that when a document is generated according to regular activities conducted by a business or organization it may be excepted from the rule against hearsay. If an email is sent when a user is expected to be present at a workstation and sent with a business-associated email signature, those facts can help authenticate the email under FRE 901, and the email may also qualify as a business record under FRE 803(6) if its elements are met.
Rules 902(13) and 902(14) took effect December 1, 2017. They let a qualified examiner’s certification stand in for live foundation testimony, provided the other side gets advance notice. A frequently cited federal discussion of these issues is Lorraine v. Markel American Insurance Co., 241 F.R.D. 534 (D. Md. 2007), where the court declined to consider unauthenticated exhibits, including emails, and denied both sides’ summary judgment motions.
Other Email Header Artifacts Used for Authentication
Message-ID
A Message-ID is a unique identifier assigned to an email when it is created. Examiners can compare Message-IDs across sender, recipient, and server records to help determine whether different records relate to the same message.
SPF and DMARC
SPF (Sender Policy Framework) and DMARC (Domain-based Message Authentication, Reporting, and Conformance) are additional email-authentication technologies that help evaluate whether a message was sent through authorized systems and whether it was altered in transit. SPF checks whether the sending server is authorized for the domain, DKIM uses a cryptographic signature to verify signed portions of the message. DMARC evaluates SPF and DKIM results and checks whether the authenticated domain matches the domain shown in the email’s visible From address. If either SPF or DKIM passes with proper alignment, the message can pass DMARC.
Email Evidence FAQs
Is email admissible in court?
Yes, if it is relevant, properly authenticated and survives any hearsay objection. Authentication under FRE 901 is usually the first hurdle, and forensic analysis of headers and server records is often what clears it.
How do you prove an email is real?
By matching it against independent records, such as the recipient’s copy and mail server logs, and by analyzing its headers and DKIM signature. Context, such as content and timing, supports the technical findings.
Can email headers be faked?
Some fields can be forged by the sender. Fields added by receiving servers, DKIM signatures and third-party server logs are much harder to fake. For this reason examiners compare multiple independent sources when evaluating an email’s authenticity.
Can a forwarded email be used as evidence?
It can, but it is weaker. Anyone in the chain can edit the quoted text, so the original message from the sender’s or recipient’s mailbox is stronger evidence.
What is DKIM in email forensics?
DKIM is a cryptographic signature the sending domain adds to an email. If it validates against the domain’s public key, the signed parts of the message have not changed since the signature was created and the message was sent.
When Email Authenticity Is Contested
If the authenticity of an email is disputed in your matter, ArcherHall’s examiners can analyze headers and server records, collect the evidence with a documented chain of custody, and testify to the findings. Contact ArcherHall to discuss your case, or learn more about our eDiscovery services.