Google Postmaster Tools and Microsoft SNDS: the dashboards providers actually give you

Mailbox providers score every message you send and tell you the result almost never. There is no hotline, no monthly statement, no notification when your domain slides from trusted to suspect. Exactly two providers hand senders a first-party window into their own scoring: Google, through Postmaster Tools, and Microsoft, through SNDS. Both are free. Everything else you will ever be shown about your reputation is somebody's inference. This lesson tours the real dashboards, and, just as important, marks the access limits: what each one cannot show, and who is locked out entirely.

Why the silence

Reputation is opaque by design: a published scoring formula would be a spammer's instruction manual. So providers reveal nothing, except where their interest flips. They would rather a legitimate sender notice a complaint spike and fix it than keep filtering the fallout, so they expose a narrow, deliberately chosen slice of the ledger. That is what these dashboards are. Not transparency, a pressure valve.

Google Postmaster Tools

The single most useful piece of reputation evidence available to any sender. You verify ownership of your sending domain with a DNS record and Google shows you charts of how Gmail sees that domain. (Google rebuilt the tool recently; the current interface replaces the original one, which is being retired, so ignore older screenshots you find elsewhere.) The dashboards, by their current names: Compliance status, Spam rate, IP reputation, Domain reputation, Feedback loop, Authentication, Encryption, and Delivery errors.

Four of them do most of the work. Spam rate is the chart with legal force, so to speak: Google defines it as the percent of your messages delivered to engaged recipients' inboxes that those recipients then mark as spam, and the sender guidelines from the previous lesson are written against this exact chart. Keep it below 0.1%; never reach 0.3%. No tool outside this dashboard can see the number Gmail holds you to.

Domain reputation and IP reputation grade you in four bands rather than numbers: Bad, Low, Medium, High. Google's own gloss on High is a history of very low spam rates and compliance with its sender guidelines; Bad means a history of sending high volumes of spam regularly. The bands are coarse on purpose. What they are good for is direction: a domain drifting from High to Medium is a warning you get from nowhere else on earth.

Authentication shows the percent of your traffic passing SPF, DKIM, and DMARC, which makes an unsigned mail stream visible as a sagging line. Delivery errors shows the percent of your authenticated mail Gmail rejected or deferred, with reasons.

The limits, honestly. It covers Gmail traffic only. It shows bands and rates, never per-message or per-campaign detail. And Google withholds data on days your volume is too low, to protect user privacy, so small senders often stare at empty charts. That last one is not a setup mistake, and no amount of re-verifying fixes it.

Microsoft SNDS and JMRP

Smart Network Data Services is Microsoft's equivalent, with one structural difference that decides who can use it: SNDS is organized by IP address, not by domain. You sign in with a Microsoft account and request access to the IPs you are responsible for, and an authorization process checks that you actually control them. For the IPs you get approved on, SNDS reports how your traffic to Microsoft mailboxes was treated, per IP, per day.

Read that access rule again, because it locks out most of the people reading this. If you send through Mailchimp, Klaviyo, Brevo, or any ESP's shared infrastructure, the sending IPs belong to the ESP. You cannot register them, and SNDS has nothing to show you. The ESP's deliverability team watches those ranges; that is their job, not yours. SNDS earns its keep for senders on dedicated IPs or their own servers, and sits closed to everyone else. Trying to get authorized on your ESP's IPs just burns an afternoon; the afternoon is the only thing that gets burned.

JMRP, the Junk Email Reporting Program, rides along with SNDS: it sends you a report when a Microsoft user junks one of your messages, so you can suppress that recipient. It is Microsoft's version of the feedback loops from two lessons back, and it shares SNDS's IP-based access model.

One more thing worth noticing: these dashboards change under you. As I write this, the SNDS site announces that spam-trap hit counts leave its data report in late July 2026. A view you built a routine around can shrink without asking you.

Yahoo, briefly

Yahoo has no reputation dashboard. What it offers instead is a complaint feedback loop through its Sender Hub: you create a profile, verify your domain, and enroll it, and complaints then arrive as individual emailed reports in a standard format called ARF. Enrollment is tied to your DKIM domain, since the DKIM signature is how Yahoo identifies who actually sent the message. Feedback by mail, not a graph. That is the honest, complete state of first-party visibility at Yahoo.

The only first-party evidence there is

Here is the frame to carry out of this lesson. These dashboards are the only places where a mailbox provider tells you, itself, what it thinks of your mail. Every third-party "sender score" or reputation lookup is built from that vendor's own traps, panels, and traffic samples: inference about the providers' opinion, not the opinion. Inference can still be useful. But when Postmaster Tools says your domain reputation is Bad, that is Gmail speaking about Gmail, and it outweighs any external score that says you are fine. Weight your evidence by who is speaking.

And none of these dashboards, first-party or not, shows you the thing senders most want: which folder your mail landed in. That gap is the next lesson.

The decay note

The failure mode with postmaster dashboards is not setup. It is the second month. The classic pattern: a crisis hits, someone sets up Postmaster Tools, watches it daily for two weeks, the crisis passes, and nobody logs in again. Which is decay in its purest form: the spam-rate line crossed 0.1% in March, the graph recorded it faithfully, and no human ever looked. A dashboard is not monitoring. It is a place where monitoring could happen, if someone shows up.

Next lesson: measuring deliverability, what you can and cannot actually know about where your mail lands.

Terms from this lesson

• Google Postmaster Tools - Google's free dashboard for verified sending domains, showing spam rate, reputation bands, authentication rates, and delivery errors for Gmail traffic.
• reputation bands - Postmaster Tools' four-step grading of a domain or IP: Bad, Low, Medium, High. Direction matters more than the label.
• SNDS - Microsoft's Smart Network Data Services, reporting how traffic from IPs you control was treated. IP-based, so closed to senders on shared ESP infrastructure.
• JMRP - Microsoft's Junk Email Reporting Program, delivering a report when a Microsoft user marks your message as junk.
• complaint feedback loop - a provider service that returns individual complaints to the sender; Yahoo's version enrolls DKIM domains and delivers reports by email in ARF format.

Check yourself

1. Postmaster Tools shows your domain reputation as Low. What is Google actually telling you?

Your exact spam-percentage score, to two decimal placesThat the domain has, in Google's words, a history of sending a significant volume of spam regularly, on its four-band scaleThat your SPF record has stopped passingThat Gmail has begun rejecting all your mail

2. Where does the spam-rate number that Gmail's sender requirements are written against actually live?

In your ESP's campaign reportsIn any public reputation-lookup toolIn Postmaster Tools, visible only to someone who has verified the domainIn your DMARC aggregate reports

3. What does Yahoo offer senders in place of a reputation dashboard?

A Postmaster Tools clone with reputation chartsRead access through Microsoft's SNDSNothing at all, at any levelA complaint feedback loop: enroll your DKIM domain and complaints arrive as emailed ARF reports

Scenario

Your client sends through Mailchimp on shared IPs. Their Outlook placement looks shaky, and a consultant has advised them: "register your sending IPs in SNDS so you can watch your Microsoft reputation directly."

What do you tell them?

Good idea. Look up Mailchimp's sending IPs and request access to them in SNDS.SNDS is closed to them on shared IPs; Mailchimp's team watches those ranges. Point the client at domain-level evidence instead: Postmaster Tools for the Gmail side, DMARC reports, and their complaint handling.Move them to a dedicated IP so they qualify for SNDS access.

The lab

Set up Google Postmaster Tools for your own domain, today, whatever your volume. Go to postmaster.google.com and sign in with any Google account. Click Add and enter the domain you authenticate with, meaning the domain in your DKIM signature or SPF record; for most senders that is the root sending domain. Google will hand you a TXT record. Add it at your DNS host, the same place you did your SPF work, then return and click Verify. Verification is usually instant, and Google says to allow up to ten minutes. (If you don't own a domain yet, park this lab until you do; first-party evidence has no read-only version.)

Then, the honest part about what happens next. The charts populate going forward, and Google withholds data on days when your volume is too low. If you send dozens of emails a day rather than thousands, expect to see "no data" on most or all dashboards for weeks, possibly indefinitely. That is normal, not broken, and re-verifying will not change it. The account still earns its place: it costs nothing, it is the compliance instrument Gmail's own requirements are written against, and it is already collecting on the day your volume grows. Finish the lab by putting a recurring fifteen-minute reminder in your calendar to open it. The setup was the easy half; the showing up is the actual instrument.