Google has retired the legacy Postmaster Tools interface and permanently removed Domain and IP Reputation. Here is what actually changed, why Google did it, and how to read sender health now that the score you relied on no longer exists.
The short version
- Postmaster Tools V1 is being switched off. There was no final announcement – access is being revoked domain by domain, so most senders discover it when they log in and land on V2.
- Domain Reputation and IP Reputation are gone permanently. Not renamed, not moved. Removed.
- Every reputation trend chart you had is unrecoverable. If it was not exported, it is lost.
- V2 replaces the score with a Compliance Status dashboard and a plain-English deliverability verdict.
- Spam complaint rate is now your primary dial: stay under 0.10%, and never reach 0.30% along with the Deliverability Signal – closest alternative of domain reputation.
What actually happened
The retirement of Postmaster Tools V1 has been one of the most confusingly communicated changes in recent deliverability memory, so it is worth laying out the sequence plainly.
Google first set a retirement date of 30 September 2025. Then, in November 2025, it reversed course: after significant pushback from senders and deliverability consultants, Google publicly postponed the deprecation and left V1 running with no replacement date announced.
That reprieve has since ended. Through 2026 the pause was quietly lifted and V1 access was withdrawn in waves. The result is an unusually uneven rollout: some senders lost access months ago, a handful can still reach the legacy dashboards today, and Google’s own help documentation has lagged behind the reality on the ground.
Why this matters
There is no date to plan around and no notification email. The practical assumption to work with is that V1 is already gone for you, or will be within weeks – and that anything you still need from it should be exported today, not scheduled for later.
What is gone, what stayed, and what is new
Most of V1 survived the move. The exception is the part everyone actually looked at first.
| Gone for good | Still available in V2 | New in V2 |
| Domain Reputation (Bad / Low / Medium / High) IP Reputation dashboard All historical reputation trend charts The V1 web interface The V1 Postmaster Tools API is retired; existing V1 API calls return 404. | Spam complaint rate, calculated daily Authentication: SPF, DKIM and DMARC Delivery errors Encryption (TLS) Feedback loop reporting Google has a V2 Postmaster Tools API for the metrics that remain in the dashboard. | Compliance Status dashboard Deliverability analysis (added June 2026) Reporting across date ranges Multi-domain reporting in one view Report Delivery Issue — lets senders raise a support ticket with Google directly from Postmaster Tools when they believe Gmail is affecting their mail delivery. |
Why Google retired the reputation dashboards
This was not a casualty of a UI refresh. Google gave three specific reasons, and they are worth understanding because they explain the direction of everything that follows.
- The data was not actionable. A rating of “Low” told you something was wrong but not what to change, and gave no path to fixing it.
- It responded too slowly. The score moved slowly and lagged behind the sender behaviour driving it, so teams often could not tell whether a fix had worked.
- It was misleading in isolation. Reputation is one input among many. A green score created false confidence, and a poor one triggered panic that was sometimes misplaced.
Read together, this is a philosophical shift rather than a feature cut. Google has moved senders away from monitoring a summary judgement and towards monitoring the behaviour that produces it. Gmail still calculates reputation internally and still uses it to filter your mail. It has simply stopped showing it to you.
What replaced the score
V2 answers the reputation question in two separate places, and the distinction between them is the single most useful thing to understand about the new interface.
Compliance Status
A direct check on whether you meet Gmail’s bulk sender requirements – authentication, valid records, and adherence to the sender guidelines. This is a pass-or-fail hygiene check, and it should always read as compliant.
Deliverability analysis
Added in June 2026, this states a verdict in plain English rather than leaving you to interpret graphs. In practice the verdicts fall into three buckets:
- “Users signal they want to get your email messages” – the healthy state, indicating genuine positive engagement signals
- “Gmail sees no clear signal” – usually low volume or insufficient data, not a problem in itself
- “Users signal they do not want your messages” – the warning state, and the one that needs immediate attention
Read these two independently
The deliverability verdict and your spam complaint rate are separate metrics that answer different questions. Spam rate tells you how many people actively complained. The verdict tells you whether people want your mail at all. A clean spam rate alongside a negative verdict is entirely possible – and it usually means disengagement rather than complaints is your real problem.
The metrics that matter now
With the score gone, sender health becomes a composite read across a handful of signals. These are the ones worth building a monitoring routine around.
| Metric | Target | Why it matters |
| Spam complaint rate | Below 0.10%; never reach 0.30% | The most important number still visible to you. Calculated daily, and directly tied to Gmail’s bulk sender requirements. |
| Compliance status | Compliant, always | A failure here is a hygiene problem with a known fix. There is no reason to sit in a non-compliant state. |
| Deliverability verdict | Positive engagement signal | The closest replacement for reputation, and the fastest read on whether your audience actually wants your mail. |
| Authentication | SPF, DKIM and DMARC passing at 100% | Partial failures often point to an unapproved or misconfigured sending source. |
| Delivery errors and blocks | Investigate any sustained rise | Error and block reason codes carry the diagnostic detail the reputation score used to summarise for you. |
| Engagement and list quality | Trending stable or upward | The input you genuinely control, and now the main lever behind everything above. |
Two additions are worth making on top of Postmaster data. First, seed or inbox placement testing, which tells you where mail is landing rather than only whether it was accepted. Second, complaint tracking at campaign level, which localises a spike to the specific send that caused it instead of leaving you with a domain-wide average.
Gotchas nobody mentions
- Compliance status is primary-domain only. The Compliance Status dashboard reports on your primary domain only. It uses subdomain data to reach its verdict but will not show you the subdomain view. If you run separate promotional and transactional subdomains, this dashboard cannot tell you which one is causing a problem.
- Without a score, you need your own baseline. Reputation repair used to be provable: you showed the client the score climbing from Low to Medium to High. That evidence no longer exists, so remediation work now needs a baseline you establish yourself before making changes.
- Historical data is unrecoverable. When V1 access was withdrawn, the reputation trend charts went with it. There is no archive and no export path after the fact.
- Your rollout may not match anyone else’s. Because access was revoked in waves rather than on a fixed date, two people on the same account can genuinely be looking at different interfaces. Confirm which version someone is on before troubleshooting what they are seeing.
