Microsoft SNDS & Outlook Sender Reputation Monitoring

If you send cold email to Outlook.com, Hotmail, or Live.com addresses, you're partly flying blind without Microsoft SNDS. Google gives every sender a free, domain-level reputation dashboard. Microsoft's equivalent, Smart Network Data Services, does a similar job for the Outlook side of the inbox, but it works on a different axis. It watches IP addresses, not domains. That single difference decides who can actually use it and what the data means.

This guide walks the full Microsoft SNDS setup: requesting data access for the sending IPs you control, reading the green/yellow/red filter result, and interpreting complaint rate and spam-trap data. It also covers JMRP, the junk mail reporting program that emails you every time an Outlook.com user clicks "report junk," and why Microsoft scores sender reputation differently from Gmail. For the Gmail half of the picture, our Google Postmaster Tools setup guide is the companion piece. This is the Microsoft side.

Key Takeaways

• SNDS is free and IP-based. It reports reputation for the sending IP addresses you authorize and covers consumer Outlook.com, Hotmail, Live, and MSN mail, not Microsoft 365 business tenants.
• You can only use SNDS for IPs you control. If you send through Google Workspace or a shared provider pool, the IP isn't yours and the data won't be available to you.
• The filter result color is one filtering layer's verdict. Green is under 10% of mail filtered as spam, yellow is 10% to 90%, and red is over 90% filtered.
• JMRP is a separate complaint feedback loop. It forwards a copy of every message an Outlook.com user marks as junk, so you can suppress those addresses fast.
• Microsoft now enforces SPF, DKIM, and DMARC for any domain sending 5,000 or more messages a day to Outlook.com.

What SNDS actually shows you (and what it doesn't)

Before you spend twenty minutes on the signup, it's worth knowing exactly what Smart Network Data Services measures, because the scope trips up most cold senders.

SNDS reports on the sending IP address, not the domain. Microsoft built Smart Network Data Services so the owner of an IP range can monitor how mail from those addresses is treated by Outlook's consumer filters. That covers the big consumer mailboxes: outlook.com, hotmail.com, live.com, and msn.com. It does not cover Microsoft 365 business tenants, which are filtered separately by Exchange Online Protection and don't surface in SNDS at all.

The IP focus has a hard consequence for cold email. If you send through Google Workspace, Microsoft 365, or any managed sending pool, you don't own the IP that delivers your mail, so you can't authorize it in SNDS and you won't see its data. SNDS becomes genuinely useful the moment you run your own sending infrastructure: a self-hosted SMTP relay, a dedicated IP, or a server you control. If that's not your setup yet, our guide to cold email infrastructure covers when owning the IP is worth it. For everyone sending from shared provider mailboxes, domain-level tools and seed tests do more of the heavy lifting.

Two more limits worth setting expectations on. First, SNDS needs volume to show anything: an IP usually has to send around 100 messages to Microsoft recipients on a given day before data appears. Low-volume senders see sparse or empty grids. Second, the filter result is the verdict from one layer of Microsoft's filtering stack, not a delivery guarantee. A red IP can still land some mail in the inbox, and a green IP can still have messages routed to junk. Read it as a strong directional signal, not a placement score.

Microsoft SNDS setup: requesting data access

The signup is free, but it's gated behind an ownership check, since Microsoft only wants to hand IP reputation data to the people actually responsible for that traffic. Here's the SNDS data access signup, start to finish.

1. Go to the SNDS portal and sign in. Open the Smart Network Data Services site and log in with any Microsoft account. A personal Outlook.com address works fine; it doesn't need to match your sending domain.
2. Request access to your IPs. Use the "Request Access" option and enter the individual IP addresses or CIDR ranges you send from. You can list a single IP or a whole block if you control the range.
3. Pass the authorization check. Microsoft confirms you actually control the space before releasing data. It sends an automated authorization request to the contact on file for the IP range, typically the WHOIS abuse or postmaster address for that block. Whoever receives it approves the request through the link inside.
4. Wait for data to populate. Once approved, data starts flowing within a day or two, and the grid backfills as your IPs send enough volume to clear the reporting minimum.

The authorization step is where cold senders get stuck. If you rent a dedicated IP from a sending provider, the WHOIS contact is usually the provider, not you, so you'll need them to forward or approve the authorization email. Plan for that handoff rather than assuming the request will land in your own inbox.

One practical note: SNDS access doesn't expire on a fixed clock, but Microsoft can require periodic re-authorization, and access tied to a range you no longer control will lapse. If your data suddenly goes blank, re-check the authorization before assuming a reputation problem.

Reading the SNDS dashboard: colors, complaint rate, and trap hits

Once data populates, SNDS gives you a per-IP, per-day grid. It's dense and unglamorous, but every column maps to a real deliverability question. Here's what each one tells you.

The filter result colors. This is the field most people open SNDS for. The color reflects how much of your mail Microsoft's filters pushed to junk: green means under 10% of your mail from that IP was filtered as spam, yellow means somewhere between 10% and 90%, and red means more than 90% got filtered. Yellow is the one to treat as an alarm, not a shrug. It means Microsoft is already applying extra scrutiny, and unaddressed yellow tends to slide into red over the next few sending days. Green is the baseline you want to hold, not a finish line.

Complaint rate. This column is complaints divided by delivered messages, and it's the leading indicator of a burn. The widely used safe ceiling is well under 0.3%, and many deliverability teams treat trouble as starting around 0.1%, roughly one junk click per thousand delivered. For cold email, that's an unforgiving bar: one complaint per thousand sends is easy to cross with a cold list, which is exactly why list quality and warmup discipline matter more than clever copy.

Trap hits. If the trap column ever shows a hit, stop and investigate the list, don't wait. A spam-trap hit means an address that should never have been mailed received your message, and that's a fast track to a blocklisting. The trap mechanics, pristine versus recycled versus typo traps, are worth understanding in full; our guide on email spam traps breaks them down. If a trap hit coincides with a reputation drop, run a blacklist check on the IP and domain immediately.

JMRP: the junk mail reporting program feedback loop

SNDS tells you that complaints happened. The JMRP junk mail reporting program tells you who complained, message by message, so you can act on it.

JMRP is Microsoft's complaint feedback loop for Outlook.com. When a recipient on a Microsoft consumer mailbox clicks "report junk," JMRP forwards a copy of that message to a reporting address you designate. It's the Outlook equivalent of the feedback loops other mailbox providers run, and like SNDS, it's free and keyed to the sending IP.

Signing up follows the same gate as SNDS. You request a JMRP feed from the same Microsoft sender support portal, using a dedicated sending IP, because the whole point is to route an IP's complaints back to the IP's owner. The signup form asks for the basics: company name, a contact address, the complaint feedback address where you want reports delivered, the format, and a couple of rate caps for how many complaints to forward per IP per day and across all IPs. Once it's live, complaints typically begin arriving within a day or two.

What you do with the feed matters more than the setup. Every JMRP report is a person telling Microsoft they didn't want your email. Treat each one as an immediate, permanent suppression: pull that address out of every active sequence and never mail it again. Senders who ignore the feed, or who only glance at it, miss the single clearest Outlook.com sender reputation signal Microsoft hands them for free. The teams that actually wire JMRP into their suppression list keep complaint rates down precisely because they remove unhappy recipients before the complaints compound.

How Outlook scores reputation differently from Gmail

If you've only ever monitored Gmail, SNDS feels backwards at first. That's because Microsoft and Google weight reputation on different primary keys, and understanding the split changes how you read both tools.

Gmail's free monitoring, Postmaster Tools, is organized around your domain. Its reputation panels, spam rate, and authentication views are all domain-keyed, which is why Google's bulk-sender guidance and its 0.10% spam-rate target are framed at the domain level. Microsoft's free monitoring, SNDS, is organized around your IP. The whole grid is per-IP, and the reputation verdict attaches to the address that connected, not the domain in your From line. In practice, Outlook has historically leaned harder on IP reputation, while Gmail leans harder on domain reputation and recipient engagement. Neither ignores the other signal, but the tooling tells you which one each provider puts first.

That difference has a real consequence for how you isolate problems. On a shared IP pool, your Outlook reputation is partly hostage to your neighbors, which is one argument for a dedicated IP at higher volumes. On Gmail, a clean domain with strong engagement can outrun a so-so IP. So a domain that places well in Gmail can still struggle at Outlook if the IP is the weak link, and SNDS is the only free tool that will show you that.

Authentication is the one place the two providers have converged. As of May 5, 2025, Microsoft enforces SPF, DKIM, and DMARC for any domain sending 5,000 or more messages a day to Outlook.com, Hotmail.com, and Live.com, with DMARC set to at least p=none and aligned to SPF or DKIM. Non-compliant mail isn't just junked; it's rejected outright with a 550 5.7.515 Access denied error stating the sending domain doesn't meet the required authentication level. That mirrors the bulk-sender rules Google rolled out in February 2024, and it means your authentication has to be correct before SNDS data is even worth reading. If any of SPF, DKIM, or DMARC is shaky, fix it first with our SPF, DKIM, and DMARC guide, then monitor.

Where SNDS fits in your monitoring routine

SNDS isn't a set-and-forget signup. It earns its keep as one feed in a small monitoring loop you check on a cadence, not a panic button you open after replies go quiet.

A workable rhythm for a self-hosted or dedicated-IP sender looks like this:

• Weekly: scan the SNDS grid for any IP that slipped from green to yellow, plus any complaint-rate creep or trap hits. Yellow is your early-warning line; catch it before it turns red.
• As it arrives: process every JMRP complaint into your suppression list the day you get it. This is the highest-leverage habit on the list.
• Monthly, or after any reputation dip: run a seed-list inbox placement test across Outlook and Gmail to confirm where mail is actually landing, since SNDS colors and real placement aren't the same thing.

SNDS and JMRP cover the Microsoft side. Pair them with Google Postmaster for Gmail and you've got both major consumer ecosystems instrumented. The full picture, what to watch, how often, and how the signals fit together, lives in our domain health monitoring guide, which is the pillar this Microsoft deep-dive hangs off. And if SNDS ever shows a red IP alongside a trap hit, assume a possible blocklisting and move straight to a delisting process rather than waiting for the color to recover on its own.

Common questions about Microsoft SNDS and JMRP

Do I need a dedicated IP to use SNDS?

Effectively, yes, for cold email. SNDS data is keyed to the IP and gated behind an ownership authorization, so you can only see data for IP space you control or can get authorized. If you send through Google Workspace, Microsoft 365, or a shared provider pool, the IP isn't yours and you won't have SNDS access. A self-hosted SMTP setup or a dedicated IP is what makes SNDS usable.

Is Microsoft SNDS free?

Yes. Both SNDS and JMRP are free Microsoft programs. The only cost is the time to complete the data access signup and the IP authorization step, plus the discipline to actually read the data and process JMRP complaints.

Does SNDS work for Microsoft 365 business mailboxes?

No. SNDS reports on consumer Outlook mail: outlook.com, hotmail.com, live.com, and msn.com. Microsoft 365 business tenants are filtered by Exchange Online Protection and don't appear in SNDS. SNDS tells you how your IP is treated by Microsoft's consumer filters, which is the relevant signal for most cold outreach to personal Outlook addresses.

How often is SNDS data updated?

SNDS reports daily, one row per IP per day, usually with a day or two of lag before a given day's data appears. Because of that lag and the volume minimum, judge reputation on the trend across several days rather than reacting to a single row.

What complaint rate is safe in SNDS?

Keep it well under 0.3%, and treat anything approaching 0.1% (about one junk report per thousand delivered) as a warning. For cold email that's a tight bar, which is why list verification and warmup matter more than copy tweaks. If your SNDS complaint rate is climbing, the fix is almost always a cleaner list, not a cleverer subject line.

The bottom line

Microsoft SNDS setup is one of the few free reputation feeds a cold sender can get for the Outlook side of the inbox, but it only works if you own the IP you send from. Authorize your IPs, learn to read the green/yellow/red filter result and the complaint-rate column, and wire JMRP into your suppression list so every junk complaint gets removed the day it lands.

Then remember what the tool is and isn't. SNDS is one filtering layer's verdict on one IP, not a placement guarantee, and Outlook scores reputation on the IP while Gmail scores it on the domain. Watch both, keep your authentication compliant, and treat yellow as the moment to act. MailBeast's deliverability monitoring and warmup are built to keep those signals green so the SNDS grid stays boring, which is exactly what you want it to be.

Sources

• Microsoft, Smart Network Data Services
• Microsoft, Strengthening the Email Ecosystem: Outlook's New Requirements for High-Volume Senders
• Google, Email sender guidelines
• Iterable, Monitoring Deliverability with Microsoft's Smart Network Data Services (SNDS)
• Validity, What Is SNDS and How Do I Even?
• Spam Resource, DELIVTERMS: JMRP