How to read email headers: sent time, route and authenticity

· 5 min read

An email's headers record when it was sent, which servers handled it and whether SPF, DKIM and DMARC passed. Mail clients hide those lines, but getting at them takes only a few clicks. This guide shows where to find the headers, which line holds the sent time, and how to interpret the hops and the authentication results.

Which header shows when the email was sent?

The Date line. It is written by the sender's mail client and gives local time with the offset from UTC: "09:14:03 +0100" is 08:14:03 UTC. Because the sender sets it, it can be wrong, through a misconfigured clock or in forged mail. The trustworthy time is in the bottom Received header: it comes from the first mail server that accepted the message.

HTTP
Received: from mx.example.com (mx.example.com [192.0.2.25])
	by mail.example.net (Postfix) with ESMTPS id 4XkQ2r1Z3Wz9sT1
	for <ben@example.net>; Tue, 10 Nov 2026 09:14:07 +0100 (CET)
Authentication-Results: mail.example.net;
	dkim=pass header.d=example.org header.s=selector1;
	spf=pass smtp.mailfrom=example.org;
	dmarc=pass header.from=example.org
Received: from laptop.example.org (unknown [198.51.100.7])
	by mx.example.com (Postfix) with ESMTPSA id 7B2C41F0A9
	for <ben@example.net>; Tue, 10 Nov 2026 08:14:05 +0000 (UTC)
From: Anna <anna@example.org>
To: Ben <ben@example.net>
Subject: Angebot
Date: Tue, 10 Nov 2026 09:14:03 +0100
Message-ID: <20261110081403.7B2C41F0A9@example.org>

In this example the message was written at 09:14:03 (+0100), accepted by the sender's server two seconds later (bottom Received header, 08:14:05 UTC) and delivered to the recipient two seconds after that (top Received header, 09:14:07 +0100).

Showing the headers in your mail client

Every client has its own name for it. Always copy the complete header block, not an excerpt:

  • Gmail: open the message, three dots at the top right, "Show original".
  • Outlook (classic, Windows): double-click the message to open it in its own window, File › Properties, the "Internet headers" box.
  • New Outlook and Outlook on the web: open the message, three dots › View › "View message details".
  • Apple Mail: View › Message › All Headers.
  • Thunderbird: View › Message Source, or Ctrl+U.
  • As a file: save the message as .eml and open it in a text editor; the headers end at the first blank line.

The Received chain: read from the bottom up

Each server that passes the message along puts its Received header on top of the stack. The bottom one is therefore the oldest, the top one comes from your own mail server. Every entry states from whom (from, with the IP address in square brackets), to whom (by) and when.

  • from … [198.51.100.7]: the address the connection really came from. The name in front is only what the other side claimed.
  • with ESMTPS or ESMTPSA: the S stands for a TLS-encrypted transfer, the A for an authenticated connection.
  • Timestamps are in each server's local time. Convert them all to UTC before comparing durations.
  • A large gap between two hops shows where the message sat: greylisting, a full queue or a spam filter.
  • Trust only the entries from your own server down to the first foreign hop. Anything below that a sender can make up.

Authentication-Results: SPF, DKIM and DMARC

The receiving server writes this line after its checks. It starts with the server's own name and then lists the results:

  • spf=pass smtp.mailfrom=example.org: the sending IP is listed in the SPF record of the envelope sender's domain. fail or softfail means not authorized.
  • dkim=pass header.d=example.org header.s=selector1: the signature of the domain after d= is valid; s= names the selector used.
  • dmarc=pass header.from=example.org: SPF or DKIM passed and the checked domain aligns with the visible From address.
  • Only the line from your own server counts, recognisable by the name right after "Authentication-Results:". Lines carrying another name may have been sent along by the sender.
  • Microsoft 365 adds a compauth value to its Authentication-Results; Google repeats the results in ARC-Authentication-Results.

Parsing headers on the command line

For a saved .eml file the standard tools are enough. Long headers are folded across several lines (continuation lines start with a space or tab), so a plain grep shows only the first line.

Shell
grep -iE "^(Date|Received|Authentication-Results):" mail.eml

# with continuation lines (the timestamp is usually on the third line of a Received header)
tr -d "\r" < mail.eml | sed -n "1,/^$/p" | grep -iE -A3 "^(Received|Authentication-Results):"

# sent time and each hop on one line
python3 -c "import email,sys; m=email.message_from_file(open(sys.argv[1])); print('Date:', m['Date']); [print('Received:', ' '.join(r.split())) for r in m.get_all('Received')]" mail.eml

The DKIM signature carries its timestamp in the t= tag as Unix time. Convert it with date -u -d @1794298445 on Linux or date -u -r 1794298445 on macOS.

Common pitfalls

Where manual analysis usually goes wrong:

  • Wrong order: reading the Received headers top to bottom gives you the route backwards.
  • Ignoring time zones: "09:14 +0100" and "08:14 +0000" are the same moment.
  • Date lies in the future or far in the past: a wrong clock at the sender or an attempt at forgery. Spam filters count it against the message.
  • spf=fail on a forwarded message: the forwarder sends from an IP the original sender never authorized. DKIM survives forwarding, which is why DMARC asks for only one of the two.
  • No Authentication-Results header: the receiving server does not check, or does not record the result in the message.
  • Only an excerpt copied: without the lower Received headers the part that shows the origin is missing.

Let a tool do the reading

The email header analyzer takes the pasted headers and tells you in plain language whether SPF, DKIM and DMARC passed, whether the checked domain matches the visible sender address, which servers the message went through and how long each hop took. The headers are not stored.

Frequently asked questions

Where in the email header is the time the message was sent?
In the Date line, set by the sender's mail client. The time in the bottom Received header, written by the first accepting mail server, is more reliable.
In which order do I read the Received lines?
Bottom to top. Each server adds its entry at the top, so the bottom one shows the origin and the top one the delivery to you.
Can a sender forge the headers?
Everything they send themselves, yes: From, Date, Subject and even invented Received lines. What they cannot forge is what your own mail server adds: its Received header and its Authentication-Results.
What does dkim=pass mean when the domain after d= differs from the sender?
The signature is valid but belongs to a third party, for example the newsletter service. For DMARC it only counts when the domain after d= aligns with the visible From domain.
Check now

Paste email headers and read them in plain words: did SPF, DKIM and DMARC pass, does the sender domain align, which servers relayed it, how long it took?

Email header analyzer

DomainWarn checks SPF, DKIM and DMARC for all client domains on a schedule and analyses the DMARC reports, so you see delivery problems before anyone has to send you a header.

Monitor this domain continuously14-day free trial, no credit card.

More guides