Authentication
What receivers validated for SPF, DKIM and DMARC.
Built for agencies and B2B sales teams.Built for lead generation agencies and B2B sales teams. Manage contacts, automate email sequences, and handle replies in one workspace.
Start free →Paste a full email header to review SPF, DKIM, DMARC, sender identity and the relay-hop timeline.
Delivery evidence
| Hop | Stage | Time | Duration |
|---|---|---|---|
| 1 | Outbound submission | 10:42:01 | – |
| 2 | Provider relay | 10:42:02 | 1 s |
| 3 | Recipient acceptance | 10:42:05 | 3 s |
Include every line, not only the top.
Review authentication, routing and identity.
DNS for authentication problems. Reputation, content or provider policy for the rest.
What receivers validated for SPF, DKIM and DMARC.
Which servers handled the message and when.
The domains involved in From, Return-Path and signing.
Compare headers before and after a DNS change.
Why a pass is not the same as aligned.
One part of an investigation, not a verdict.
Every mail app has a way to show the raw message. You only need the header block, not the body.
| Mail app | Where to find the header |
|---|---|
| Gmail | Open the message, then More (three dots), then Show original |
| Outlook (new and web) | Open the message, then View message details |
| Outlook (classic) | Open the message, then File, then Properties |
The sending server is not authorised. Check the SPF record.
The signature did not validate. Check the selector and key.
Neither SPF nor DKIM aligned with From.
SPF passed for another domain. Check alignment.
A relay held the message. Compare timestamps.
Common with sending platforms. Check DMARC alignment.
SPF, DKIM or DMARC results show where the chain broke.
Timestamps show which relay held the message.
Compare From, Return-Path and the DKIM d= domain.
A truncated header hides the evidence you need.
Headers can contain addresses, IPs and message IDs. Paste only what you are comfortable analyzing. You do not need the message body, and the analysis is transport evidence, not a malware, phishing or content verdict. One delivered message reflects one receiver's path and outcome.
Read what the receiver recorded.
Compare results before and after.
Find which hop was slow.
A tool that parses message metadata into a readable report of authentication, routing and identity.
SPF checks the sending server, DKIM checks the message signature, and DMARC checks that one of them aligns with the visible From domain.
Open the message, choose More, then Show original.
In new and web Outlook use View message details. In classic Outlook use File, then Properties.
It is common with sending platforms. What matters is whether SPF or DKIM aligns with the From domain for DMARC.
Yes, if the DKIM signing domain does not align with the From domain.
Each hop adds a timestamp, so you can find where a delay happened. Clock accuracy on each server can affect the numbers.
It shows the evidence that matters, such as failed authentication and mismatched identities, but it cannot prove intent on its own.
No. The header is usually enough, and leaving out the body protects the content of the message.
No. Reputation, content and other factors also decide where mail lands.
Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.