Every email carries a hidden technical history — a set of headers most mail clients hide from view, but which honestly record which servers the message passed through and whether the sender was actually who they claim to be.
Why a subject line sometimes looks like "=?UTF-8?B?...?="
Email headers were designed decades ago around plain 7-bit ASCII, so a subject like "Café meeting notes — François" can't just be dropped into a header as-is. RFC 2047 solves this with the "encoded word" syntax: =?UTF-8?B?Q2Fmw6kgbWVldGluZyBub3Rlcw==?= — a charset, then B for Base64 or Q for quoted-printable, then the encoded bytes themselves. This is the single most common reason a raw header dump looks like garbage: any subject or display name with an accented letter, an emoji, or non-Latin text gets wrapped this way, and a header parser has to decode it back before it's readable.
Received headers: the message's route, in reverse
Every mail server the message passes through adds its own Received header to the top of the stack — so to trace the message's actual path from sender to inbox, the headers have to be read from bottom to top, opposite to the order they were added in.
SPF, DKIM, and DMARC: three separate trust checks
SPF (Sender Policy Framework) is a DNS record listing which servers are allowed to send mail for a domain; the Received-SPF header shows whether the sending server was on that list. DKIM attaches a cryptographic signature that a public key published in the sender's DNS can verify, proving the message body wasn't altered in transit. DMARC then tells the receiving server what to do with mail that fails SPF or DKIM — reject it, flag it as spam, or deliver it with a warning. Together they're the difference between "this looks like it's from your bank" and "this is provably from your bank's mail servers."
What this is useful for
- Checking whether a suspicious email is a phishing attempt with a spoofed sender address.
- Decoding a subject or sender name that arrived as an unreadable
=?UTF-8?B?...?=string. - Diagnosing why your own outgoing mail keeps landing in recipients' spam folders.
What Message-ID is for
The Message-ID header is a unique identifier assigned by the sending client, meant to never repeat across any other email in the world. It's essential for threading: when you reply to a message, your client copies the original Message-ID into an In-Reply-To header, and that link is what lets mail apps group messages into one conversation instead of showing them as unrelated items.