# Gmail, Yahoo and Microsoft Bulk Sender Rules Checker

Check a sending domain against the bulk sender rules of Gmail and Yahoo (13 rules) and Microsoft (4 rules): SPF or DKIM, SPF and DKIM for bulk, DMARC published, DKIM key length, no gmail.com From address, reverse DNS of a sending IP, TLS, one-click unsubscribe and alignment. Rules DNS can settle are pass, warn or fail with evidence and a fix; the rest are unknown, each with what would settle it (headers, sending_ip, external). Optionally pass the headers of a sent message (up to 256 KB, read in memory, never stored or logged) or a sending IP. Provider differences are shown per rule. Returns counts, never a letter grade, with the date the rules were last verified. Public domains only.

**Not for:** Reading one SPF, DKIM or DMARC record (use spf_check, dkim_check, dmarc_check).

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

## Input

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `domain` | string | yes |  | The domain in the From address of your mail, such as example.com. min length 1, max length 253 |
| `provider` | "gmail" \| "yahoo" \| "microsoft" \| "all" | no | `"all"` | Which provider's rules to check. gmail and yahoo are shown together on the Gmail and Yahoo page; microsoft has four rules of its own. |
| `bulk` | boolean | no | `true` | You send 5,000 or more messages a day to that provider's users. With false the bulk rules stay visible, marked "Not required for you", and do not count in the verdict. |
| `sendingIp` | string | no |  | The public IPv4 or IPv6 address your mail is sent from. Needed for the reverse DNS rule; a private address is refused. max length 45 |
| `dkimSelector` | string | no |  | The DKIM selector (the s= value of a signature). Without it we look for common selectors as the DKIM checker does. max length 63 |
| `headers` | string | no |  | The headers of a message you sent (Show original), up to 256 KB. Read in memory for this one request: never stored, logged, cached or put in an address. It settles the rules that need a sent message. max length 262144 |
| `fromDomain` | string | no |  | A fact read from a message in the browser: the domain in the From address. Sent instead of the headers when JavaScript read them. max length 253 |
| `envelopeDomain` | string | no |  | A fact read from a message in the browser: the domain of the envelope sender (Return-Path). max length 253 |
| `dkimSignatures` | string[] | no |  | A fact read from a message in the browser: one "d=example.com; s=selector" entry per DKIM signature. max 10 items |
| `tlsFirstHop` | boolean | no |  | A fact read from a message in the browser: the first hop used TLS. |
| `hasListUnsubscribe` | boolean | no |  | A fact read from a message in the browser: a List-Unsubscribe header is present. |
| `hasOneClick` | boolean | no |  | A fact read from a message in the browser: List-Unsubscribe-Post: List-Unsubscribe=One-Click is present. |

## 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 |  |
| `providers` | "gmail" \| "yahoo" \| "microsoft"[] |  |
| `mode` | "dns" \| "headers" \| "facts" | dns: records only. headers: the raw header was read on our server for this request. facts: the browser read the header and sent only six facts. |
| `bulk` | boolean |  |
| `summary` | object |  |
| `requirements` | object[] |  |
| `dnsSignals` | object |  |
| `usedHeadersFrom` | string \| null | The From domain of the message that was read, when one was. Never the header itself. |
| `headerNote` | object | other-domain: the message came from another domain than the one asked about. none-usable: the headers had no Received or Authentication-Results lines. |
| `failed` | "spf" \| "dkim" \| "dmarc" \| "reverse-dns"[] | Parts that could not be checked in time. The rules they feed are unknown with "could not check". |
| `inheritedFrom` | string \| null | The parent domain whose DMARC record applies, when the domain has none of its own. |

## Examples

### github.com, DNS only: 8 rules need a sent message

```json
{"domain":"github.com","provider":"all","bulk":true}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/sender-requirements?bulk=true&domain=github.com&provider=all'
```

Web page: https://lookupowl.com/gmail-yahoo-sender-requirements?q=github.com

### example.com sends nothing and fails the bulk rules

```json
{"domain":"example.com","provider":"all","bulk":true}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/sender-requirements?bulk=true&domain=example.com&provider=all'
```

Web page: https://lookupowl.com/gmail-yahoo-sender-requirements?q=example.com

### The four Microsoft rules for github.com

```json
{"domain":"github.com","provider":"microsoft","bulk":true}
```

```bash
curl 'https://lookupowl.com/api/v1/tools/sender-requirements?bulk=true&domain=github.com&provider=microsoft'
```

Web page: https://lookupowl.com/microsoft-sender-requirements?q=github.com

## Web pages

- https://lookupowl.com/gmail-yahoo-sender-requirements
- https://lookupowl.com/microsoft-sender-requirements

## Limits and caching

- Cost: 10 units for a live lookup, 1 unit for a cached one. Budgets are per network and published in the `RateLimit` response headers.
- Cache: the lifetime follows the data (for DNS, the record TTL, within a few minutes).
- Timeout: 20 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.
- [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.
- [DMARC Record Checker](https://lookupowl.com/tools/dmarc-checker.md): Look up and validate a domain's DMARC policy, report addresses and alignment settings.
- [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.
- [Email Header Analyzer](https://lookupowl.com/tools/email-header-analyze.md): Read the headers of an email: the route it took, the delay at each hop and whether it passed SPF, DKIM and DMARC, without storing anything.
- [SPF Flattener and Lookup Limit Fixer](https://lookupowl.com/tools/spf-optimize.md): Fix an SPF record that needs more than 10 DNS lookups: see what each include costs, pick the safest fixes and get the new record.

## Guide: Gmail and Yahoo sender requirements

Check a sending domain against the Gmail and Yahoo rules, and see what DNS can settle and what it cannot.

### What Gmail and Yahoo ask of senders

Since 2024 Gmail and Yahoo have asked every sender to authenticate mail, keep spam complaints low and use a proper From address. Senders of 5,000 or more messages a day to their users face more: both SPF and DKIM, a published DMARC record, alignment, and one-click unsubscribe. The checker lists all thirteen rules in one table, with Gmail and Yahoo side by side, because the two lists are almost but not exactly the same.

| Rule | Who it applies to | Can DNS settle it? |
|---|---|---|
| SPF or DKIM, one at least | Every sender | Yes |
| Forward and reverse DNS for the sending IP | Every sender | Yes, once you give the IP |
| TLS, no gmail.com in From, message format | Every sender (TLS is a Gmail rule only) | No for TLS and format, yes for From |
| Spam rate under 0.3% | Every sender | No, only the provider can see it |
| SPF and DKIM both, DMARC published, DKIM key at least 1024 bits | Bulk senders | Yes |
| Alignment and one-click unsubscribe | Bulk senders | Only from a sent message |
| Visible unsubscribe link, unsubscribes honoured within 2 days | Bulk senders | No, the body and your own records |

Where the two providers differ, the row says so. Yahoo lists no TLS rule and no gmail.com rule, accepts relaxed alignment, and advises the POST form of one-click unsubscribe while accepting a mailto: link. The rule text comes from each provider and carries the date we last checked it.

### How to check your domain

1. **Enter the domain you send from**: Use the domain in the From address of your mail, such as `example.com`. For a subdomain, the check follows DMARC up to the parent domain and tells you when it does.
2. **Say whether you are a bulk sender**: With No, the bulk rules stay visible and are marked "Not required for you". They do not count in the answer.
3. **Read the answer**: The answer is a count of rules met, with warnings and unknowns, never a letter grade. Open a row to see what the provider says, what we found and the fix.

> **In Claude, ChatGPT or Cursor** Connect the LookupOwl MCP server and ask: "Does example.com meet the Gmail and Yahoo sender rules?" The assistant calls `sender_requirements_check` and reads the same rule table.

### What DNS cannot show, and what would

Unknown is not a fail. A record in DNS can show that SPF is published and that a DKIM key exists, but it cannot show that a message passed, which TLS version a server used, or how many people marked your mail as spam. Each rule we cannot settle says what would: a sent message (its headers), your sending IP, the message body, or only the provider.

- Rule 2 needs the sending IP. Enter it under More options and we check the reverse name and that it resolves back.
- Rules 3, 5, 9 and 10 need the headers of a message you sent.
- Rules 4 and 12 can only be read from [Google Postmaster Tools](https://postmaster.google.com/) and the Yahoo complaint feedback loop.
- Rule 11 needs the message body, which no outside check can read.

### Checking a sent message without giving it away

Open a message you sent, choose Show original, and paste the headers under "Check a sent message". In a browser with JavaScript the headers are read on your device and only six facts are sent: the From domain, the envelope sender domain, the names in the DKIM signatures, whether the first hop used TLS, and whether two unsubscribe headers are there. Without JavaScript the text goes to our server for that one request. In both cases it is not stored, logged or put in the page address, and the page is never cached.

To read a whole message in detail, use the [email header analyzer](https://lookupowl.com/email-header-analyzer). To see how the same domain scores across every mail record at once, run the [email health check](https://lookupowl.com/email-health-check).

### Fixing what fails

- No SPF: build a record with the [SPF record generator](https://lookupowl.com/spf-record-generator).
- SPF over the limit of 10 lookups: use the [SPF flattener](https://lookupowl.com/spf-flattener) to see what each include costs.
- No DKIM: ask your sending service for its selector, then confirm the key with the [DKIM checker](https://lookupowl.com/dkim-checker).
- No DMARC: start with `p=none` from the [DMARC record generator](https://lookupowl.com/dmarc-record-generator) and read the reports before you tighten it.
- A sending address that is listed: check it with the [blacklist checker](https://lookupowl.com/blacklist-checker).

### Frequently asked questions

**What counts as a bulk sender?**

Both providers use 5,000 or more messages a day to their own users. Below that, only the rules for all senders apply. Once you pass the line you stay a bulk sender for the domain.

**Why are some rules unknown instead of pass or fail?**

Spam rate, TLS, message format and unsubscribe handling cannot be seen from DNS. Each unknown row says what would settle it, such as the headers of a message you sent. An unknown never counts against you.

**Does p=none satisfy the DMARC rule?**

Yes. Gmail and Yahoo only ask for a published record. A policy of none does not stop anyone pretending to be you, so the result adds a note when that is your policy.

**Are Gmail and Yahoo rules the same?**

Nearly. Yahoo lists no TLS rule and no gmail.com From rule, and it differs on alignment and one-click unsubscribe. The matrix shows each provider in its own column.

**Does this check mail sent to Google Workspace?**

Google says the rules cover mail sent to personal Gmail accounts. Mail to Workspace domains and mail inside one Workspace domain are not covered, though the same practices help.

**How current are the rules?**

Each result shows the date the rules were last verified against the providers' pages. If that date is more than 90 days old, the page says so and asks you to check the source.
