How to Tell if an Email Was Backdated or Faked
A plain-English guide to how digital forensic examiners use email headers and metadata to detect whether a message was backdated, altered, or fabricated, and when to bring in a professional.
An email can be shown to have been backdated or faked by examining its hidden header information. Beyond the date and sender you see at the top, every email carries a behind-the-scenes record of the servers it passed through and the times it was handled. When that internal record conflicts with the date or origin the message claims, it is a common indicator of tampering.
An email carries a hidden delivery record
The part of an email you normally see, the sender, date, and subject, is only the surface. Behind it sits the email header, a detailed technical record that email systems add as a message travels from sender to recipient. Most people never look at it, which is exactly why it is valuable in an examination.
An email's header and metadata can record:[1]
- The chain of servers the message passed through, each stamped with its own date and time in the header's Received trace fields, which must not be reordered.[1]
- Originating information that can point to where a message actually came from. Each server's Received field records the system it got the message from, including name and IP address, and the date and time.[2]
- A unique message identifier (the Message-ID field) assigned when the message is created.[3]
- The origination date the sender's system recorded (the Date field), which reflects when the creator marked the message ready to send, and can be compared against the server timestamps.[1]
Common signs an email was backdated or faked
Each of these is a plain-language warning sign, and each points to something specific an examiner looks at:
- The header's server timestamps don't match the date the email displays.
- The originating details are inconsistent with where the sender claims to have been.
- The routing record is missing, incomplete, or doesn't fit how the message should have traveled.
- Only a forwarded copy or a screenshot exists, rather than the original message with its full header.
- Internal identifiers disagree with the visible sender or date.
Why the date and sender at the top can't be trusted on their own
The sender name and date shown at the top of an email are easy to change, and a printout or screenshot shows only that surface. The header's behind-the-scenes record is much harder to fake convincingly, which is why a forensic examination looks past the visible message and into its underlying header data.
What an examination can, and can't, tell you
Being straight about the limits is part of doing this credibly. An email header examination can establish whether the header's own timestamps and routing are consistent with the date and origin a message claims. Its power depends heavily on having the original email with its full header rather than a forward, printout, or screenshot. It generally cannot by itself prove exactly who composed a message or their intent, only what the underlying records show. A qualified examiner is careful to claim only what the evidence supports.
If an email's authenticity matters to a legal or business dispute, a professional examination produces documented, defensible findings suitable for litigation. Forwarding or printing a message can strip away the header that matters most, so the safest step is to preserve the original email and have it examined. Preserving original digital evidence in this way is a core principle of established forensic practice.[4]
Why you need a forensics firm that specializes in metadata analysis
If you suspect an email was backdated or faked, the right professional is a digital forensics firm that specializes in metadata analysis. This is a distinct specialty. A traditional forensic document examiner focuses on handwriting, ink, and paper, and a general IT or computer forensics firm focuses on recovering data from devices and networks. Neither is necessarily trained to read the internal structure of an email and its header and explain what its metadata does, and doesn't, show.
When choosing an examiner, look for:
- A metadata analysis specialty covering the specific file type in question.
- A forensically sound process that works from a preserved original and documents chain of custody.
- A written forensic findings report that states what the evidence supports and what it doesn't.
- Expert witness experience, so the findings can be explained in a deposition or at trial.
Suspect an email was backdated or faked?
DeepData Forensics is a digital forensics firm that specializes in metadata analysis. We perform confidential email header and metadata analysis and delivers written forensic findings reports, typically within 48 hours.
Contact us about your email →Who should I hire to find out if an email was backdated or faked?
Can you tell if an email was backdated?
What do you need from me to examine an email?
Can a screenshot of an email be examined?
How long does an email analysis take?
- IETF RFC 5322, Internet Message Format — the Internet standard defining email structure, including the origination Date field, the Message-ID field, and the rule that trace header fields must not be reordered. Published by the RFC Editor: rfc-editor.org/info/rfc5322
- IETF RFC 5321, Simple Mail Transfer Protocol — the standard that defines the Received trace header each mail server prepends, recording the sending system's name and IP address and the date and time of handling: datatracker.ietf.org/doc/html/rfc5321
- IETF RFC 5322, Section 3.6.4, defining the Message-ID field — a globally unique identifier assigned to a message: rfc-editor.org/rfc/rfc5322.html
- Scientific Working Group on Digital Evidence (SWGDE), Best Practices for Digital Evidence Collection, and NIST Special Publication 800-86, Guide to Integrating Forensic Techniques into Incident Response — on preserving original digital evidence and treating message data as a forensic data source: swgde.org — Digital Evidence Collection; csrc.nist.gov/pubs/sp/800/86