Google Postmaster Tools is a free dashboard that shows how Gmail sees the mail your domain sends: your user-reported spam rate, whether you meet Gmail’s sender requirements, authentication and encryption pass rates, and why messages were rejected. To use it, you add the domain you sign mail with, prove you own it with a DNS record, and wait for enough Gmail traffic to generate data. It’s the closest thing you get to a direct readout from Gmail’s filters.

This guide covers setup, what each dashboard tells you, and a weekly routine for acting on the data. One thing has changed since many older tutorials were written: the current version (v2) no longer includes the Domain Reputation and IP Reputation dashboards. If you relied on those, our post Postmaster Tools v2 retired reputation scores. Now what? covers what to watch instead. Here we focus on getting value from what’s still there.

What Google Postmaster Tools shows in 2026

Google’s Postmaster Tools dashboards page describes the current set. Google’s deprecation notice says the Domain and IP Reputation dashboards are being retired, all other legacy dashboards are carried into v2, and the v2 API covers everything except reputation while adding compliance status endpoints. The legacy interface’s shutdown was postponed after sender feedback, but the direction is clear: plan around v2.

Dashboard	What it tells you	When to look
Compliance status	Whether you meet each Gmail sender requirement	Weekly, and after any DNS or platform change
Spam Rate	Share of inboxed mail that users marked as spam	Weekly; daily during big campaigns
Feedback Loop	Spam rates by your own campaign or customer identifiers	When spam rate rises and you need to find the source
Authentication	Share of traffic passing SPF, DKIM, and DMARC	After adding a new sending tool
Encryption	Share of traffic sent over TLS	Once, then occasionally
Delivery Errors	Rejected and temporarily failed traffic, with reasons	Whenever bounce rates at Gmail jump

How to set up Google Postmaster Tools

Setup takes about 10 minutes plus DNS propagation. These steps follow Google’s Set up Postmaster Tools help article.

Pick the right domain. Add the domain you use to authenticate outgoing mail. That’s the DKIM signing domain (the d= value) or the SPF domain (the Return-Path domain). For most senders it should be the same as your From domain, like example.com.
Sign in at postmaster.google.com with a Google account. Use a shared team account or add colleagues later so access doesn’t live in one person’s inbox.
Add the domain. On the Manage Domains page, click Add new domain and enter it.
Verify ownership. Choose Verify domain and copy the record Google gives you. Add it at your DNS host. A TXT verification record looks like this:
```
example.com.  IN TXT  "google-site-verification=AbCdEf123..."
```
Wait for verification. Google says verification usually happens right away but can take up to 10 minutes to show. Leave the record in place afterward.
Add users. Grant access to anyone else who needs the dashboards, such as your ESP’s deliverability contact.

Which domain should you add?

Add the organizational domain (example.com). Google’s sender guidelines treat subdomains under the same primary domain together for bulk-sender counting. If you sign with a separate subdomain like mail.example.com, you can add that too. For senders who use different domains for different streams, add each one.

Why is my Postmaster Tools dashboard empty?

The most common reasons:

Not enough volume. Google says dashboards might not include all data on days when volume is low. Small senders often see gaps or nothing at all.
Wrong domain. If your mail is DKIM-signed by your ESP’s domain instead of yours, the traffic doesn’t count toward your domain.
Too soon. Data updates daily. Give it a few days after verifying.

If you send only a few hundred messages a day to Gmail, Postmaster Tools may stay mostly empty. That doesn’t mean something is wrong.

Reading the Compliance status dashboard

This is the dashboard to check first. It lists each requirement from Google’s Email sender guidelines and marks it Compliant, Needs work, or No data found. Google says some requirements apply only to bulk senders, defined as around 5,000 or more messages to Gmail accounts in a 24-hour period.

Things to know:

Status uses a rolling average over multiple days. Google notes changes can take up to 7 days to show. If you fix a DNS problem today, don’t panic when it still says “Needs work” tomorrow.
Deliverability analysis sits under this dashboard. It gives recommendations when you send too little mail, when messages fail to deliver, when spam exceeds the recommended threshold, or when recipients don’t engage with your mail.

What to do with a “Needs work” status

Requirement flagged	Where to look	Typical fix
SPF and DKIM	Authentication dashboard, a sample message’s headers	Publish missing record, add custom DKIM at your ESP
DMARC	DNS lookup of `_dmarc.example.com`	Publish at least `v=DMARC1; p=none`
DMARC alignment	Message headers (`header.from` vs `d=`)	Sign with your own domain, not the platform’s
TLS	Encryption dashboard	Enable STARTTLS on your MTA
Forward and reverse DNS	PTR lookup on sending IPs	Ask your provider or host to set a matching PTR
User-reported spam rate	Spam Rate dashboard	See below
One-click unsubscribe	Message headers	Add `List-Unsubscribe` and `List-Unsubscribe-Post`, DKIM-sign both

For a step-by-step audit of each requirement, see our Gmail and Yahoo bulk sender requirements guide.

Reading the Spam Rate dashboard

The spam rate is the single most important number in Postmaster Tools. Google’s dashboard documentation defines it as the share of messages delivered to the inbox of engaged recipients that those recipients then marked as spam. Mail that went to spam and was then marked “not spam” counts as delivered to the inbox. The dashboard shows spam rate for DKIM-authenticated mail.

Two things follow from that definition:

Mail filtered to spam doesn’t count against you here. A low spam rate when most of your mail lands in the spam folder is not good news. Pair this dashboard with delivery errors and your own engagement data.
It reflects your recipients, not your content alone. Complaints come from people who don’t recognize you or don’t want your mail anymore.

Google’s guidelines say to keep the rate below 0.1% and never let it reach 0.3%. Bulk senders with a spam rate above 0.3% lose eligibility for mitigation help until the rate stays below 0.3% for 7 consecutive days, per Google’s sender guidelines FAQ. We go deeper in Gmail’s spam rate threshold.

Translating the percentage into complaints

A spam rate is easier to act on when you think in absolute numbers. At 0.1%, one in every 1,000 inboxed messages gets a spam report. If you send 50,000 messages to Gmail and most reach the inbox, about 50 complaints puts you at the recommended ceiling. About 150 puts you at the hard limit.

Using the Feedback Loop dashboard

The Gmail Feedback Loop breaks spam rates down by identifiers you add to your mail. You add a Feedback-ID header:

Feedback-ID: spring-sale:newsletter:promo:exmpl01

The format is a:b:c:SenderId. The first three fields are optional identifiers you choose, such as campaign, customer, or mail type. The last field, the SenderId, is required, must be 5 to 15 characters, and should stay consistent across your mail stream. The header must be covered by a DKIM signature from a domain you’ve verified in Postmaster Tools.

Gmail reports aggregate data, not individual complaint messages, and only for identifiers that appear in enough volume and enough distinct spam reports on a given day. ESPs that send for many customers use this to find which customer is causing complaints. A single brand can use it to compare newsletters against promotions, or a new list segment against an old one. Our explainer on email feedback loops compares Gmail’s approach with Yahoo and Microsoft.

Reading the Authentication and Encryption dashboards

The Authentication dashboard shows what share of your traffic passed SPF, DKIM, and DMARC. A sudden drop usually means one of these:

A new tool (CRM, help desk, invoicing app) started sending as your domain without DKIM set up.
A DKIM key was rotated and the new selector wasn’t published.
An SPF include was removed, or the record exceeded the 10-lookup limit set in RFC 7208.

The Encryption dashboard should read close to 100% for TLS. If it doesn’t, your MTA isn’t offering STARTTLS.

Reading the Delivery Errors dashboard

Delivery Errors shows the share of your traffic Gmail rejected or temporarily deferred, with a reason category. A spike here is often the first sign of trouble. Line up the date of the spike with what changed: a new list import, a new IP, a sending tool change, or a big jump in volume.

If errors point to bad addresses or high bounce rates, the problem is upstream in your list. Screen imports and signups before they reach your sending platform. Our free email verifier catches syntax errors, domains without MX records, disposable and role-based addresses, and common typos like gamil.com. It doesn’t log in to the mailbox over SMTP, so pair it with bounce handling for addresses that look valid but don’t exist.

A weekly Google Postmaster Tools routine

Open Compliance status. Anything other than Compliant gets a ticket.
Open Spam Rate for the last 30 days. Note any day above 0.1% and match it to the campaign you sent that day.
If a spike lines up with a specific campaign, check the Feedback Loop data for that identifier.
Glance at Authentication and Delivery Errors for drops or spikes.
Write down what you sent, to whom, and what changed. Postmaster data is only useful if you can tie it to your own sending log.

What Google Postmaster Tools can’t tell you

Inbox placement. It doesn’t tell you what percentage of mail went to spam. Use seed testing; see inbox placement testing.
Per-recipient data. You never see which person complained.
Other providers. Yahoo, Microsoft, and Apple have their own tools. For Outlook, see Microsoft SNDS and JMRP.
Reputation scores. v2 dropped them. Use spam rate, delivery errors, and compliance status as your health signals.

FAQ

Is Google Postmaster Tools free?

Yes. You only need a Google account and the ability to add a DNS record for the domain you want to monitor. There’s no paid tier.

Why doesn’t Postmaster Tools show my domain reputation anymore?

Google is retiring the Domain and IP Reputation dashboards, and the v2 interface and API don’t include them. Google said reputation data was hard to act on and slow to reflect changes. Use the Compliance status, Spam Rate, and Delivery Errors dashboards instead.

How long does it take for data to appear?

Verification is usually immediate, but data appears only once Gmail has enough traffic from your domain to report on, and it updates daily. Low-volume senders may see gaps or no data at all.

Should I add my ESP’s domain or my own domain?

Your own. Add the domain in your From address and the one your mail is DKIM-signed with. If your ESP signs with its own domain, set up custom DKIM first, or your traffic won’t show up under your domain.

Google Postmaster Tools: A Practical Guide for 2026