Free tool

Gmail and Yahoo bulk sender checker

Enter a sending domain and paste the headers of a marketing message to check them against the Gmail and Yahoo bulk sender requirements. No account needed. The domain is looked up in public DNS and is not stored, and the headers stay in your browser.

The SendRaven raven holding a wrench and a magnifying glass

Gmail and Yahoo bulk sender checker

Send one to yourself and copy its original source. DKIM, alignment, TLS and unsubscribe only show on a real message. The headers are read in your browser and are not sent anywhere.

Result

Nothing failing so far, 8 not shown by what you have entered.

  • Not shown
    SPF

    Enter a domain to check its SPF record.

  • Not shown
    DKIM

    DNS cannot list DKIM selectors. Paste a message's headers to check it, or test a selector with the DKIM checker.

  • Not shown
    DMARC, at least p=none

    Enter a domain to check its DMARC record.

  • Not shown
    From domain aligned with SPF or DKIM

    Depends on the message. Paste its headers to check it.

  • Not shown
    TLS when delivering (Gmail)

    Not visible in DNS. Paste a message's headers to check it.

  • Not shown
    Forward and reverse DNS for the sending IP

    Depends on the sending IP, which is your provider's to set up. A self-hosted server must publish a PTR record that resolves back to the same address.

  • Not shown
    One-click unsubscribe on marketing mail

    Not visible in DNS. Paste the headers of a marketing message to check it.

  • Not shown
    Spam rate below 0.3%

    Only the mailbox provider knows this. Read it in Google Postmaster Tools and Yahoo's Sender Hub.

How to read the result

Pass, fail, and what cannot be seen

Most checkers call a domain compliant from its DNS alone. DNS shows less than half of this list, so here anything out of sight says so.

From DNS

SPF and DMARC, read from the records a receiver reads.

From a message

DKIM, alignment, TLS and one-click unsubscribe. These depend on how the message was actually sent.

From the provider

Your spam rate, and whether reverse DNS on a shared sending IP is right. Only they can answer these.

Requirements read from Google’s sender guidelines and Yahoo’s best practices on 2 November 2026. A failing unsubscribe header? Build a correct one.

FAQ

Questions about the bulk sender requirements

What are the Gmail bulk sender requirements?

Anyone sending 5,000 or more messages a day to Gmail needs SPF and DKIM, a DMARC record with at least p=none, a From domain aligned with SPF or DKIM, forward and reverse DNS on the sending IP, TLS, messages that follow RFC 5322, a spam rate below 0.3%, and one-click unsubscribe on marketing and subscribed mail.

Are Yahoo's requirements the same?

Very close. Yahoo asks bulk senders for SPF and DKIM, a DMARC policy of at least p=none that passes, alignment, valid forward and reverse DNS, a spam rate below 0.3% and one-click unsubscribe. It accepts a mailto: target and highly recommends RFC 8058, and asks that unsubscribes are honored within 2 days. Yahoo publishes no volume threshold.

Do I count as a bulk sender below 5,000 a day?

Not at Gmail, where the line is 5,000 messages a day to personal accounts, and once you cross it you stay classed as a bulk sender. Smaller senders still need SPF or DKIM, forward and reverse DNS, TLS and a spam rate below 0.3%, so most of this list applies anyway.

Why does the checker say a requirement is not shown?

Because nothing you entered can show it, and a guess would be worse than no answer. DNS shows SPF and DMARC. DKIM, alignment, TLS and unsubscribe need a real message's headers. Your spam rate is known only to the mailbox provider, in Google Postmaster Tools and Yahoo's Sender Hub.

Does transactional mail need one-click unsubscribe?

No. The requirement covers marketing and subscribed messages. A password reset or a receipt is exempt, which is one more reason to send the two kinds from separate subdomains.

Next step

One-click unsubscribe and aligned signing on every campaign

SendRaven adds the unsubscribe headers and signs them, keeps marketing on its own identity, and warms up a new domain before it can burn.