What are the bulk sender requirements?
Gmail and Yahoo ask every sender to authenticate mail with SPF or DKIM, give sending IPs working reverse DNS and keep spam complaints under 0.3%. Bulk senders must also use both SPF and DKIM, publish DMARC and offer one-click unsubscribe. Microsoft set similar authentication rules for Outlook.com addresses in May 2025.
Reading the result
Five requirements can be read from DNS, and each gets a verdict: SPF, DKIM, DMARC, whether alignment is possible and, if you enter the sending IP, its reverse DNS. Open any of them to see each provider's own rule, restated, with a link to the page it comes from. TLS, spam rate, unsubscribe headers and message format are listed apart, because DNS cannot show them.
Beat runs on the same engine, on a schedule, across all 41 checks and 25 blacklists. What it adds is asking again, noticing when an answer changes and telling you what to do about it.
Common problems it finds
No DMARC record
All three providers ask bulk senders for one. p=none meets the rule, so you can publish it today and tighten the policy once the reports show your senders pass.
DKIM on a selector we did not try
DNS cannot list selectors, so without yours the tool asks the 21 that common providers use. If it finds none, enter the selector named in the s= tag of a DKIM-Signature header from a message you sent.
Alignment that rests on SPF alone
If your sending platform uses its own Return-Path domain and signs with its own DKIM domain, nothing aligns with your From address and DMARC fails while SPF and DKIM both pass. A DKIM key on your own domain fixes it.
No reverse DNS on the sending IP
Gmail and Yahoo require a PTR record whose hostname resolves back to the same IP. Your hosting or sending provider sets it, not your DNS host.
Unsubscribes honoured too slowly
Google's FAQ asks for unsubscribes to be honoured within 48 hours and Yahoo within 2 days. DNS cannot show this, so test it by unsubscribing from your own mail.