Gmail Postmaster Tools: A Practical Walkthrough

If a meaningful share of your mail goes to Gmail addresses, Google Postmaster Tools is the only direct view you'll get into how Gmail sees your sending. The data is delayed and aggregated, but it is also the closest thing to ground truth you can find.

What Postmaster Tools shows you

Postmaster Tools (PMT) is a free dashboard from Google that displays seven panels of data about a domain's sending to Gmail and G Suite addresses:

• Spam rate — the percentage of your mail Gmail's filters classified as spam.
• IP reputation — per-IP reputation buckets (Bad, Low, Medium, High).
• Domain reputation — reputation of your sending domain (the From or DKIM-signing domain).
• Authentication — pass rates for SPF, DKIM and DMARC.
• Encryption — percentage of mail encrypted with TLS.
• Delivery errors — reasons Gmail rejected or deferred mail.
• Compliance status — whether you meet the bulk-sender requirements (since Feb 2024).

Data appears with about 24 hours of delay and only when you exceed certain volume thresholds (a few hundred messages a day to Gmail). Below those thresholds the panels stay empty.

How to set it up

1. Go to postmaster.google.com and sign in with a Google account.
2. Click "Add a domain" and enter your sending domain. This is the domain in your DKIM d= tag, not your envelope-from. For most senders that's the same as your apex domain.
3. Google asks you to verify ownership by publishing a TXT record at the domain. Copy the value, paste it as a TXT at the apex, save.
4. Click "Verify" in the PMT UI. If your DNS has propagated, verification is instant.
5. Add additional sending domains the same way. You can verify many domains under a single Google account.

Verification gives you no additional capability except to view the dashboards — you don't grant Google any extra access to your mail.

Reading the spam rate panel

This is the most important number on PMT. It's the percentage of your authenticated mail that Gmail users actively classified as spam by clicking "Report spam." It does not include mail that ended up in spam folders by filter action.

Thresholds to know:

• Below 0.1% — healthy. Gmail's bulk-sender requirements ask you to "stay under 0.3%."
• 0.1–0.3% — warning zone. Watch the trend.
• Above 0.3% — you're failing Gmail's stated threshold for bulk senders. Reputation will degrade and inbox placement will drop.

The 0.3% number is a hard line in the sand since February 2024. Sustained complaints above it will get your bulk-sending capability throttled.

IP reputation panel

One row per IP that sent meaningful volume in the reporting window. Each is bucketed:

• Bad — almost all your mail goes to spam. Reputation is probably unrecoverable from this state on a short timescale.
• Low — spam folder placement is high. Recoverable but takes weeks of clean sending.
• Medium — mixed inbox and spam. Most accounts get inbox; some don't.
• High — consistent inbox placement. The goal.

If a previously-High IP slips to Medium, look at recent campaigns — usually the cause is a single bad send that you can identify within a day or two.

Domain reputation panel

Same buckets, applied to the sending domain. Important to remember: domain reputation is increasingly weighted over IP reputation by Gmail. An IP can be replaced; a domain has identity. If both are in the High bucket you're solid; if your domain is Low while your IP is High, the domain is the bottleneck and switching IPs won't help.

Authentication panel

Three lines for SPF, DKIM and DMARC pass rates over time. All three should be at or near 100%. Common failure causes:

• SPF dropping after you added a new sender without updating the record.
• DKIM dropping after a key rotation that wasn't propagated everywhere.
• DMARC dropping after a third-party sender changed its envelope-from to something that no longer aligns.

Pair this panel with your DMARC aggregate reports to identify exactly which sending source is failing — PMT shows you the rate, the reports show you the source.

Encryption panel

Percentage of mail you sent over TLS. Should be near 100% in 2026 — every modern MTA supports STARTTLS by default. Below 95% means you have a configuration issue, almost always on your sending side. Look at your MTA logs for outbound TLS handshake failures.

Delivery errors panel

The most overlooked panel. It lists categories of SMTP errors and their rates: rate limits, content rejection, authentication failures, bad addresses. A spike in any of these is an early-warning system. The two most common patterns:

• "Throttled by domain" — you're sending faster than Gmail accepts. Slow down per-recipient-domain.
• "User unknown" — bad addresses on your list. Trigger to revalidate before the next campaign.

Compliance status

Added in 2024 with the bulk-sender requirements. Six green ticks if you're compliant: SPF, DKIM, DMARC, low spam rate, valid PTR, and one-click unsubscribe. A red mark on any of them means you're at risk of being throttled if you exceed the bulk-sender volume threshold.

How to act on what you see

The general workflow:

1. Daily: glance at spam rate. If it's trending up, identify the campaign that caused it and look at the segment, content and timing.
2. Weekly: review IP and domain reputation. Investigate any drops.
3. After every campaign: check delivery errors for that day. Spikes are easier to attribute to a specific send.
4. Monthly: verify authentication is at 100%. If not, audit each failing source.

What PMT doesn't tell you

PMT is the best free Gmail-side data, but it has real limitations:

• It does not show inbox placement — only spam folder via active complaint.
• It does not show open or click rates.
• It does not break down by recipient cohort.
• It does not include G Suite (paid Workspace) accounts in the same buckets — those are reported separately.
• It does not exist for Outlook, Yahoo or any other receiver. Those have their own equivalents (SNDS for Microsoft) or no equivalent at all.

Use PMT alongside your own engagement metrics, your DMARC reports, and a seed-list inbox-placement service for a complete picture. For more on the wider stack, see our deliverability guide.