Email-Header Analyzer: the question this tool answers
Parse pasted message headers locally in the request and summarize authentication and routing fields without storing the message body. The live result starts with Authentication-Results, then uses Received-SPF and DKIM signatures to confirm or challenge the first interpretation. A healthy result here is intentionally scoped to business-email DNS and mail authentication; it does not claim that unrelated parts of the domain are healthy.
- Authentication-Results
- Received-SPF
- DKIM signatures
- DMARC results
- Received hops
How to read the Authentication-Results, Received-SPF and DKIM signatures evidence
Start with the value that directly controls the failing service, then use the other signals to confirm or challenge that interpretation. A single record or response can look correct while another hostname, IP family, redirect or mail-authentication path still fails. The tool therefore keeps the raw observed value visible and explains how the signals relate.
- Authentication-Results — Verify Authentication-Results from the public Internet and compare it with the value the responsible provider says should be live.
- Received-SPF — Inspect the single public v=spf1 policy, validate its terms and count DNS-query-causing mechanisms; duplicate policies or excessive lookups can invalidate SPF.
- DKIM signatures — Use the selector configured by the sender or found in a DKIM-Signature header. Selector guessing is only a convenience and an empty guessed result is not proof that DKIM is absent.
- DMARC results — Query _dmarc, validate the policy tags and distinguish publication from message-level alignment; a published record does not by itself prove every message passes DMARC.
- Received hops — Verify Received hops from the public Internet and compare it with the value the responsible provider says should be live.
Common email-header analyzer failure patterns
The most useful warnings are mismatches rather than isolated missing fields. Authentication-Results can be absent or stale; Received-SPF can point somewhere different from the expected provider; and DKIM signatures can reveal a second path that behaves differently. If public sources disagree, first decide whether the difference comes from authoritative data, caching, a separate hostname, IPv6, or another protocol layer before editing configuration.
What to change — and what not to change
Change the smallest setting that the evidence proves is wrong. Compare the observed Authentication-Results with the current value supplied by the responsible provider, save the existing value, make one correction, and retest. Do not replace nameservers, delete unrelated MX/TXT records, disable TLS controls or remove IPv6 simply because Email-Header Analyzer shows a warning in another layer. Broad changes can turn one isolated problem into several independent outages.
How HostWithShery runs Email-Header Analyzer
The submitted public input is normalized and validated before any server-side request is made. HostWithShery then obtains Authentication-Results and Received-SPF using the appropriate public DNS, HTTP, TLS or mail protocol and adds DKIM signatures plus DMARC results where it materially changes the interpretation. URL-based checks are restricted to public destinations, and redirect targets are revalidated instead of being trusted automatically.
How to interpret conflicting email-header analyzer signals
When Authentication-Results looks correct but Received-SPF or DKIM signatures disagrees, do not treat the whole domain as broken. Isolate the public path that differs, identify whether it belongs to business-email DNS and mail authentication, and verify that path against the authoritative provider value before making a change. HostWithShery keeps these signals separate so a healthy value in one layer cannot mask a failure in another.
When a email-header analyzer result is inconclusive
This is a public-configuration diagnostic. Network filtering, private control-panel settings, split-horizon DNS, provider-internal state and transient routing conditions can limit what can be confirmed from outside the account. Public diagnostics cannot see private control-panel state, unpublished origin addresses, provider account status or split-horizon/internal DNS. If the remote service times out, blocks automated requests or hides a signal, the result stays inconclusive instead of inventing a provider or configuration. That distinction matters when the next step is a potentially disruptive DNS, SSL or mail change.
How to verify the repair
The public MX/authentication records should match the intended mail provider, required hostnames should resolve, and the relevant SPF/DKIM/DMARC check should no longer show the original failure. Repeat Email-Header Analyzer after the change and compare the same Authentication-Results, Received-SPF and DKIM signatures evidence that exposed the problem. A provider dashboard saying “saved” is not enough when the public Internet still returns the old value.
What to check next if Email-Header Analyzer is healthy
If Authentication-Results, Received-SPF and DKIM signatures now agree but the user-facing problem remains, move to the adjacent layer instead of editing the same setting repeatedly. Use the related diagnostics on this page to test the next plausible cause, and keep the previous result as evidence when escalating to a hosting, DNS or email provider.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.