# Email Health Checker and Spoofing Test

Audit a domain's email setup from public DNS and policy files. Runs the mail server (MX), SPF, DKIM, DMARC, BIMI, MTA-STS, TLS-RPT and blocklist checks and returns a level word (healthy, good-with-fixes, needs-attention, not-working), counts of pass, info, warn, fail and not checked (counted, not weighted, no letter grade), one headline per category, up to 3 fixes to make first (with provider-specific advice when the mail provider is known), the findings, a spoofability verdict (can someone send mail as this domain?), and the changes since the last scan. scope spoofing runs only the DNS subset. DANE and mail server TLS need a mail server connection and are not part of this report. Public domains only; no mail is sent.

**Not for:** Reading one record in depth (use spf_check, dmarc_check, dkim_check) or checking a message (use email_header_analyze).

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

## Input

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `domain` | string | yes |  | A domain name such as example.com. We read its public records and nothing else. An email address is reduced to its domain. min length 1, max length 320 |
| `scope` | "full" \| "spoofing" | no | `"full"` | full: every category. spoofing: only the DNS-only subset (MX, SPF, DMARC with sp and np), fast and cheaper. |

## Output

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

| Field | Type | Description |
|---|---|---|
| `domain` | string |  |
| `scope` | "full" \| "spoofing" |  |
| `scannedAt` | string |  |
| `incomplete` | boolean | true when a category did not finish in time. Those categories are unknown, never passes, and the result is not stored as a normal answer. |
| `state` | "ok" \| "incomplete" \| "parked-protected" \| "parked-open" \| "no-mail" \| "nxdomain" \| "dns-error" |  |
| `level` | "healthy" \| "good-with-fixes" \| "needs-attention" \| "not-working" |  |
| `counts` | object |  |
| `categories` | object[] |  |
| `unfinished` | "mx" \| "spf" \| "dkim" \| "dmarc" \| "bimi" \| "mta-sts" \| "tls-rpt" \| "blocklists"[] |  |
| `notChecked` | "dane" \| "mail-tls"[] | Parts that need a mail server connection. Not part of this report or its level. |
| `mailServers` | string[] |  |
| `topFixes` | object[] | max 3 items |
| `findings` | object[] |  |
| `provider` | object |  |
| `policyDomain` | string \| null | The domain DMARC was read from, when it is not the domain checked. |
| `spoofability` | object |  |
| `changesSinceLastScan` | object | Always null for now: scans are not stored. |
| `permalink` | string |  |

## Examples

### github.com: valid SPF with no lookups to spare

```json
{"domain":"github.com","scope":"full"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/email-health?domain=github.com&scope=full'
```

Web page: https://lookupowl.com/email-health-check?q=github.com

### lookupowl.com: DMARC reject, no MTA-STS

```json
{"domain":"lookupowl.com","scope":"full"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/email-health?domain=lookupowl.com&scope=full'
```

Web page: https://lookupowl.com/email-health-check?q=lookupowl.com

### example.com: a parked domain

```json
{"domain":"example.com","scope":"full"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/email-health?domain=example.com&scope=full'
```

Web page: https://lookupowl.com/email-health-check?q=example.com

### Can github.com be spoofed?

```json
{"domain":"github.com","scope":"spoofing"}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/email-health?domain=github.com&scope=spoofing'
```

Web page: https://lookupowl.com/email-spoofing-check?q=github.com

## Web pages

- https://lookupowl.com/email-health-check
- https://lookupowl.com/email-spoofing-check

## Limits and caching

- Cost: from 1 unit up, depending on the input (a registry lookup counts every upstream request); 1 unit for a cached result. Budgets are per network and published in the `RateLimit` response headers.
- Cache: results are kept for 600 s. Add `fresh=true` (MCP argument or query parameter) to look again; it costs 3 units per unit and is limited to 10 per hour.
- Timeout: 30 s.

## Related tools

- [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.
- [MTA-STS Checker](https://lookupowl.com/tools/mta-sts-check.md): Check a domain's MTA-STS record and policy file: mode, mail server patterns, lifetime and whether they match the MX hosts.
- [TLS-RPT Checker](https://lookupowl.com/tools/tls-rpt-check.md): Check a domain's TLS-RPT record: where mail servers send reports about failed encrypted deliveries, and whether those addresses work.
- [BIMI Checker](https://lookupowl.com/tools/bimi-check.md): Check a domain's BIMI record, DMARC policy, logo file and VMC or CMC certificate, and see which inboxes would show the logo.
- [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.
- [DNS Health Checker](https://lookupowl.com/tools/dns-health.md): A full DNS health report for a domain: delegation, name servers, SOA, DNSSEC, mail records, IPv6 and security, with the fix for each problem.
- [Domain Report: Registration, DNS, Web, Hosting and Email](https://lookupowl.com/tools/domain-report.md): One scored report on a domain: registration, DNS, certificate and security headers, hosting, SPF, DMARC, DKIM and blocklists.

## Guide: Email health check

Check whether the mail for a domain is set up so that it arrives and cannot easily be faked, in one report with the fixes to make first.

### What the report covers

Mail depends on a handful of records that live in different places and are easy to get slightly wrong. Each has its own checker, and people rarely have the time to open all of them. This report runs the lot for one domain and puts the answer on one page.

- Mail servers (MX): where mail for the domain is delivered, and which provider runs it when we can tell.
- SPF: which servers may send as the domain, and whether the record stays under the limit of 10 lookups.
- DKIM: the signing keys we can find among the common selectors, and whether any is shorter than 2048 bits or broken.
- DMARC: what receivers are told to do with mail that fails, and whether the policy is enforced or only watching.
- Blocklists: whether any mail server address of the domain is listed.
- BIMI, MTA-STS and TLS-RPT: the optional records. Not having them is a recommendation, never a fault.

Each part gets one line and a status: pass, info, warning, fail, or "Couldn't check" when it did not answer in time. Every status has a word next to its icon, so the page reads the same without colour.

### A level word and counts, not a grade

The top of the report says one of four things: healthy, good with things to fix, needs attention, or not working. The level is the lowest result among the parts, and the counts beside it say how many passed, how many are information only, and how many are warnings or failures. Nothing is weighted and there is no letter, because a letter invites you to chase the letter instead of the problem.

A part that is not set up, such as BIMI, counts as information and never lowers the level. A part we could not check never counts as a pass. If a fifth or more of the parts did not finish, the report says it is based on the checks that did.

> **What is left out, and why** DANE and mail server TLS can only be tested by connecting to your mail servers. We do not do that yet, so they are listed once as not in this report and do not count toward the level.

### Fix first

Under the answer you get up to three fixes in the order that matters most: a missing DMARC record before a short DKIM key, a broken SPF record before an unlisted logo. Each row says why it matters and what to do, and where a copy-ready record helps, it has a Copy button.

When we recognise the mail provider from the MX records, the advice is written for it. A 1024-bit key at Microsoft 365 is fixed in the Defender portal, not in your DNS, and the row says so. When we do not recognise the provider, the advice stays general rather than guessing.

### Can someone send mail as this domain?

The last card answers that in plain words, from the SPF and DMARC records: no, partly, or yes. A domain with no DMARC record, or one set to p=none, can be faked and the fake will usually be delivered. A domain that publishes p=reject and holds subdomains to the same rule cannot. The [email spoofing check](https://lookupowl.com/email-spoofing-check) page gives only this answer and runs faster.

Mailbox providers such as gmail.com are a special case. They publish p=none on purpose, because millions of people send through other services as @gmail.com, and a stricter policy would block real mail. The card says "Yes, and that is on purpose" rather than calling it a mistake.

### What we touch and what we keep

We read public DNS records and the public policy files for MTA-STS and BIMI. We never open a connection to a mail server and we never send a message. The report is built for the one request, a result that is a few minutes old may be shown again to save the servers asking twice, and nothing is kept about you.

The whole report can take up to 15 seconds, because it runs several checks and some of them query many blocklists. Without JavaScript the page waits and shows the finished report. With it, you see the parts finish one by one.

### Frequently asked questions

**Do you send an email to test?**

No. We never send a message. We read your DNS records and, for MTA-STS and BIMI, the public policy files those records point to.

**Why is there no grade?**

A grade invites comparison between very different setups and hides what to do. A level word, counts and three fixes say what to change, and a domain that sends no mail can still be healthy.

**Why does it say BIMI, MTA-STS and TLS-RPT are not set up when my mail works?**

They are optional extras. Mail arrives without them. We list them as information because they add something: a logo in some inboxes, a rule that senders must use encryption, and reports when delivery fails.

**What does "Couldn't check" mean?**

That part did not answer within the time limit, so we cannot say if it passes. It is never counted as a pass or a fail. Run the matching checker on its own, or try the whole report again in a minute.

**Why are DANE and mail server TLS missing?**

They need a test that connects to your mail servers on port 25. We have not built that yet, so rather than guess, the report says they are not included and leaves them out of the level.

**Does it check subdomains?**

Yes, you can enter one. We check that exact name, and when its DMARC policy comes from the parent domain, the report says so. Mail for a subdomain that has no records of its own often relies on the parent.

**Can I use the result in a ticket or a chat?**

The Copy summary row gives a plain text version with the level, the counts and the fixes. The Copy summary for an AI row gives one line with the fix names, which suits a prompt.
