Gmail Postmaster Tools and Microsoft SNDS report sender reputation in fundamentally different ways. How to read both dashboards and act on what they actually show.
Gmail and Microsoft together handle the majority of consumer inboxes, and both offer free dashboards that expose how their filters see your mail. The problem is that Postmaster Tools and SNDS measure different things, at different granularities, with different delays. Senders who read one as if it were the other draw the wrong conclusions and fix the wrong problems.
Key Takeaways
- Postmaster Tools reports domain-level reputation; SNDS reports per-IP data only
- The Postmaster spam rate is user reports divided by inboxed mail, not total sent volume
- SNDS color bands are driven by spam filter verdicts, complaint rates, and trap hits
- Both dashboards go silent below volume thresholds, and silence is not a signal of health
- Neither tool shows you the full picture; pair them with your own bounce and engagement data
Two dashboards, two philosophies
Google built Postmaster Tools around identity. Reputation is tracked against the authenticated domain, which means your DKIM d= domain or SPF domain carries the history, wherever the mail is physically sent from. Microsoft built SNDS around infrastructure. You register IP ranges, and the dashboard tells you what Outlook.com filters observed from each address on each day.
That design difference explains most of the confusion. A domain migration barely registers in SNDS but resets your Postmaster history. A new IP pool shows up as unknown territory in SNDS while Postmaster Tools keeps reporting a healthy domain. Neither view is wrong; they answer different questions.
Postmaster Tools vs. SNDS at a glance
| Feature | Gmail Postmaster Tools | Microsoft SNDS |
|---|---|---|
| Tracking unit | Authenticated domain | Individual IP address |
| Reputation scale | Bad, Low, Medium, High | Green, Yellow, Red bands |
| Complaint data | User-reported spam rate (%) | Complaint rate < 0.1%, < 0.3%, or above |
| Spam trap visibility | Not exposed | Trap message count per IP |
| Minimum volume to see data | Roughly hundreds per day | About 100 messages per IP per day |
| Data delay | 2 to 3 days | 1 to 2 days |
Reading Gmail Postmaster Tools
Domain and IP reputation
The domain reputation chart is the single most predictive signal in the dashboard. High means your mail is overwhelmingly landing in the inbox. Medium usually means some campaigns or segments are getting filtered. Low and Bad mean the spam folder is your default destination, and recovery is measured in weeks of clean sending rather than days.
IP reputation in Postmaster Tools is secondary for most senders. Gmail weights domain identity heavily, so a shared IP with mixed history matters less than it does at Microsoft. If domain reputation is High and IP reputation is Medium, trust the domain signal.
The spam rate chart
The user-reported spam rate is calculated as the number of Gmail users who mark your mail as spam divided by the number of messages delivered to the inbox. Mail that already lands in the spam folder cannot be reported, so a worsening reputation can paradoxically flatten your spam rate chart. Read the two charts together: a falling spam rate alongside falling volume and dropping reputation means filtering is increasing, not that users suddenly like your mail.
Reading Microsoft SNDS
SNDS (Smart Network Data Services) requires you to prove control of the IPs you register, either through reverse DNS or an authorized email address on the range. Once verified, you get a daily table per IP: message volume seen by Outlook.com, the filter verdict color, complaint rate band, and spam trap hits.
The color bands summarize how Microsoft's filters classified your traffic that day. Green means less than 10% of your mail was flagged as spam by the filters. Yellow means between 10% and 90%. Red means more than 90% was flagged. Yellow is the band that deserves the most attention: it usually appears before complaint problems fully develop and gives you time to react.
Pair SNDS with JMRP, Microsoft's Junk Mail Reporting Program. SNDS shows you aggregates; JMRP forwards the actual complaint messages so your suppression pipeline can remove the complainers. Registering for one without the other leaves half the value on the table.
Where the data misleads
Both dashboards fail silently below their volume thresholds. Postmaster Tools simply shows no data points for low-volume days, and SNDS omits IPs that Microsoft saw fewer than roughly 100 messages from. Senders often misread these gaps as clean days. If you send in bursts, expect gaps and do not average across them.
Delay is the second trap. Postmaster data typically lags two to three days, which means the dashboard describes the campaign before the one you just sent. During an active deliverability incident, your own real-time signals, bounce codes, seed placements, and engagement rates move first. Use the dashboards to confirm a diagnosis, not to detect the problem.
Finally, neither tool covers the rest of the inbox landscape. Yahoo, Apple, and the business filtering stacks (Proofpoint, Mimecast, Barracuda) publish no comparable dashboards. A High reputation at Gmail says nothing about your standing elsewhere.
Frequently Asked Questions
Do I need Postmaster Tools if I use an ESP?
Why does SNDS show no data for my IPs?
Which dashboard should I check first during an incident?
Can I see Gmail spam trap hits anywhere?
Set up both dashboards before you need them. Reputation data with a three-day lag is useless if you only register after the incident starts, and historical baselines are what turn these charts from decoration into diagnosis.
Related articles
Deliverability Incident Response: A Playbook for the First 4 Hours
When email reputation collapses, the first 4 hours determine the recovery timeline. Triage, containment, communication the operational playbook teams actually need.
List Hygiene Beyond Bounces: Engagement-Based Suppression Strategies
Bounce-based list cleaning is decades behind modern deliverability. The 90/180/365-day engagement model, sunset policies, and re-engagement that actually works.
Blocklist Remediation Playbook: Spamhaus, SORBS, and UCEPROTECT
How to remove your IP or domain from Spamhaus, SORBS, UCEPROTECT, and other blocklists. Which lists matter, which to ignore, and the delisting process for each.