Gmail Postmaster Tools: Gmail's own verdict on your mail
Almost everything a DMARC tool tells you is inference: it reads your DNS records and the aggregate reports receivers send back, then works out how the mailbox providers probably see you. Gmail Postmaster Tools removes the 'probably'. It is Gmail publishing its own verdict on the mail it actually received from your domain. Here's what it measures, what the grades mean, and how to read it next to your DMARC data.
What Gmail Postmaster Tools is
Postmaster Tools is a free Google service that reports on mail your domain sends to Gmail inboxes. Where DMARC reports tell you what happened during authentication, Postmaster tells you what Gmail decided about your mail after it arrived: whether it met Google's sender requirements, and how often real Gmail users pressed "Report spam" on it.
That last part matters because no DMARC report can see it. A domain can pass SPF, DKIM, and DMARC perfectly and still end up in the spam folder because recipients keep flagging its mail. Postmaster is the only place that number is published.
The compliance grades
Since the February 2024 bulk-sender rules, Gmail grades senders against its requirements and publishes the result as a compliance status. Each requirement comes back as COMPLIANT or NEEDS_WORK. The graded set covers eleven requirements, including:
- SPF, DKIM, and SPF and DKIM together - your mail authenticates with both mechanisms.
- DMARC policy - the sending domain publishes a DMARC record.
- DMARC alignment - the domain in the visible From header matches the domain that authenticated.
- User-reported spam rate- complaints stay under Google's guideline (more on the exact lines below).
- One-click unsubscribe and honoring unsubscribes - bulk mail carries the RFC 8058 header and opt-outs are processed promptly.
- TLS encryption, forward and reverse DNS, and message formatting - the transport-level hygiene rules.
Young or low-volume domains often show only a subset of grades. That isn't a failure; Gmail simply won't judge what it hasn't seen enough of.
The 0.10% and 0.30% spam-rate lines
The user-reported spam rate is the share of your delivered Gmail mail that recipients marked as spam. Google publishes two thresholds, and they are worth memorizing:
- 0.10% is the guideline. Google's sender requirements say to keep the rate below this line. Postmaster's own compliance verdict flags a sender the moment it crosses it.
- 0.30% is the rejection line. A sustained rate at or above this and Gmail starts rejecting or junking bulk mail from the domain. Getting back out of that state takes weeks of clean sending, not a DNS change.
There is no DNS record that fixes a spam-rate problem. The levers are list hygiene, expectations set at signup, easy unsubscribes, and sending volume consistency. The thresholds are Gmail's own; they are not configurable and no tool can negotiate them.
Why Gmail can disagree with a perfect DNS setup
The most valuable moment Postmaster gives you is a contradiction. Your DNS can look flawless from the outside - p=reject published, 100% alignment in your DMARC reports - while Gmail grades DMARC_ALIGNMENT or DKIM as needing work. When that happens, Gmail is not wrong. It is grading real traffic you cannot fully see: a subdomain stream you forgot, an internal tool sending unsigned mail only to Gmail addresses, or an ESP configuration that quietly regressed.
In trustyourinbox, that contradiction is surfaced directly: when a connected domain's Gmail grades contradict the DNS read, the Google + Yahoo compliance card flips to at risk with "Gmail disagrees with your DNS", and the Deliverability tab breaks down exactly which requirement Gmail flags. When the two agree, the card carries a "Confirmed by Gmail" chip: the verdict is no longer an inference.
How the connect works
Postmaster data is private to the domain owner, so connecting is a one-time proof of control, done from the domain's Deliverability tab in the dashboard:
- Open Deliverability on a sending domain and press Connect.
- If Google's registration API is available, you publish one DNS TXT record to prove control and verify. If it isn't (Google's v2 API currently rejects some automated registrations), the tab walks you through a guided three-step connect at postmaster.google.com instead: add the domain, grant read access, and press "check again".
- From then on, grades and the daily spam rate sync automatically once a day. No mail is redirected and nothing about your sending changes; the connection is read-only.
How to read it next to your DMARC data
Treat the two sources as complementary. DMARC aggregate reports are broad (every participating receiver, not just Gmail) and diagnostic: they tell you which source failed and why. Postmaster is narrow but authoritative: it is the receiver that matters most for many senders, publishing its actual verdict. When Postmaster flags something your DMARC data can't explain, start with the subdomains sending as you and unknown senders views; the stream Gmail is grading usually shows up there.
Keep reading
Which subdomains are sending email as your domain
Spoofers and forgotten tools send from your subdomains too. How to see every subdomain sending as you, tell a real one from a forgery, and close the gap with np and sp.
Protecting parked domains from spoofing
A domain that never sends mail is the easiest one to spoof. Three DNS records lock it down for good: SPF -all, DMARC p=reject, and a null MX.
What to do when a report shows Unknown senders
Some rows in your DMARC reports won't have a vendor name attached. Just a bare source IP marked Unknown. Here's the triage guide: what aligned-vs-not means, how to figure out who the IP actually belongs to, and when an Unknown is safe to ignore.
Free for one domain. Set up in five minutes. We parse the reports; you read plain-English summaries.