Skip to content
LookupOwl

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.

The domain in the From address of your mail.

It only changes labels: with No, the bulk rules are marked "Not required for you" and do not count in the verdict.

More options

Needed for the reverse DNS rule. Public IPv4 or IPv6 only.

Optional. Otherwise we look for common selectors, as the DKIM checker does.

Paste the headers of a message you sent (from Show original). In a browser with JavaScript they are read on your device and only 6 facts are sent: the From and envelope domains, the DKIM signature names, TLS, and two unsubscribe headers. W…

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.

RuleWho it applies toCan DNS settle it?
SPF or DKIM, one at leastEvery senderYes
Forward and reverse DNS for the sending IPEvery senderYes, once you give the IP
TLS, no gmail.com in From, message formatEvery sender (TLS is a Gmail rule only)No for TLS and format, yes for From
Spam rate under 0.3%Every senderNo, only the provider can see it
SPF and DKIM both, DMARC published, DKIM key at least 1024 bitsBulk sendersYes
Alignment and one-click unsubscribeBulk sendersOnly from a sent message
Visible unsubscribe link, unsubscribes honoured within 2 daysBulk sendersNo, 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 fromUse 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 senderWith No, the bulk rules stay visible and are marked "Not required for you". They do not count in the answer.
  3. Read the answerThe 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.

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 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. To see how the same domain scores across every mail record at once, run the email health check.

Fixing what fails

Questions people ask

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.

Use it from AI, the API or the command line

Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is sender_requirements_check. Please be kind to the rate limits.

curl
curl "https://lookupowl.com/api/v1/tools/sender-requirements?q=github.com"
MCP
claude mcp add --transport http lookupowl https://lookupowl.com/mcp