Google Postmaster Tools in 2026: setup, what survived v2, and reading it at low volume
The domain reputation chart everyone screenshotted is gone. What remains is narrower, more honest, and still the only free window into how Gmail sees you.
Google retired Postmaster Tools' domain reputation and IP reputation dashboards on September 30, 2025, along with the historical reputation data behind them. The v1 API followed by the end of the year. If your deliverability routine was "check whether the reputation badge is still green," that routine no longer exists, and Google replaced it with something narrower on purpose: a compliance checklist and a spam-rate chart.
Postmaster Tools is still the only first-party view of how Gmail sees your domain, which makes it required equipment for anyone doing the work in our email deliverability handbook. Here is the current state of it, how to set it up, and an honest section most guides skip: what the dashboards look like when you send fifty emails a day instead of fifty thousand.
What changed, and when
The v2 migration was a staged demolition. Google spent the summer of 2025 redirecting users from the v1 interface to v2. On September 30, 2025 the old dashboard went away entirely, taking domain reputation, IP reputation, and the historical reputation views with it. The v1 API shut down by the end of 2025. The v2 API reached general availability on February 3, 2026, and in June 2026 Google added a "Deliverability analysis" section inside the compliance dashboard that turns your sending data into plain-language verdicts with recommended actions.
The removal of the reputation charts annoyed a lot of senders, but the logic is defensible. The old badges were coarse (Bad, Low, Medium, High), lagged reality by days, and invited cargo-cult analysis of every wobble. What Google kept is the data you can act on: whether your authentication passes, and whether recipients mark you as spam.
Setting it up
You need control of the domain's DNS and a Google account. The whole process:
- Go to postmaster.google.com and sign in.
- Click the plus button, enter your sending domain (the domain in your From address, not your ESP's).
- Google gives you a verification TXT record. Add it at the root of your DNS zone:
yourdomain.com. TXT "google-site-verification=abc123exampletoken"
- Click Verify. DNS propagation usually makes this work within minutes.
- Wait. Data appears only after Google has seen enough of your mail, which can mean days for an active sender or indefinitely for a tiny one.
If you already verified the domain in Google Search Console, Postmaster Tools accepts that verification and you can skip the TXT record. Add every domain you send from, including subdomains used for bulk mail; Gmail tracks their spam rates separately.
What remains in v2
| Dashboard | What it shows | Why you care |
|---|---|---|
| Compliance status | Pass/fail on SPF, DKIM, DMARC alignment, PTR, TLS, one-click unsubscribe, and spam-rate thresholds | This is Gmail's bulk-sender checklist grading you directly |
| Spam rate | The percentage of your delivered mail that recipients mark as spam, daily | The reputation number now. The whole game |
| Delivery errors | Rejected and temp-failed mail as a percentage of attempts | Catches hard rejections you might otherwise never see |
| Authentication | Percentage of mail passing SPF, DKIM, DMARC | Should be a flat line at ~100%; any dip is an incident |
| Encryption | TLS percentage | Should also be ~100% on any modern relay |
| Feedback loop | Data for senders using the Feedback-ID header | Identifies which campaign or stream drives complaints |
The compliance dashboard is the one to open first. Since Gmail began hard-rejecting unauthenticated mail in November 2025, a failing row here does not mean "worse filtering someday," it means 550 rejections now. The full rule set is worth reading once in our breakdown of Gmail's bulk sender requirements.
Spam rate is the reputation number now
With the reputation badges gone, the spam-rate chart carries the load, and Google has published exact lines to hold: keep it under 0.1%, and treat 0.3% as the critical limit. Those numbers have teeth. At or above 0.3%, Gmail withholds delivery mitigation until you have been back under the line for a sustained stretch, which in practice means weeks of degraded inbox placement you cannot argue your way out of.
Two practical notes on reading the chart. First, the denominator is mail Gmail delivered, not mail you sent, so a small sender's chart is lumpy: one complaint on a 200-recipient day is 0.5%, a number that looks like an emergency and means one annoyed person. Second, stamp a Feedback-ID header on every send. Google offers no traditional feedback loop that returns individual complaints the way Yahoo and Microsoft do, so the Feedback-ID dashboard is how you find out which stream is generating the complaints your spam rate is counting. We put the header on every campaign send for exactly this reason, and our deliverability panel plots our own complaint data against the 0.1% and 0.3% lines so the thresholds are visible before Gmail's chart updates. The deeper mechanics are in our piece on spam complaint rate.
Automating it: the v2 API
The v2 API is free, OAuth-authenticated, and better than v1 in the ways that matter for automation: date-range queries, batch queries across multiple domains, and access to compliance status, not just the metrics. If you pull deliverability data into your own dashboards or alerting, this is the supported path, and since v1 is dead there is no other one.
We poll it as part of a monitoring stack that costs nothing: Postmaster Tools v2 for Gmail, Microsoft SNDS for Outlook's view of the sending IPs, Yahoo's complaint feedback loop (which also covers AOL), and mail-tester.com as a pre-send gate. Total spend, zero. For a small sender there is no paid tool in this category worth buying before those four are wired up.
Reading it at low volume: the honest section
Under roughly 100 emails a day to Gmail, most of these dashboards are empty most of the time. Google has never published the minimum volume that makes charts render, but the behavior is consistent: below some threshold, no data points appear for that day, and small senders see gaps or nothing at all.
We can report this first-hand. LetterDuck's own sending is dozens of emails a day, a live workspace running since June 2026, and our Postmaster charts are mostly blank. That is not a malfunction and it does not mean Gmail is ignoring your authentication or your complaint rate; the enforcement rules apply at any volume. It means the dashboard was built for senders with statistically meaningful daily Gmail volume, and you are not one yet.
What to do instead at that scale: verify the domain anyway (history starts accruing when volume arrives), watch bounce and complaint events from your ESP's webhooks since those fire on the first bad send, and test your setup directly rather than waiting for charts. We went as far as building a canary: every two hours a probe message runs our full production inbound path and alerts us if it fails to arrive, because at low volume silence in a dashboard is indistinguishable from broken. That system is written up in how we monitor inbound email.
Set up Postmaster Tools this week even if you send twenty emails a day. It costs one TXT record, the compliance dashboard grades you at any volume, and the day your list grows is the wrong day to start collecting history.