Gmail bulk sender requirements checklist
Review the public DNS and message-readiness signals Google describes for senders to personal Gmail accounts. This checklist is a diagnostic guide, not a guarantee that Gmail will accept or place every message.
Scan before reviewing Gmail
Check public DMARC, SPF, DKIM, MX, BIMI, MTA-STS, and TLS-RPT signals before changing DNS.
Check the public sender-auth records mailbox providers expect.
Keep one URL with evidence, owner steps, and decisions.
Add human review, provider context, and verification steps.
Review DMARC policy strength before a high-volume send.
- Public DNS evidence
- DMARC/SPF/DKIM status and caveats are visible before you pay.
- Owner-ready next step
- The audit adds provider context and a verification checklist.
Overall sender readiness
Needs attention
Sample output: one warning and one fail mean this domain is not campaign-ready yet.
Fix workspace preview
The scan becomes a focused work surface: evidence, owner action, verification, and the paid context a public lookup cannot infer.
Review DMARC policy strength before a high-volume send.
- Evidence
- Evidence: a monitoring-only policy can satisfy visibility needs, but enforcement requires aligned legitimate senders.
- Verify after change
- Re-scan _dmarc after DNS propagation and confirm aligned SPF or DKIM senders before enforcement.
- Paid audit adds
- Policy sequence, starter record review, alignment questions, and enforcement caveats.
What the official source says to review
Google's sender guidelines describe baseline requirements for all senders to Gmail personal accounts, plus additional requirements for senders above the 5,000 messages per day threshold. The public DNS part includes SPF or DKIM for all senders, and SPF, DKIM, and DMARC for bulk senders.
Gmail readiness checklist
- Authenticate the sending domain: Publish SPF and DKIM for the real systems that send mail, then confirm DMARC alignment against the visible From domain.
- Publish DMARC: Bulk senders should have a DMARC policy for the sending domain. Google notes that the policy can be p=none, which is monitoring, not enforcement.
- Keep DNS and transport basics healthy: Review forward and reverse DNS for sending IPs, TLS use, and standards-compliant message formatting.
- Treat unsubscribe and complaint rate as part of readiness: Marketing and subscribed messages need an easy unsubscribe path, and Google describes keeping spam rates below its published threshold.
Limits of a public DNS check
- A DNS scan cannot see Google Postmaster Tools, spam complaint rates, actual message headers, or campaign content.
- Passing SPF, DKIM, and DMARC does not guarantee inbox placement.
- Do not change SPF, DKIM, or DMARC records until every legitimate sender for the domain has been inventoried.
Gmail FAQ
Does Gmail require both SPF and DKIM for every sender?
Google describes SPF or DKIM for all senders to personal Gmail accounts, and SPF, DKIM, and DMARC for senders over its bulk threshold. If you send meaningful volume, review the bulk-sender section directly.
Is DMARC p=none enough?
Google says a bulk sender's DMARC policy can be set to none. That is useful for monitoring, but it does not enforce rejection or quarantine of failing mail.
Can SenderReady check unsubscribe headers?
Not from DNS alone. SenderReady can flag public DNS readiness, but unsubscribe headers require inspecting actual outgoing messages and campaign tooling.
Need a plain-English report?
SenderReady can turn public DNS findings into a cautious action list for your DNS, email, or IT admin. It does not guarantee inbox placement or legal compliance.