Gmail
Open the email. Beside Reply, open More, then choose Show original and Copy to clipboard.
Email header analyser
Copy the headers of any email you have received and paste them in. We tell you in plain English which server sent it, whose name it was signed in, and whether it passed SPF, DKIM and DMARC as the domain in its From address.
Open the email. Beside Reply, open More, then choose Show original and Copy to clipboard.
Open the email. At the top of the message choose More actions, then View, then View message details. Copy everything in the box.
Source: Microsoft, view internet message headers in Outlook.
Double-click the email to open it in its own window. Choose File, then Properties, and copy everything in the Internet headers box.
Source: Microsoft, view internet message headers in Outlook.
Open the email. Choose View, then Message, then All Headers, and copy the headers shown above the message.
Pasting the whole message is fine: the page keeps the headers and sends nothing after them.
The server that handed the email to your mail service, and the mail service or network that server belongs to.
The SPF, DKIM and DMARC results your own mail server wrote when the email arrived. A line the sender wrote into its own email is set aside.
Whether the domain asks inboxes to refuse an email faked in its name, send it to junk, or deliver it anyway.
Each server the email passed through, in order, with the time at each and which lines are the sending side's own account.
An example: an email that claims to be from harbourview.example, sent from a server that domain does not approve. The sender put a ready-made pass into its own email, and it was set aside.
Example dataharbourview.example asks inboxes to refuse email like this. Treat it as a fake unless you know why it failed.
The headers you pasted: "Invoice 2291 is overdue", from harbourview.example.
Sent from 198.51.100.24 on Example Hosting's network.
Received by mx.northquay.example.
Failed. The server that sent it (198.51.100.24) is not on harbourview.example's list of approved senders.
Not signed. Nothing vouches that this email really came from harbourview.example.
Failed. Neither SPF nor DKIM passed as harbourview.example, so receivers cannot tell this email apart from a fake.
The server that sent it is not on the Spamhaus blocklist.
The SPF, DKIM and DMARC results are the ones mx.northquay.example recorded when it received the email.
We set aside 1 result line in the paste that we could not tie to the receiving server. A sender can put any line it likes into its own email.
Each server an email passes through adds a line. The first hop is at the top.
| Hop | Handed over by | Received by | When | Network |
|---|---|---|---|---|
| 1 | 10.0.4.17as the sending side describes it | mail.parcel-notice.example | 9 Nov 2026, 09:14:05 UTC | Not known |
| 2 | mail.parcel-notice.example (198.51.100.24) | mx.northquay.example | 9 Nov 2026, 09:14:07 UTC2 seconds later | Example Hosting |
The lines every mail server adds as an email travels. They record which servers handled it and which checks it passed. Mail apps hide them, and the steps on this page show where to find them.
They show whether it passed DMARC as the domain in its From address. A pass proves the domain and nothing about the sender's intentions, so read the domain letter by letter: a look-alike domain with good records passes too.
No. The page cuts your paste at the end of the headers before anything is sent, so what the email says never leaves your browser. We read the headers once and keep nothing. To check them we look up the domains and the sending server they name in public DNS.
The rows say which check failed, and the list under them says what to change. To have a signature checked properly, send the same email to the email tester.
The headers held no result from your mail server that we could rely on, so we checked the sending server against the domain's records as they are now. A line the sender wrote into its own email is never counted.
SPF lists the servers allowed to send email for a domain. DKIM is a signature the sending service adds, which shows the email was not changed on the way. DMARC ties both to the From address you see, and tells inboxes what to do with email that fails.
Each of the three in more depth: SPF, DKIM and DMARC explained.
It reads your SPF, DKIM and DMARC records in about 30 seconds, and tells you where you stand today.