# Email Header Analyzer

Parse the headers of an email (up to 256 KB): the route (oldest hop first: server, address, protocol, TLS, time, delay, clock skew), SPF, DKIM, DMARC and ARC results as written in the header, alignment with the From domain, From, Return-Path and Reply-To checks, spam and unsubscribe headers, the originating IP and signs of forgery. Returns a verdict (looks-normal, slow, suspicious, likely-forged, incomplete) and each header line with the findings it explains. Addresses are masked. Optional lookups send only addresses or domain names. Read in memory: never stored, logged or cached, no permalink.

**Not for:** Checking a domain's records (use email_health) or verifying a DKIM signature against the whole message.

- Tool id: `email-header-analyze`
- Category: email
- Execution: network
- MCP tool `email_header_analyze` at https://lookupowl.com/mcp
- REST `GET https://lookupowl.com/api/v1/tools/email-header-analyze` (or POST a JSON body)
- OpenAPI: https://lookupowl.com/api/openapi.json

## Input

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `headers` | string | yes |  | Message headers, up to 256 KB. A whole message is fine; only the top part is read. Never stored. min length 1, max length 262144 |
| `enrichIps` | boolean | no | `true` | Look up up to 10 public mail server addresses (network, country, name, blocklists). Only addresses are sent. |
| `enrichOrigin` | boolean | no | `true` | Also look up the oldest address. |
| `lookupDomains` | boolean | no | `false` | Ask DNS for the From domain DMARC policy and each DKIM key. Only names are sent. |
| `message` | number | no | `1` | Which message, when the text holds several. min 1, max 5 |

## Output

Results are wrapped in an envelope: `tool`, `version`, `requestId`, `data`, `summary`, `meta` (cache status, timing), `permalink`. `data` has these fields:

| Field | Type | Description |
|---|---|---|
| `summary` | object |  |
| `hops` | object[] |  |
| `auth` | object |  |
| `signatures` | object[] | The DKIM-Signature headers: signing domain, selector and algorithm. The signature itself is never returned. |
| `alignment` | object |  |
| `identity` | object |  |
| `spamVerdicts` | object |  |
| `unsubscribe` | string[] | Which List-Unsubscribe forms are present: url, mailto, one-click. |
| `originatingIp` | object |  |
| `findings` | object[] | Every check, with the header lines (numbers into `lines`) it is about. |
| `lines` | object[] | Every header line, addresses masked, with the hop it belongs to and the findings it explains, so the Headers tab can highlight them. At most 2,000. |
| `messages` | object |  |
| `lookups` | object | What the lookups the person chose found. Absent when nothing was looked up. |
| `warnings` | string[] |  |

## Examples

### A normal newsletter (made up)

```json
{"headers":"Return-Path: <bounce+8f3a@bounce.shop.example.com>\nDelivered-To: jordan@example.org\nReceived: from filter.example.org (filter.example.org [192.0.2.80])\n\tby mailbox.example.org with LMTP id kQ8d3w\n\tfor <jordan@example.org>; Fri, 13 Nov 2026 09:18:18 +0000\nARC-Seal: i=1; a=rsa-sha256; t=1794561499; cv=none; d=example.org; s=arc2026;\n\tb=ZmFrZS1zaWduYXR1cmUtZm9yLWRlc2lnbi1vbmx5\nARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=example.org; s=arc2026;\n\th=from:to:subject:date:message-id; bh=ZmFrZS1ib2R5LWhhc2gtZm9yLWRlc2lnbi1vbmx5LTAw;\n\tb=ZmFrZS1zaWduYXR1cmUtZm9yLWRlc2lnbi1vbmx5LTAy\nARC-Authentication-Results: i=1; mx-in.example.org;\n\tspf=pass smtp.mailfrom=bounce.shop.example.com;\n\tdkim=pass header.d=shop.example.com; dmarc=pass header.from=shop.example.com\nReceived: from mx-in.example.org (mx-in.example.org [192.0.2.70])\n\tby filter.example.org (Postfix) with ESMTP id 4SzB4k2\n\tfor <jordan@example.org>; Fri, 13 Nov 2026 09:18:19 +0000\nAuthentication-Results: mx-in.example.org;\n\tspf=pass (sender authorized) smtp.mailfrom=bounce.shop.example.com;\n\tdkim=pass header.d=shop.example.com header.s=s2026-11 header.b=ZmFrZS1z;\n\tdkim=pass header.d=mailer.example.net header.s=esp1 header.b=bW9yZS1m;\n\tdmarc=pass (policy=quarantine) header.from=shop.example.com\nReceived: from relay2.mailer.example.net (relay2.mailer.example.net [198.51.100.24])\n\tby mx-in.example.org (Exim 4.97) with ESMTPS (TLS1.3) tls TLS_AES_256_GCM_SHA384\n\t(envelope-from <bounce+8f3a@bounce.shop.example.com>) id 1vJxQe-0003aB-2k\n\tfor jordan@example.org; Fri, 13 Nov 2026 09:14:04 +0000\nReceived: from out1.mailer.example.net (out1.mailer.example.net [198.51.100.21])\n\tby relay2.mailer.example.net (Postfix) with ESMTPS id 4SzA2h9\n\tfor <jordan@example.org>; Fri, 13 Nov 2026 09:14:03 +0000 (UTC)\nReceived: from app-1.shop.example.com (app-1.shop.example.com [192.0.2.15])\n\tby out1.mailer.example.net (Postfix) with ESMTPS id 4SzA1c7\n\tfor <jordan@example.org>; Fri, 13 Nov 2026 10:14:02 +0100\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shop.example.com; s=s2026-11;\n\tt=1794561242; h=from:to:subject:date:message-id:list-unsubscribe:list-unsubscribe-post;\n\tbh=ZmFrZS1ib2R5LWhhc2gtZm9yLWRlc2lnbi1vbmx5LTAw; b=ZmFrZS1zaWduYXR1cmUtZm9yLWRlc2lnbi1vbmx5LTAx\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailer.example.net; s=esp1;\n\tt=1794561243; h=from:to:subject:date:message-id;\n\tbh=ZmFrZS1ib2R5LWhhc2gtZm9yLWRlc2lnbi1vbmx5LTAw; b=bW9yZS1mYWtlLXNpZ25hdHVyZQ\nFrom: Shop updates <news@shop.example.com>\nTo: Jordan Sample <jordan@example.org>\nSubject: Your November order update\nDate: Fri, 13 Nov 2026 10:14:00 +0100\nMessage-ID: <20261113091400.8f3a@shop.example.com>\nList-Unsubscribe: <https://shop.example.com/u/8f3a>, <mailto:unsub@shop.example.com?subject=unsubscribe>\nList-Unsubscribe-Post: List-Unsubscribe=One-Click\nX-Spam-Status: No, score=-1.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,SPF_PASS autolearn=ham\nMIME-Version: 1.0\nContent-Type: text/plain; charset=utf-8\n","enrichIps":false,"enrichOrigin":false,"lookupDomains":false,"message":1}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/email-header-analyze?enrichIps=false&enrichOrigin=false&headers=Return-Path%3A+%3Cbounce%2B8f3a%40bounce.shop.example.com%3E%0ADelivered-To%3A+jordan%40example.org%0AReceived%3A+from+filter.example.org+%28filter.example.org+%5B192.0.2.80%5D%29%0A%09by+mailbox.example.org+with+LMTP+id+kQ8d3w%0A%09for+%3Cjordan%40example.org%3E%3B+Fri%2C+13+Nov+2026+09%3A18%3A18+%2B0000%0AARC-Seal%3A+i%3D1%3B+a%3Drsa-sha256%3B+t%3D1794561499%3B+cv%3Dnone%3B+d%3Dexample.org%3B+s%3Darc2026%3B%0A%09b%3DZmFrZS1zaWduYXR1cmUtZm9yLWRlc2lnbi1vbmx5%0AARC-Message-Signature%3A+i%3D1%3B+a%3Drsa-sha256%3B+c%3Drelaxed%2Frelaxed%3B+d%3Dexample.org%3B+s%3Darc2026%3B%0A%09h%3Dfrom%3Ato%3Asubject%3Adate%3Amessage-id%3B+bh%3DZmFrZS1ib2R5LWhhc2gtZm9yLWRlc2lnbi1vbmx5LTAw%3B%0A%09b%3DZmFrZS1zaWduYXR1cmUtZm9yLWRlc2lnbi1vbmx5LTAy%0AARC-Authentication-Results%3A+i%3D1%3B+mx-in.example.org%3B%0A%09spf%3Dpass+smtp.mailfrom%3Dbounce.shop.example.com%3B%0A%09dkim%3Dpass+header.d%3Dshop.example.com%3B+dmarc%3Dpass+header.from%3Dshop.example.com%0AReceived%3A+from+mx-in.example.org+%28mx-in.example.org+%5B192.0.2.70%5D%29%0A%09by+filter.example.org+%28Postfix%29+with+ESMTP+id+4SzB4k2%0A%09for+%3Cjordan%40example.org%3E%3B+Fri%2C+13+Nov+2026+09%3A18%3A19+%2B0000%0AAuthentication-Results%3A+mx-in.example.org%3B%0A%09spf%3Dpass+%28sender+authorized%29+smtp.mailfrom%3Dbounce.shop.example.com%3B%0A%09dkim%3Dpass+header.d%3Dshop.example.com+header.s%3Ds2026-11+header.b%3DZmFrZS1z%3B%0A%09dkim%3Dpass+header.d%3Dmailer.example.net+header.s%3Desp1+header.b%3DbW9yZS1m%3B%0A%09dmarc%3Dpass+%28policy%3Dquarantine%29+header.from%3Dshop.example.com%0AReceived%3A+from+relay2.mailer.example.net+%28relay2.mailer.example.net+%5B198.51.100.24%5D%29%0A%09by+mx-in.example.org+%28Exim+4.97%29+with+ESMTPS+%28TLS1.3%29+tls+TLS_AES_256_GCM_SHA384%0A%09%28envelope-from+%3Cbounce%2B8f3a%40bounce.shop.example.com%3E%29+id+1vJxQe-0003aB-2k%0A%09for+jordan%40example.org%3B+Fri%2C+13+Nov+2026+09%3A14%3A04+%2B0000%0AReceived%3A+from+out1.mailer.example.net+%28out1.mailer.example.net+%5B198.51.100.21%5D%29%0A%09by+relay2.mailer.example.net+%28Postfix%29+with+ESMTPS+id+4SzA2h9%0A%09for+%3Cjordan%40example.org%3E%3B+Fri%2C+13+Nov+2026+09%3A14%3A03+%2B0000+%28UTC%29%0AReceived%3A+from+app-1.shop.example.com+%28app-1.shop.example.com+%5B192.0.2.15%5D%29%0A%09by+out1.mailer.example.net+%28Postfix%29+with+ESMTPS+id+4SzA1c7%0A%09for+%3Cjordan%40example.org%3E%3B+Fri%2C+13+Nov+2026+10%3A14%3A02+%2B0100%0ADKIM-Signature%3A+v%3D1%3B+a%3Drsa-sha256%3B+c%3Drelaxed%2Frelaxed%3B+d%3Dshop.example.com%3B+s%3Ds2026-11%3B%0A%09t%3D1794561242%3B+h%3Dfrom%3Ato%3Asubject%3Adate%3Amessage-id%3Alist-unsubscribe%3Alist-unsubscribe-post%3B%0A%09bh%3DZmFrZS1ib2R5LWhhc2gtZm9yLWRlc2lnbi1vbmx5LTAw%3B+b%3DZmFrZS1zaWduYXR1cmUtZm9yLWRlc2lnbi1vbmx5LTAx%0ADKIM-Signature%3A+v%3D1%3B+a%3Drsa-sha256%3B+c%3Drelaxed%2Frelaxed%3B+d%3Dmailer.example.net%3B+s%3Desp1%3B%0A%09t%3D1794561243%3B+h%3Dfrom%3Ato%3Asubject%3Adate%3Amessage-id%3B%0A%09bh%3DZmFrZS1ib2R5LWhhc2gtZm9yLWRlc2lnbi1vbmx5LTAw%3B+b%3DbW9yZS1mYWtlLXNpZ25hdHVyZQ%0AFrom%3A+Shop+updates+%3Cnews%40shop.example.com%3E%0ATo%3A+Jordan+Sample+%3Cjordan%40example.org%3E%0ASubject%3A+Your+November+order+update%0ADate%3A+Fri%2C+13+Nov+2026+10%3A14%3A00+%2B0100%0AMessage-ID%3A+%3C20261113091400.8f3a%40shop.example.com%3E%0AList-Unsubscribe%3A+%3Chttps%3A%2F%2Fshop.example.com%2Fu%2F8f3a%3E%2C+%3Cmailto%3Aunsub%40shop.example.com%3Fsubject%3Dunsubscribe%3E%0AList-Unsubscribe-Post%3A+List-Unsubscribe%3DOne-Click%0AX-Spam-Status%3A+No%2C+score%3D-1.2+required%3D5.0+tests%3DDKIM_SIGNED%2CDKIM_VALID%2CSPF_PASS+autolearn%3Dham%0AMIME-Version%3A+1.0%0AContent-Type%3A+text%2Fplain%3B+charset%3Dutf-8%0A&lookupDomains=false&message=1'
```

Web page: https://lookupowl.com/email-header-analyzer?enrichIps=false&enrichOrigin=false

### A forged message (made up)

```json
{"headers":"Return-Path: <x7q@mailer.cheap-host.example>\nDelivered-To: jordan@example.org\nReceived: from mx-in.example.org (mx-in.example.org [192.0.2.70])\n\tby mailbox.example.org with LMTP id aB3dEf\n\tfor <jordan@example.org>; Fri, 13 Nov 2026 03:02:14 +0000\nAuthentication-Results: mx-in.example.org;\n\tspf=fail (sender IP is 198.51.100.77) smtp.mailfrom=mailer.cheap-host.example;\n\tdkim=none (message not signed);\n\tdmarc=fail (p=reject) header.from=examplebank.example\nReceived: from mailer.cheap-host.example (unknown [198.51.100.77])\n\tby mx-in.example.org (Postfix) with SMTP id 4SzF1x3\n\tfor <jordan@example.org>; Fri, 13 Nov 2026 03:02:12 +0000\nFrom: \"Example Bank Support\" <support@examplebank.example>\nReply-To: <help@examplebank-secure.example>\nTo: Jordan Sample <jordan@example.org>\nSubject: Your account is locked\nDate: Fri, 13 Nov 2026 03:02:00 +0000\nMessage-ID: <a1b2c3@mailer.cheap-host.example>\nMIME-Version: 1.0\nContent-Type: text/html; charset=utf-8\n","enrichIps":false,"enrichOrigin":false,"lookupDomains":false,"message":1}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/email-header-analyze?enrichIps=false&enrichOrigin=false&headers=Return-Path%3A+%3Cx7q%40mailer.cheap-host.example%3E%0ADelivered-To%3A+jordan%40example.org%0AReceived%3A+from+mx-in.example.org+%28mx-in.example.org+%5B192.0.2.70%5D%29%0A%09by+mailbox.example.org+with+LMTP+id+aB3dEf%0A%09for+%3Cjordan%40example.org%3E%3B+Fri%2C+13+Nov+2026+03%3A02%3A14+%2B0000%0AAuthentication-Results%3A+mx-in.example.org%3B%0A%09spf%3Dfail+%28sender+IP+is+198.51.100.77%29+smtp.mailfrom%3Dmailer.cheap-host.example%3B%0A%09dkim%3Dnone+%28message+not+signed%29%3B%0A%09dmarc%3Dfail+%28p%3Dreject%29+header.from%3Dexamplebank.example%0AReceived%3A+from+mailer.cheap-host.example+%28unknown+%5B198.51.100.77%5D%29%0A%09by+mx-in.example.org+%28Postfix%29+with+SMTP+id+4SzF1x3%0A%09for+%3Cjordan%40example.org%3E%3B+Fri%2C+13+Nov+2026+03%3A02%3A12+%2B0000%0AFrom%3A+%22Example+Bank+Support%22+%3Csupport%40examplebank.example%3E%0AReply-To%3A+%3Chelp%40examplebank-secure.example%3E%0ATo%3A+Jordan+Sample+%3Cjordan%40example.org%3E%0ASubject%3A+Your+account+is+locked%0ADate%3A+Fri%2C+13+Nov+2026+03%3A02%3A00+%2B0000%0AMessage-ID%3A+%3Ca1b2c3%40mailer.cheap-host.example%3E%0AMIME-Version%3A+1.0%0AContent-Type%3A+text%2Fhtml%3B+charset%3Dutf-8%0A&lookupDomains=false&message=1'
```

Web page: https://lookupowl.com/email-header-analyzer?enrichIps=false&enrichOrigin=false

## Web pages

- https://lookupowl.com/email-header-analyzer

## Limits and caching

- Cost: 3 units for a live lookup, 1 unit for a cached one. Budgets are per network and published in the `RateLimit` response headers.
- Cache: results are never cached.
- Timeout: 15 s.

## Related tools

- [Email Health Checker and Spoofing Test](https://lookupowl.com/tools/email-health.md): Check a domain's whole mail setup in one report: mail servers, SPF, DKIM, DMARC, BIMI, MTA-STS, TLS-RPT and blocklists, with the fixes to make first.
- [SPF Record Checker](https://lookupowl.com/tools/spf-checker.md): Check a domain's SPF record, count its DNS lookups against the limit of 10 and find errors.
- [DMARC Record Checker](https://lookupowl.com/tools/dmarc-checker.md): Look up and validate a domain's DMARC policy, report addresses and alignment settings.
- [DKIM Record Checker](https://lookupowl.com/tools/dkim-checker.md): Find and check a domain's DKIM public keys, even when you do not know the selector.
- [IP and Domain Blacklist Checker](https://lookupowl.com/tools/blacklist-checker.md): Check an IP address, a mail server or a domain against live spam blocklists, with how to get delisted.
- [Gmail, Yahoo and Microsoft Bulk Sender Rules Checker](https://lookupowl.com/tools/sender-requirements.md): Check a domain against the Gmail, Yahoo and Microsoft bulk sender rules, rule by rule, and see what only a sent message can settle.
- [IP Location Lookup](https://lookupowl.com/tools/ip-location.md): Where an IP address is: city, region, country and the network that runs it, from DB-IP, with an honest accuracy note.

## Guide: Email header analyzer

Read the headers of an email to see where it came from, why it was late and whether the sender's checks passed.

### What the analyzer shows

Every server that handles an email adds a line called `Received` to the top of its headers. Read from the bottom up, those lines are the route of the message. The analyzer lists them oldest first, works out the time between each pair and marks the step where most of the wait happened.

The receiving server also writes an `Authentication-Results` line that says whether the message passed SPF, DKIM and DMARC. The analyzer shows those results as written, checks whether the sending domain matches the From domain (the alignment that DMARC needs) and compares the From, Return-Path and Reply-To addresses.

- The route: each server, its address, the protocol, whether the hop used TLS and the delay at each step.
- The checks: SPF, DKIM, DMARC and ARC as recorded by the receiver, with the alignment worked out from the header.
- The people: who the message claims to be from, where replies go, and whether the display name, the address and the reply address agree.
- The signs of forgery: a display name that names another address, a look-alike Reply-To domain, or a failed DMARC check that was delivered anyway.

### What happens to what you paste

Headers hold names, addresses and the network addresses of people, so this page is built to keep them to itself. With JavaScript on, the headers are read inside your browser and nothing is sent anywhere. We do not store the header and we do not put it in the page address, a link or a statistic.

Some extras need our servers, so they are off until you ask. After the headers are read, a card lists exactly what each lookup would send: the public address of a mail server, or a domain name. Only the items you tick leave the page, and the header never does.

> **Without JavaScript** The form posts the headers to our server for that one request. We read them, show the result and don't keep them. The answer is never cached and the page address has no query.

To check DKIM signatures themselves you need the whole message, because the signature covers the body. Drop the `.eml` file on the page and the check runs in your browser. It asks DNS for the public key of each signature and sends only that DNS name, for example `s2026-11._domainkey.shop.example.com`.

### How to get the headers

Every mail program hides the headers by default. Look for the option called Show original, View source, Message details or Internet headers, and copy everything from the top down to the first blank line. You can paste the whole message too: only the top part is read.

1. **Gmail**: Open the message, choose the three dots next to Reply, then Show original. Choose Copy to clipboard and paste it here.
2. **Outlook on the web**: Open the message, choose the three dots, then View, then View message details. Copy the text in the box.
3. **Outlook for Windows**: Double-click the message to open it, choose File, then Properties. Copy the text under Internet headers.
4. **Apple Mail**: Select the message, choose View, then Message, then All Headers or Raw Source. Copy the text at the top.
5. **Yahoo Mail**: Open the message, choose the three dots, then View raw message. Copy the lines at the top.
6. **Thunderbird**: Open the message, choose More, then View Source, or press Ctrl+U. Copy the lines at the top.
7. **Proton Mail**: Open the message, choose the three dots, then View headers. Copy the text.

### Reading the result

The answer at the top is one sentence. "Looks normal" means the checks passed and nothing in the route stands out. "Worth a closer look" means a check failed or an address does not match. "Likely forged" means several signs point the same way; it is a reason to be careful, not proof.

A long delay at one hop usually means a scan or a greylisting wait at that server. The header shows when each server received the message but not why it waited, so the page says where the time went and never guesses the cause. Clocks that run slightly behind are counted as zero seconds.

Only the top `Authentication-Results` line is trusted, because it was written by the server that delivered the message to you. Lower ones were written by earlier servers and anyone in the chain can forge them. The analyzer says which server wrote the one it trusts.

### Frequently asked questions

**Is my email kept anywhere?**

No. With JavaScript the headers are read in your browser and never sent. Without JavaScript they go to our server for that one request, are shown back to you and are not stored, logged or cached. There is no link to share a result, because a link would have to hold the header.

**Where do I find the headers of an email?**

Open the message and look for Show original, View source, Message details or Internet headers. The page lists the steps for Gmail, Outlook, Apple Mail, Yahoo Mail, Thunderbird and Proton Mail.

**Why was my email delayed?**

The route shows the time between each pair of servers. A big jump at one hop is typically a spam or virus scan or a greylisting delay at that server. The header cannot say which, so the page names the step and leaves the cause open.

**How can I tell if an email is forged?**

Look for a failed SPF or DMARC result, a Return-Path or Reply-To on a different domain, and a display name that claims a bank or brand the address does not belong to. One sign alone can be innocent. Several together are worth treating as a forgery: do not click links or reply.

**What do SPF, DKIM and DMARC mean here?**

SPF says the sending server is allowed to send for a domain. DKIM says a signature from the domain matches the message. DMARC asks for one of them to pass and to match the From domain. The analyzer shows the result the receiver wrote and whether the domains line up.

**Why does it say DKIM is reported by the receiver?**

A DKIM signature covers the body of the message, which a header paste does not include. To check the signature here, drop the whole `.eml` file on the page. The check runs in your browser and sends only the DNS name of each public key.

**Can it check the sending server or domain further?**

Yes, if you tick it after the result. You can look up the public mail server addresses (network, country, name and blocklists) and the domain checks (DMARC policy and DKIM keys). Only the addresses or names you tick are sent.
