- Home
- Skills
- APIs & Backend
- Email Header Analyzer
Works with the AI Agents you already use
Email Header Analyzer
Parse email headers to map server hops, calculate delivery delays, and audit SPF/DKIM/DMARC security verdicts.
$2.99
Email Header Analyzer
Example session with this skill installed
Analyze these headers from a delayed email to see why it took two hours to arrive and check if the SPF/DKIM passed. <pasted_headers>
- Read your context and instructions
- Compiled the email header analyzer
I have analyzed the provided headers. The delay was primarily caused by a 118-minute hold at the final receiving gateway, likely due to greylisting or intensive content scanning. Authentication checks for SPF and DKIM passed successfully.
Email Header Analysis Report
Delivery Path & Latency
| Hop | From (Sender) | To (Receiver) | Delay | Protocol |
|---|---|---|---|---|
| 1 | mail-ej1-x62c.google.com | mx.google.com | 0s | TLS 1.3 |
| 2 | mx.google.com | relay.corporate-filter.net | 2s | TLS 1.2 |
| 3 | relay.corporate-filter.net | internal-ms-01.local | 118m 14s | Internal |
| 4 | internal-ms-01.local | User Mailbox | 1s | Local |
Security & Authentication
| Test | Status | Details |
|---|---|---|
| SPF | PASS | IP 209.85.218.44 authorized for domain.com |
| DKIM | PASS | selector=20230601, domain=domain.com |
| DMARC | PASS | policy=none, status=pass |
| Spam Score | 1.2 | Microsoft SCL: 1 (Non-spam) |
Red Flags
- Display Name Check: Match (Sender name matches address).
- Reply-To: No mismatch detected.
- Message-ID: Valid (Generated by google.com).
Next steps
- Review the configuration of
relay.corporate-filter.netto investigate the 118-minute processing delay. - Run with
--verify-dkimif you suspect the body content was altered after the message was sent. - Check the internal mail server logs for the specific timestamp
2023-10-27T14:22:01Z.
Connects securely to your tools. The creator never sees your data.
About this skill
Email headers are notoriously difficult to read manually. This skill parses raw header data to reconstruct the exact path a message took across the internet, identifying precisely where delays occurred and if security protocols were breached. It turns dense text blobs into a clear timeline of server hops and authentication results.
What it does
- Hop analysis Rebuilds the delivery path from
Receivedheaders and calculates the specific time delay at every server. - Authentication audit Summarizes SPF, DKIM, DMARC, and ARC results recorded by receiving mail servers.
- Spam scoring Extracts and interprets scores from SpamAssassin, Microsoft SCL/BCL, and Google filtering verdicts.
- Security red-flagging Detects display name spoofing, mismatched
Reply-Todomains, and suspiciousMessage-IDhosts. - Signature verification Optionally performs live or offline DKIM re-verification using
dkimpyto detect post-signing tampering.
How it works
- Input raw data Provide an exported
.emlor.msgfile, or paste raw headers directly from your mail client. - Execute parsing Run the script to generate a hop-by-hop delivery timeline and security summary.
- Verify signatures Use the
--verify-dkimflag for live DNS lookups or provide a local TXT file for offline key verification.
Frameworks & tools
The tool is built with Python 3 and uses the dkimpy library for cryptographic signature validation. It requires access to live DNS for real-time DKIM verification or a provided text file for offline environments.
Why this beats prompting it yourself
LLMs often hallucinate time calculations or misinterpret the bottom-up order of Received headers. This skill uses a logic-based parser to ensure hop delays are mathematically accurate and security verdicts are pulled directly from the source headers without inference errors.
Use cases
- Troubleshoot mail lag Pinpoint exactly which mail server held a message for 40 minutes.
- Verify phishing Check if the sender's display name matches the underlying envelope address.
- Audit deliverability Debug why a legitimate email was marked as junk by checking SCL and BCL scores.
- Detect tampering Confirm if the body content of an email was modified after the DKIM signature was applied.
Known limitations
DKIM re-verification requires the full message body, not just headers. Negative hop delays may appear if server clocks are not synchronized.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
DKIM re-verification requires the full message body. Negative hop delays may occur due to unsynchronized server clocks. Requires dkimpy library for verification features.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago