Does an email not arrive, does it end up in spam, or do you doubt whether a message really comes from the sender? The email header has the answer. This unexpected piece of technology behind every email message shows exactly which servers passed the message along, whether SPF, DKIM, and DMARC passed, and why a spam filter may have blocked the message. In this article, you’ll learn how to retrieve, read, and use the header to solve problems yourself.
What exactly is an email header
Every email consists of two parts: the content you see (text, images, attachments) and the header, a collection of technical lines that’s usually hidden. The header shows, among other things, which mail servers processed the message, when it was sent, who the sender claims to be, and the outcome of authentication checks such as SPF, DKIM, and DMARC. You can compare the header to a packing slip that comes with a package: you see the contents right away, but the packing slip tells you where it came from and what steps it went through.
Retrieving the header in Gmail, Outlook, and webmail
In every mail program this option is hidden under a different label somewhere, but you’ll always be able to find it.
Gmail
Open the email, click the three dots in the top right of the message, and choose ‘Show original’. The full header appears in a new tab.
Outlook (desktop)
Double-click the email to open it in a separate window, go to File > Properties. At the bottom you’ll find the ‘Internet headers’ field.
Outlook on the web
Click the three dots next to the message, choose ‘View’ and then ‘View message source’.
Roundcube webmail
Open the message, click the settings icon above the message, and choose ‘Show source’. You use Roundcube, for example, for email via business email hosting.
Reading and understanding the most important lines
A header can look messy, but a few lines are really important:
- Received: every server that passed the message along adds its own ‘Received’ line at the top. Read them from bottom to top to follow the route: the bottom line is the starting point, the top line is where the message most recently arrived.
- From and Return-Path: this is the sender address as shown, and the address where bounces go. If these don’t match the expected domain, that’s a sign of spoofing.
- Authentication-Results: here you see in one line whether SPF, DKIM, and DMARC passed, failed, or weren’t checked (none).
- Message-ID: a unique identifier for the message, useful if you open a support ticket and need to demonstrate the problem.
Recognizing common problems
With the header in hand, you can diagnose most delivery problems yourself.
SPF fails: this means the sending server isn’t allowed in the SPF record of the sender domain. Check the TXT record of the domain and add the correct server. You can easily manage DNS records via the domain names management in Plesk.
DKIM fails: the digital signature in the email doesn’t match the public key in DNS. This often happens after a server migration where the DKIM key wasn’t carried over, or when a mailing list modifies the content of the message.
DMARC fails: DMARC builds on SPF and DKIM. If DMARC fails, first check which of the two underlying checks is incorrect and fix that.
Large delay between Received lines: if there’s a large time gap between two ‘Received’ lines, the message got stuck somewhere along the way. This can indicate an overloaded server or greylisting at the receiving party.
Unexpected stop along the route: if you see a server in the route that you don’t recognize or that has nothing to do with your own infrastructure, check whether your mail account has been misused or whether an open relay is active.
If emails still end up in spam despite correct SPF, DKIM, and DMARC, the problem may lie with the reputation of the IP address or with the content of the message itself. Switching to a hosting provider with a clean mail infrastructure can then offer a solution; check out the options via switching to Tandata.
Frequently asked questions
Can I also view the header of a sent email?
Yes, in most mail programs this works the same for sent as for received messages. Find the message in your sent items and use the same steps.
Why is there no Authentication-Results line in the header?
Then the receiving server didn’t perform an authentication check, for example with internal mail within the same system, or the server doesn’t support these checks.
Is it dangerous to share a header with support?
The header doesn’t contain passwords, but it does contain IP addresses and internal server information. Only share it with a trusted party, such as your hosting provider.
How do I know if an email is phishing based on the header?
Watch for discrepancies between the ‘From’ address and the ‘Return-Path’, a failed DMARC check, and a sending server that doesn’t logically match the company supposedly sending the mail.
Conclusion
The email header is a powerful tool for understanding delivery problems, spam complaints, and suspicious messages. By checking the Received lines, Authentication-Results, and the From address, you quickly find out where things go wrong and can adjust SPF, DKIM, or DMARC settings in a targeted way. If you’re unsure about the correct configuration, consult the knowledge base for more explanation.