Paste · Parse · Troubleshoot
Email Header Analyzer
Parse raw email headers and get clear insights into SPF, DKIM, DMARC, ARC, routing hops, alignment, and delivery clues.
✓ Raw header parsing·✓ No sign-up required·✓ Browser-local analysis·✓ Authentication insights
Header Analysis Workspace
Review message authentication, routing, alignment, and header evidence in one workspace.
Authentication results
SPF passed for example.com.
DKIM passed using example.com / selector selector1 (rsa-sha256).
DMARC passed for example.com with policy quarantine and the message is aligned.
No ARC headers were found in this message.
Sender alignment
Delivery route / Received path
2 hopsParsed header fields
Raw header preview
Return-Path: <bounce@example.com>
Received: from mail.example.com (mail.example.com [192.0.2.10])
by mx.google.com with ESMTPS id abc123
for <jane@gmail.com>;
Sun, 31 Mar 2024 10:14:25 +0000
Received: from security.example.net (security.example.net [172.253.118.27])
by mail.example.com with ESMTPS id def456;
Sun, 31 Mar 2024 10:14:24 +0000
Authentication-Results: mx.google.com;
spf=pass smtp.mailfrom=bounce@example.com;
dkim=pass header.i=@example.com header.s=selector1 header.b=abc123;
dmarc=pass (p=quarantine) header.from=example.com
Received-SPF: pass (google.com: domain of bounce@example.com designates 192.0.2.10 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; d=example.com; s=selector1;
c=relaxed/relaxed; q=dns/txt; h=from:to:subject:date:message-id;
bh=SampleBodyHash123; b=SampleSignature123
From: John Doe <john@example.com>
To: Jane Example <jane@gmail.com>
Reply-To: john@example.com
Subject: Meeting tomorrow
Date: Sun, 31 Mar 2024 10:14:22 +0000
Message-ID: <20240331101422.12345@example.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
X-Mailer: Microsoft Outlook 16.0About This Email Header Analyzer
Mailvovo parses raw email headers locally in your browser and turns authentication, routing, identity, and delivery evidence into a clear analysis. Review SPF, DKIM, DMARC, ARC, sender alignment, Received hops, relay IPs, and important message metadata without manually reading long header blocks.
What it checks
- SPF, DKIM, DMARC, and ARC results
- Email routing and Received hops
- From, Return-Path, and DKIM alignment
- Authentication-Results evidence
- Important header fields and metadata
- Common delivery and authentication warnings
Who it’s for
- Domain owners
- IT administrators
- Email deliverability teams
- Security analysts
- Email administrators
- MSPs and agencies
Important to know
- Analysis uses only the supplied message header
- Not every message contains ARC headers
- Authentication results are message-specific
- Received headers can contain private or intermediary IPs
- Alignment is different from simple authentication success
- Use DNS checkers to investigate configuration separately
How It Works
Get header insights in four simple steps.
- 1Paste or Upload
Paste raw headers or upload a local .eml or .txt file.
- 2We Analyze
Mailvovo parses authentication, identities, and Received routing evidence.
- 3View Insights
See authentication results, alignment, hops, metadata, and findings.
- 4Take Action
Use the findings to troubleshoot message or domain configuration issues.
Frequently Asked Questions
You can paste a standard raw email header or upload a text-based .eml or .txt file containing email headers.
SPF evaluates the envelope sender, DKIM validates a cryptographic message signature, and DMARC evaluates alignment between the visible From domain and authenticated identities.
This analyzer processes the supplied header in your browser. The free analyzer does not need to upload the header to Mailvovo for parsing.
ARC is mainly useful when messages pass through intermediaries such as forwarding systems or mailing lists. Many direct messages legitimately contain no ARC chain.
This version analyzes one message header at a time so the authentication and routing evidence stays tied to one message.
Use the finding details to identify whether the problem is SPF, DKIM, DMARC, alignment, or routing related, then use the matching Mailvovo DNS tool for configuration-level investigation.
Analyze Another Header
Try another email header to get fresh authentication and routing insights.