Email glossary

Received header

Every server that accepts a message adds a Received header on top of the existing ones with the previous host, its own name, the protocol, an id and a timestamp. Reading them from the bottom up gives the route and the time spent at each hop.

Example

Received: from out12.sender-platform.example.net (out12.sender-platform.example.net [198.51.100.24])
 by mx3.inbound-provider.example with ESMTPS id k2n9d1; Tue, 03 Nov 2026 09:12:41 +0000

Why it matters

Received headers are the only built-in evidence of where delays happen and which servers touched a message. Only the ones added by servers you trust are reliable; earlier ones can be forged.

Related tools and resources

Paste the headers of a message to see its identities, the route and timing between servers, DKIM signatures and the authentication results each server declared.

Messages, headers and errors

Related terms

Mailiqo

Follow every message without opening headers

In Mailiqo every message has its own history of statuses and events: deliveries, bounces and errors with their reason, all from the panel.

See what Mailiqo includes