Free, reads live DNS
Gmail and Outlook sender check
Checks the authentication and transport records Gmail and Outlook read before they trust your mail. Since the 2024–2025 enforcement waves, bulk senders must pass these.
Sender Readiness: /100
for
Direct answer
What do Gmail and Outlook require from bulk senders?
Since February 2024, Gmail and Yahoo require bulk senders to authenticate mail with SPF and DKIM, publish a DMARC record, and keep the spam complaint rate low. Microsoft applies similar authentication checks for Outlook. This page reads those DNS records for one domain. It cannot open the reputation charts inside Google Postmaster Tools, which only the domain owner can see.
- Bulk, for Gmail, means about 5,000 messages a day to personal Gmail accounts. The authentication rules are worth meeting below that volume too.
- SPF or DKIM must pass and align with the From domain. Passing on a vendor domain while the From is yours does not satisfy DMARC.
- A DMARC record of p=none meets the published requirement. It does not stop someone else from spoofing the domain.
- A one-click unsubscribe and a low complaint rate are also required. Neither of those is a DNS record, so this check cannot see them.
Questions people ask
Is this Google Postmaster Tools?
No. Google Postmaster Tools shows spam rate, domain reputation, and delivery errors to the verified owner of a domain. This audit only reads the public DNS records those requirements depend on. If the records fail here, Postmaster data will not fix delivery until the DNS is corrected.
Does p=none satisfy Gmail?
Gmail’s bulk-sender guideline asks for a DMARC record. p=none qualifies. Gmail still recommends moving to enforcement. A none policy will not reject forged mail.
What if SPF passes and DKIM fails?
DMARC passes when either SPF or DKIM passes and aligns. One aligned pass is enough. Both is safer, because forwarding often breaks SPF and leaves DKIM as the only aligned check.
Why does a new domain still land in spam after this passes?
Authentication proves the mail is yours. Reputation decides whether the inbox wants it. A domain with no sending history needs a slow warmup after these records pass.
The records are only half of inbox placement.
Once SPF, DKIM, and DMARC pass, a cold domain still needs a slow sending history. iSend warms the domain and sends with the same authentication these tools just checked.