# How to Read Email Headers When a Message Went Wrong

Canonical page: https://email-deliverability-desk.vercel.app/tools/email-header-analyzer/

Shows what the receiving server recorded about authentication and delivery for one message.

Tool: [Email Header Analyzer](https://billionverify.com/email-header-analyzer)

## What it checks

- SPF, DKIM, DMARC, ARC and DKIM-ATPS results with domains
- From, To, Subject, Date and Message-ID fields
- Number of Received hops on the delivery path
- X-Spam-Score value when the header is present
- Runs in the browser, nothing is uploaded

Knowing how to read email headers turns a vague complaint into evidence. When a message lands in spam, the receiving server has already written its verdicts into the headers. The BillionVerify Email Header Analyzer parses a pasted header block and pulls out the parts that matter for delivery.

**Key facts:**

- The BillionVerify Email Header Analyzer reads the Authentication-Results header for SPF, DKIM, DMARC, ARC and DKIM-ATPS, per its parser.
- It counts the Received lines and shows the total as delivery hops.
- It shows X-Spam-Score only when that header exists, and marks values above 5 in red.
- The parsing runs in your browser. The tool makes no network request with your headers.
- Authentication-Results is defined in RFC 8601, and each receiving server writes its own.

## How to read email headers step by step

You need the raw headers of a message that arrived, not the one you sent. Open the delivered copy in the mailbox that received it. Use the option called show original, view source or view headers.

1. Copy the whole header block, from the first line to the blank line before the body.
2. Paste it into the box.
3. Press Analyze Headers.
4. Press Clear when you are done. The pasted text goes away with it.

## What the analyzer shows

### Authentication results

Each protocol gets a row and a badge. A domain shows beside it only when the header gives `header.from` or `header.i`; SPF often uses `smtp.mailfrom`, so its row may show no domain. Only pass and bestguesspass show green. Everything else shows red, including neutral and none. Red therefore means "not a pass", and it does not always mean a hard failure. If no row appears, the header had no Authentication-Results line, so no server recorded a check.

### Key fields

From, To, Subject, Date and Message-ID appear as a short list. When an authentication row shows a domain, check it against the From domain. A mismatch is a common reason DMARC fails even when SPF passes.

### Delivery path

The tool gives a count of Received lines. It does not order them. Every server that handles a message adds its own Received line at the top, so read them from the bottom up to follow the route. A long gap between two hops points to a queue or a throttle on that server.

### Spam score

Some filters add an X-Spam-Score line. If it is present, the tool shows the number. A high value tells you the filter disliked the message. It does not tell you why, so use a full test for the named rules.

## What to check next

If SPF or DKIM shows red, check that record next. If all three pass and the message still went to spam, the cause is usually content, list quality or reputation. Look at the addresses you mail. Paste one into the checker to [check whether an email address exists](https://billionverify.com/email-checker).

The same applies to a single bounced recipient found in your logs. Use [a free online email verification tool](https://billionverify.com/email-verifier) to see whether that mailbox still accepts mail before you resend.
