Apple Mail app
- 1
Open the message in Mail.
- 2
From the menu bar, choose View > Message > Raw Source. If your version shows All Headers instead, select that option.
- 3
Select the complete source with Command + A, then copy it with Command + C.
Paste the original message headers to explain authentication, server hops, delivery delays, and sender details in plain language.
Use the original message—not a forwarded copy. Then follow the steps for the app where you received it.
Copy the full source or message details. The abbreviated From, To, and Subject fields shown above an email are not enough for routing and authentication analysis.
Open the message in Mail.
From the menu bar, choose View > Message > Raw Source. If your version shows All Headers instead, select that option.
Select the complete source with Command + A, then copy it with Command + C.
Open the message, select More actions (…) > View > View message details, then select and copy everything in the details window.
Double-click the message, choose File > Properties, then select and copy everything in the Internet headers box.
Open the message in Outlook on the web or Outlook.com.
At the top of the message, select More actions (…).
Choose View > View message details, then select and copy the complete contents.
Open the message in Gmail on a computer.
Next to Reply, select the More (three dots) menu—not the More menu in Gmail’s main toolbar.
Choose Show original, then select Copy to clipboard.
Return to the analyzer, paste them into the field, and select Analyze headers.
Headers describe how a receiver handled one message. They provide valuable evidence, but they cannot prove that content or a sender is trustworthy.
SPF, DKIM, DMARC, alignment, and forwarding-chain results.
Visible server hops, timestamps, transit time, and unusual delays.
From, Reply-To, Return-Path, and authenticated sending domains.
Decoded subject, message date, identifiers, and mailing-list controls.
Analyzing the pasted headers…
Authentication-Results fields are assertions made by receiving systems and are most reliable at a trusted receiver boundary. A passing result does not prove that a message is harmless, and a failure does not by itself prove malicious intent.
Analyze the headers, then copy your report into a support request. Our team can help identify what matters and recommend the next step.
Get help with results