In one paragraph. Google Postmaster Tools v2 launched in 2024 with a new design and a Compliance status dashboard. Google's help center states that all dashboards from the old Postmaster Tools are available in v2 except the Domain and IP Reputation dashboards, which will be retired, and that the v2 API excludes Domain and IP reputation as well. Google later announced it was postponing the deprecation of the legacy web interface after sender feedback. IP reputation itself has not gone anywhere — only Google's published view of it.
The timeline in brief
- 2024 — Google launches the new Postmaster Tools (v2) alongside the existing interface. It introduces the Compliance status dashboard, which tracks adherence to Google's email sender guidelines.
- 2025 — Google announces that the old web interface will be deprecated and replaced by v2, that senders will be redirected automatically, and that the Domain and IP Reputation dashboards will be retired rather than carried over. The v2 API is released; Google states the v1 API will be retired.
- Later in 2025 — after sender feedback, Google announces it is postponing the deprecation of the legacy web interface, with timing to be shared later. The direction does not change: v2 is the product going forward, and the reputation dashboards are not part of it.
- Today — depending on your account, opening Postmaster Tools may take you straight to v2. Teams that relied on the IP Reputation dashboard need another source for per-IP visibility.
Because the exact dates have moved more than once, this page describes the state of the product rather than a countdown. The reliable facts are the ones Google has published: what v2 contains, what it does not, and why.
Dashboard by dashboard: legacy Postmaster Tools vs. v2
| Dashboard | What it shows | Legacy | v2 |
|---|---|---|---|
| Compliance status | Whether you meet the requirements in Google's email sender guidelines, with a deliverability analysis | — | New in v2 |
| Spam rate | Percentage of delivered mail that Gmail users manually mark as spam | Yes | Yes |
| IP Reputation | Bad / Low / Medium / High rating for each sending IP | Yes | Not included — to be retired |
| Domain Reputation | Bad / Low / Medium / High rating for the sending domain | Yes | Not included — to be retired |
| Feedback loop | Campaign identifiers with spam complaints (requires the Feedback-ID header) | Yes | Yes |
| Authentication | Share of mail passing SPF, DKIM and DMARC | Yes | Yes |
| Encryption | Share of mail sent over an encrypted (TLS) connection | Yes | Yes |
| Delivery errors | Percentage of authenticated mail rejected or temporarily failed, by error category | Yes | Yes |
Two things stand out. First, everything that remains is domain-level and Gmail-only: it describes how Gmail and its users react to your mail as a whole. Second, the only per-IP view Google ever offered is the one being retired. If you operate several SMTP servers or IP pools, nothing in v2 tells you which of them is the problem.
Why Google is retiring the reputation dashboards
Google's help center gives three reasons. Paraphrased: reputation data is not easily actionable for most senders; changes in sending behavior are slow to reflect in the dashboard; and a reputation label can be misleading because reputation is only one of many factors affecting deliverability. Google says replacement dashboards will provide clearer, more actionable insights.
These are reasonable criticisms of a four-step label. "Low" never told a sender what to fix, and by the time a rating moved the underlying problem was often days old. But the reasons are about the dashboard, not about the concept. Google's sender guidelines still say that the activity of any sender on a shared IP affects the reputation of all senders on that IP, that a negative reputation can impact delivery rate, and that senders should make sure their IPs are not on internet blocklists. Gmail's SMTP error reference still includes responses that temporarily rate-limit or reject mail because of the sending IP's reputation.
So the accurate summary is: Google changed the product; sending IPs still carry a reputation with every receiving system; and teams still need a way to see it move.
What it means for API users
If you pulled IP reputation programmatically — into a BI dashboard, an internal alerting job or a deliverability platform — that data path ends with the v1 API. According to Google, the v2 API includes all v1 functionality except Domain and IP reputation, adds endpoints for compliance status, domain management and batch operations, and uses a distinct data schema that requires client code updates.
Practically, that means two migrations: update your client for the v2 schema to keep spam rate, authentication, encryption and delivery error data flowing, and find a different source for the per-IP series. IP Reputation Monitor stores every daily result and, on the Command plan, exports history as CSV so it can be loaded into the same internal reports that used to consume the Postmaster feed.
Private reputation vs. independent monitoring
It helps to be precise about what any monitor can and cannot show:
- A mailbox provider's internal reputation — Gmail's, Microsoft's, Yahoo's — is private. It is computed from that provider's own observations (complaints, engagement, spam-trap hits, authentication, volume patterns, history) and is not exposed as a number. The legacy Postmaster dashboard was a coarse, delayed window onto Gmail's view; nothing else ever exposed it.
- An independent reputation score is a measurement built from signals that are observable from outside — infrastructure configuration, listings, reputation signals from multiple sources, consistency over time — consolidated into one scale. The Innova Reputation Score is this kind of measurement: 0–100, per IP, per day. It does not claim to be any provider's private value and it does not guarantee inbox placement.
The strength of an independent score is not that it reads Gmail's mind. It is that it is consistent: the same scale for every IP, every SMTP group and every day, so a drop from 86 to 74 on one address means something you can act on — and something you can see coming.
A migration checklist for sending teams
- Confirm your Postmaster Tools v2 access and review the Compliance status dashboard for any unmet sender-guideline requirement.
- Keep watching Spam rate and Delivery errors weekly at minimum; they remain the best Gmail-side symptoms.
- Move API integrations to v2 and remove any job that expected reputation fields.
- Inventory your sending IPs by SMTP server, customer, environment or pool — the structure you will monitor.
- Add an independent daily per-IP monitor so the "which IP?" question has an answer again. IP Reputation Monitor's free trial covers 5 IPs for 7 days.
- Define response thresholds: who is notified at Warning, what happens at Critical, and which logs to pull when a group total moves.