Google Postmaster Tools and Microsoft SNDS: how to read them

How to set up Google Postmaster Tools and Microsoft SNDS, what each dashboard shows today, what to do when a signal turns bad, and a weekly check routine.

Technical drawing of two instrument panels on stands with analog gauges and a strip-chart recorder drawing a line, both wired to a sending server.

Google Postmaster Tools shows how Gmail sees your sending domain: compliance with its sender rules, spam complaints, authentication and delivery errors. Microsoft SNDS shows how Outlook.com sees your sending IPs: volume, spam filter verdicts and complaints. Both are free and both update about once a day. This guide sets up each one, explains what the dashboards show as of November 2026, and ends with a routine you can run every week.

The two tools side by side

Google Postmaster ToolsMicrosoft SNDS
CoversMail to personal Gmail accounts (@gmail.com, @googlemail.com)Mail to Outlook.com consumer mailboxes
Organised byDomain (your DKIM or SPF domain)IP address
Who can sign upAnyone who can verify the domain in DNSThe owner of the IP range
UpdatesTypically within 24 hours, in UTCDaily, around midnight Pacific time
HistoryLast 7, 30, 60, 90 or 120 days90 days

The key difference is the unit. Postmaster Tools follows your domain wherever you send from. SNDS follows the IP, so on a shared IP it shows the traffic of every sender on it.

Set up Google Postmaster Tools

  1. Sign in at postmaster.google.com with a Google account.
  2. On Manage Domains, choose Add new domain and enter the domain you authenticate with: the DKIM d= domain or the SPF (Return-Path) domain. If you send from news.yourcompany.com and sign with that domain, add it.
  3. Open the domain’s menu, choose Verify domain, and copy the TXT or CNAME record it shows.
  4. Add the record at your DNS provider, then return and click Verify. Google says this is usually immediate but can take up to 10 minutes.
  5. Optional: under Manage users, give teammates access. They need a Google account, and Google does not notify them.
news.yourcompany.com.  3600  IN  TXT  "<verification value copied from Postmaster Tools>"

If the primary domain is verified, subdomains don’t need their own verification. Add them anyway if you want to see their data separately.

What Postmaster Tools shows today

Google’s help page lists these dashboards:

DashboardWhat it showsCheck it for
Compliance statusWhether your mail meets each Gmail sender requirementThe first thing to check every week
Spam rateShare of mail delivered to the inbox that recipients marked as spamStaying below 0.1%
Feedback loopSpam rate per campaign, using your Feedback-ID headerWhich campaign drives complaints
AuthenticationShare of mail passing SPF, DKIM and DMARCA drop after a DNS change
EncryptionShare of mail sent over TLSAnything below 100% from your own servers
Delivery errorsRejected and temporarily failed messages, with the reasonRate limits and blocks

Compliance status

This dashboard checks each requirement from Google’s sender guidelines and gives it one of three states: Compliant, Needs work or No data found.

All senders are checked on SPF and DKIM, DNS records, message formatting, encryption and user-reported spam rate. Bulk senders, those sending about 5,000 or more messages a day to Gmail accounts, are also checked on DMARC, one-click unsubscribe and honouring unsubscribes. Google expects an unsubscribe to be processed within 48 hours.

Two details catch people out:

  • The dashboard reports for the primary domain only. If you add email.yourcompany.com, its data counts toward yourcompany.com.
  • It uses a rolling average. After you fix something, Google says it can take up to 7 days for Needs work to clear.

Under Compliance status there is also a Deliverability analysis tool. It gives a recommendation when, for example, you send too little mail, your messages fail to deliver, or recipients don’t interact with your email.

Spam rate

This is the rate of user reports, not of mail Gmail filtered on its own. It counts messages that reached the inbox and were then marked as spam, for DKIM-signed mail. Gmail’s sender guidelines ask you to stay below 0.1% and never reach 0.3%.

A very low spam rate is not always good news. If Gmail is already sending most of your mail to the spam folder, few recipients see it in the inbox, so few can report it. Google’s own troubleshooting notes describe this case. Read the spam rate next to delivery errors and engagement.

Feedback loop

Gmail’s feedback loop reports complaints per campaign, in aggregate. It does not tell you which addresses complained. It needs a Feedback-ID header on your messages:

Feedback-ID: a:b:c:SenderId

SenderId is a required ID of 5 to 15 characters that stays the same across your mail stream. a, b and c are optional IDs you choose, such as a campaign or a mail type. Reports appear only when an ID has enough volume and enough spam reports on a given day.

Reputation

Google’s help page still describes IP and domain reputation ratings: High, Medium, Low and Bad. If your account shows them, read them as a trend. Compliance status and Spam rate are the better place to start.

Set up Microsoft SNDS

SNDS has a new portal, announced by Microsoft in September 2026. It is free and needs a Microsoft account.

  1. Sign in and go to Request access.
  2. Enter an IP, an IP range or an Autonomous System Number (ASN) you own.
  3. SNDS finds authorization addresses from the reverse DNS and the registry (RDAP) records for those IPs, such as postmaster@ and abuse@ at the domain in the reverse DNS names. Pick one you can receive mail at.
  4. Click the link in the authorization email.

The same announcement says access no longer needs to be renewed periodically.

What SNDS shows

For each IP, per day:

FieldMeaning
Activity periodFirst and last hour of mail that day, Pacific time
RCPT commandsRecipients you tried to send to
DATA commandsMessages you transmitted
Message recipientsRecipients on messages actually sent
Filter resultGreen, yellow or red. See below
Complaint rateJunk reports divided by message recipients
CommentsExtra notes, such as junk mail reporting blocks

The filter result colours are defined by the share of spam verdicts on your mail:

ColourSpam verdicts
GreenUnder 10%
YellowBetween 10% and 90%
RedOver 90%

Microsoft notes that a message to ten recipients counts as ten verdicts, and that the colour is one data point, not a measure of inbox placement.

Two benchmarks from Microsoft’s FAQ are useful. More than a third of IPs keep the share of RCPT commands that don’t become recipients under 10%. A large gap points to an old list. More than 30% of IPs keep their complaint rate under 0.3%. Complaints are shown on the day they were reported, so a busy day can briefly look worse than it was.

The View IP Status page lists IPs with a problem: Blocked, Bot or Junked. Data may be missing for an IP that sent fewer than 100 messages that day. You can export each page as CSV or turn on an automated download URL.

To get the actual messages users marked as junk, enroll the IPs in Microsoft’s Junk Mail Reporting Program (JMRP) from the same site.

When a signal turns bad

SignalLikely causeWhat to do
Compliance: Needs work on authenticationA DNS change broke SPF or DKIMCheck the records, send a test, wait up to 7 days for the status
Compliance: Needs work on one-click unsubscribeSome promotional mail lacks the headersUse the feedback loop to find the campaign, add the headers
Gmail spam rate above 0.1%A segment or campaign is unwantedFind the source in the feedback loop, cut inactive subscribers, slow the frequency
Gmail spam rate near 0.3%The same, at a level Gmail treats as non-compliantStop sending to the cause now. Send only to recent engaged subscribers until it drops
Delivery errors: rate limitVolume rose too fastPause, then send slower. See IP warm-up
SNDS turns yellowSpam verdicts rising at Outlook.comCheck complaints and JMRP reports for the same days, remove the group that caused it
SNDS turns red, or IP status Junked or BlockedMost mail filtered or refusedStop sending from that IP to Microsoft, fix the cause, then contact Microsoft sender support
Large gap between RCPT commands and recipientsMany invalid addressesClean the list and check your bounce handling

Email bounce codes and what to do with each covers the codes behind the delivery errors, and Spam complaint rate: the limits and how to stay under them covers complaints in detail.

A weekly check routine

Fifteen minutes on the same day each week, plus a look after any large send:

  1. Postmaster Tools, Compliance status. Every item Compliant? Note any change since last week.
  2. Spam rate, last 30 days. Below 0.1%? Look for a rising line, not only the latest day.
  3. Feedback loop. Which ID has the highest rate? Is it the same one as last week?
  4. Authentication and encryption. Any drop below your usual level?
  5. Delivery errors. Any new rate limit or block reasons?
  6. SNDS, each IP. Colour for each day of the week, complaint rate, and the RCPT to recipients gap.
  7. SNDS IP status page. Empty is good.
  8. Write it down. One line per signal in a shared doc. A trend over 8 weeks tells you more than a single bad day.

Checklist

  1. Postmaster Tools set up for each sending domain, with the team added as users.
  2. A Feedback-ID header on your mail so the feedback loop can report per campaign.
  3. SNDS access for your IPs, or an agreement that your provider shares the data.
  4. JMRP enrollment for your IPs.
  5. A weekly routine and a place to record it.
  6. Agreed actions for each signal before it turns bad.

At EmailMarketer.io, complaints from provider feedback loops unsubscribe and suppress the address automatically, and each campaign report shows bounce and complaint rates with warnings, plus results by recipient domain (see reports). Senders from 500,000 emails a month have a named deliverability contact to read these signals with. The deliverability page has the details.

Get new posts by email

Guides on sending at volume, deliverability and pricing. One email when a post goes up. Unsubscribe any time.

By subscribing you agree to receive these emails. See the Privacy Policy.

Keep reading

Recommended posts