Free Tools
Email Header Analyzer
A bounded analysis of routing, authentication, sender-identity, and transport evidence recorded in raw Internet message headers.
This tool analyzes header evidence only. It does not determine who authored a message, message legitimacy, malicious content, link or attachment danger, sender reputation, spoofing certainty, overall message safety, or sender verification status.
This analysis runs in your browser. Your pasted headers are not sent to Collabovizion, saved as history, or included in analytics. Headers can contain private addresses, internal hostnames, IP addresses, and Message-IDs; redact them when they are not needed for the diagnostic.
Results
Some header evidence was truncated to keep this analysis bounded.
Factual summary
Identity
Each field below is reported header evidence, shown separately. No single field is treated as the authoritative "real sender."
Authentication-Results
Authentication-Results reports what a receiving system recorded; this analyzer does not independently verify that the reporting authserv-id is trusted.
Different Authentication-Results entries report conflicting outcomes for the same authentication method.
One or more Authentication-Results entries report an authentication failure.
No Authentication-Results field is present in the analyzed header block.
Received-SPF evidence
This is supplemental header evidence and is not treated as more authoritative than Authentication-Results.
No Received-SPF field is present.
DKIM signatures
This analyzer reads DKIM-Signature metadata only. It does not retrieve the selector key or cryptographically verify the signature.
No DKIM-Signature field is present.
Recorded route — oldest header evidence to newest
Received headers are evidence recorded in the message. Earlier headers may have been added before the message entered a trusted mail system and can be forged.
No Received fields are present.
Timestamp / delay evidence
No adjacent hop delay evidence is available.
The message Date header is later than the newest valid Received timestamp recorded in the header.
Transport evidence
These are transport details recorded in the headers. They do not independently verify certificate validity, complete TLS negotiation, downgrade resistance, or current SMTP behavior.
No transport evidence is recorded.
ARC
ARC fields are displayed as reported header evidence. This analyzer does not cryptographically verify the ARC chain.
Contextual provider metadata
Message metadata
Provider-reported fields
No provider-specific header fields are present.
Findings
No findings for this result.