For years, Google Postmaster Tools gave senders a reputation label – High, Medium, Low, or Bad – and left them to figure out what was causing the problem. The labels were opaque by design. You could watch your reputation slide from High to Medium and have no direct signal as to whether the culprit was your SPF configuration, your DKIM signing, your list quality, or something else entirely.
That model is gone. Google retired Postmaster Tools v1 in 2026, and in early June the company added a new Deliverability Analysis section to the Compliance Status page in v2. The new section replaces the reputation label system with an explicit compliance checklist. You can now see exactly which authentication requirement is failing, exactly where your spam rate sits relative to the thresholds that trigger enforcement, and exactly what is sending your mail to the spam folder or to outright rejection.
This is a meaningful operational change for anyone sending bulk mail to Gmail. It is also a signal about how Google intends to manage the enforcement relationship with senders going forward – less ambiguity, harder edges, specific numeric thresholds that carry defined consequences.
What the New Deliverability Analysis Section Shows
The Deliverability Analysis section surfaces four categories of compliance signal that Google evaluates for every sending domain it tracks:
SPF alignment. Whether your outbound mail is sent from IP addresses authorized by your SPF record, and whether the SPF domain aligns with the From header domain. Partial alignment – where SPF passes but on an unrelated domain – no longer satisfies Google’s requirements for bulk senders.
DKIM alignment. Whether your mail carries a valid DKIM signature from a key published under your sending domain, and whether that signature covers the From header domain. DKIM must be signing from your own domain, not a third-party ESP domain, to satisfy alignment requirements.
DMARC policy. Whether you have a DMARC record published for your sending domain, and what policy it specifies. Google no longer treats p=none as a meaningful compliance signal for bulk senders. The checklist notes policy level. It does not reject p=none mail outright, but the absence of p=quarantine or p=reject is reflected in your compliance posture.
One-click unsubscribe. Whether your bulk mail carries both the List-Unsubscribe and List-Unsubscribe-Post headers as required by RFC 8058. A footer unsubscribe link is not sufficient. The header must be present, and the unsubscribe action must be processed within two business days.
Each item shows as either compliant or non-compliant for the sending domain in question. There is no partial credit and no “improving” status. You either pass the check or you do not.
The Spam Rate Threshold Is Now a Functional Kill Switch
The most operationally significant change in the new interface is how Google presents the spam rate threshold. In v1, spam rate was one signal among many feeding into an aggregate reputation score. In v2, it is presented as a standalone metric with two explicitly labeled thresholds.
The recommended ceiling is 0.10 percent. At this level, Google’s filters begin factoring complaint signals more heavily into inbox placement decisions. Senders above 0.10% see deliverability degradation that may not be immediately obvious – fewer messages landing in the primary inbox, more routed to spam – without receiving an explicit error at the SMTP level.
The hard ceiling is 0.30 percent. Exceeding this threshold puts the sending domain into a category where Google issues permanent 5xx SMTP rejections. The mail does not go to spam. It does not get deferred. It is rejected at the connection level with a permanent error code. From Gmail’s perspective, a domain operating above 0.30% spam rate has demonstrated that it cannot be trusted to manage its own sending hygiene, and the appropriate response is to stop accepting its mail entirely.
Recovering from a 0.30% threshold breach is not a matter of simply cleaning your list. Google requires a sustained period of improved metrics – typically several weeks of sending with sub-0.10% complaint rates – before automatic enforcement is lifted. During that period, your mail to Gmail accounts is rejected regardless of authentication status. A domain in that state has effectively lost access to Gmail as a delivery destination until it earns its way back.
What Is Changing in September 2026
Google announced that additional changes to Postmaster Tools will take effect in September 2026. The company has not fully disclosed the scope of those changes, but several signals from the announcement and from the current v2 interface are worth noting.
The Deliverability Analysis section currently monitors the four signals described above. Industry observers familiar with Google’s direction expect the September update to expand the set of monitored signals to include click-through engagement patterns, unsubscribe complaint rates as a distinct metric from spam complaint rates, and potentially expanded DKIM key size requirements. The 1024-bit DKIM key minimum that Google introduced previously may move to a 2048-bit minimum, which requires DNS record updates from any sender still using shorter keys.
What is confirmed is that Postmaster Tools v2 will not revert to the older model. The explicit compliance checklist is the format Google intends to maintain going forward. Senders who have been relying on the opaque reputation signal to identify problems will need to adapt to working with specific, auditable compliance categories.
What a Low Reputation Score in v2 Actually Tells You
One of the practical improvements in v2 is that the relationship between compliance status and reputation score is now traceable. In v1, a reputation decline could be caused by any number of things and the score itself gave no directional information. In v2, you can check the Deliverability Analysis section and determine whether the reputation signal correlates with a specific compliance failure or whether it is driven by complaint volume alone.
This distinction matters because the remediation path is different in each case. A reputation problem caused by a failed DKIM alignment check requires a DNS and ESP configuration fix. A reputation problem caused by elevated complaint rates requires list hygiene – removing unengaged subscribers, tightening opt-in practices, reducing send frequency to inactive segments. Conflating the two leads to senders making configuration changes that have no effect on complaint-driven reputation problems, or running re-engagement campaigns that do nothing to address authentication failures.
The v2 interface separates these signals. If your Deliverability Analysis section shows all four compliance items passing and your reputation is still declining, the problem is in your list quality and complaint rate, not in your authentication setup. If a compliance item is failing, that is where to start.
The Practical Checklist for Postmaster Tools v2
Every sender with a domain that reaches Gmail inboxes should take the following steps now, before the September changes take effect:
Log into Postmaster Tools v2 and navigate to the Compliance Status page for each verified domain. The Deliverability Analysis section is on this page. Check whether all four items are listed as compliant. If any are not, the section will indicate which specific check is failing.
Verify that your DKIM signing is configured to sign from your own domain rather than your ESP’s domain. If your emails carry a DKIM signature like d=sendgrid.net or d=mailchimp.com but your From address is @yourcompany.com, DKIM alignment is failing and the Deliverability Analysis section will reflect this.
Confirm that your bulk sending infrastructure includes List-Unsubscribe and List-Unsubscribe-Post headers on all commercial messages. This is a header-level implementation, not a footer link. If your ESP does not generate these headers automatically, it needs to be configured to do so, or you need to add them programmatically.
Monitor your spam rate weekly, not monthly. A rate that crosses 0.10% requires action within days, not weeks. At 0.30%, the domain is at risk of automatic enforcement that takes weeks to recover from. The Postmaster Tools v2 interface shows current spam rate clearly; the new Deliverability Analysis section puts it in context alongside your compliance status.
Excello Mail gives you DMARC aggregate report visibility, sending source monitoring, and authentication compliance tracking across all your domains – the same signals that Google Postmaster Tools v2 now surfaces, available in one place with actionable diagnostics. Sign up for free to Excello Mail and make sure your sending infrastructure passes every check before September.