Email Sender Reputation: What Shapes It and How to Monitor It

What is sender reputation?

Sender reputation is a mailbox provider’s judgment, based on past behavior, of whether mail from your domain and sending IPs is wanted by its users. Gmail, Yahoo and Microsoft each build their own view from their own data, and each uses it, alongside authentication and per-message signals, to decide whether your next message goes to the inbox, the spam folder or nowhere at all.

There’s no single reputation score. You have a reputation at Gmail, another at Microsoft and another at Yahoo, and they can differ a lot. Third-party scores and blocklist checks can be useful signals, but they’re estimates from outside the providers’ systems, not the providers’ own view.

Domain reputation vs IP reputation

Providers track both. IP reputation attaches to the server addresses your mail comes from. Domain reputation attaches to the domains you authenticate with, mainly the DKIM signing domain and the From domain.

Domain reputation has become the more important of the two for most senders. Most businesses send through email platforms on shared IP pools, where the IP’s reputation reflects many senders at once, and the platform manages it. Your domain goes with you wherever you send from, which is why switching platforms rarely fixes a reputation problem.

Subdomains have their own reputation to a degree, but providers also consider the parent domain. Sending marketing from news.example.com keeps it somewhat separate from staff mail on example.com, but it won’t hide sustained bad practice.

Dedicated IPs put IP reputation in your hands. That’s helpful if you send enough mail, consistently enough, for providers to form a clear view. At lower or irregular volume, a dedicated IP often performs worse than a well-run shared pool, because there isn’t enough history to judge.

What builds and damages reputation

Providers don’t publish how they weight signals, and they change them. What they do say publicly, and what holds up in practice, comes down to a few groups.

Signals you control directly:

• Authentication. Consistent SPF, DKIM and DMARC alignment lets a provider tie your mail’s history to your domain. See our DMARC guide.
• Who you mail. Bounces to unknown users and spam-trap hits suggest poor list practice. Our list hygiene guide covers this.
• How you send. Sudden volume spikes, irregular bursts and new domains sending at full volume all look like spam. See domain warm-up.

Signals your recipients control:

• Spam complaints. The strongest negative signal.
• Engagement. Providers observe how users treat your mail: opening and reading it, replying, moving it out of spam, deleting it unread or ignoring it. They don’t publish the details, but sending mainly to people who engage is the most reliable way to keep this positive.

Here’s how these combine. A subscription brand sends a promotion to its full list, including a large segment that hasn’t engaged in over a year. A small fraction of those people mark it as spam, which barely registers on the platform’s dashboard but is enough to push Gmail’s measured rate up for that day. The next few sends land in spam more often, engagement drops further because fewer people see them, and the problem reinforces itself. The fix starts with narrowing the audience, not rewriting the subject lines.

How are spam complaint rates measured?

Gmail measures spam rate as the share of DKIM-authenticated mail delivered to the inbox that users then mark as spam. Gmail requires all senders to stay below 0.3% and recommends staying below 0.1%. Yahoo also uses 0.3% as its limit, and likewise calculates the rate from mail delivered to the inbox.

Two consequences follow, and both mislead people:

• Your platform’s complaint rate isn’t Gmail’s. Email platforms count complaints from feedback loops that send them individual reports. Gmail doesn’t send per-message complaint reports to senders in that way, so Gmail users’ complaints are largely missing from platform dashboards. A platform figure that looks fine can sit alongside a Gmail spam rate that’s too high. Check Postmaster Tools directly.
• A low rate can be bad news. Because only inbox-delivered mail counts, if Gmail is already filtering much of your mail to spam, fewer people can complain, and the rate can look artificially healthy. Google’s own documentation points this out. Read it alongside delivery and engagement data.

Microsoft doesn’t publish an equivalent percentage threshold for Outlook.com. Its complaint data reaches senders through SNDS and the Junk Mail Reporting Program, covered below.

Google Postmaster Tools

Google Postmaster Tools is Google’s free dashboard showing how Gmail sees mail from domains you’ve verified. You add a domain, prove ownership with a DNS TXT record, and data appears once you send enough daily volume to personal Gmail accounts. Low-volume days may show nothing.

The tool changed substantially in 2025 and 2026. The original version was retired on 30 September 2025, and the domain reputation and IP reputation dashboards that older guides describe have been retired too, so you’ll no longer see the bad/low/medium/high labels. If you’re following an older playbook built around those charts, it needs updating.

The current version is built around:

• Compliance status, showing whether your mail meets Gmail’s sender requirements. All senders are checked on SPF and DKIM, DNS records, message formatting, encryption and spam rate. Bulk senders are also checked on DMARC, one-click unsubscribe and handling unsubscribes within 48 hours. Each requirement shows as compliant, needing work, or without enough data. Updates can take several days to appear.
• Spam rate, the user-reported rate described above.
• Feedback loop, which reports spam rates grouped by identifiers you place in a Feedback-ID header. Useful for seeing which campaign type or customer segment is driving complaints. It’s designed for bulk senders and only shows identifiers that reach a minimum level of reports.
• Authentication, Encryption and Delivery errors. Delivery errors are worth checking regularly: they show the share of mail Gmail rejected or deferred and the reasons, which can still point to reputation or rate-limiting problems.
• A deliverability analysis tool within the compliance view to help diagnose issues.

Google adjusts this tool fairly often, so check the current help documentation if a dashboard name doesn’t match what you see.

Yahoo Sender Hub

Yahoo’s Sender Hub publishes its sender requirements and best practices and is where you enroll in the Complaint Feedback Loop (CFL). The CFL sends you reports when Yahoo users mark your mail as spam, keyed on your DKIM signing domain, so you need DKIM signing with your own domain to use it. If you sign with your own domain, ask your email platform whether it registers that domain for the CFL or whether you need to do it yourself.

Microsoft SNDS and JMRP

Microsoft’s Smart Network Data Services (SNDS) shows data on mail from IP addresses you control to Outlook.com, Hotmail, Live and MSN consumer mailboxes. It’s IP-based only. You can register only addresses you’re responsible for, which in practice means SNDS is useful if you send from dedicated IPs and of little use on a platform’s shared pool.

For each registered IP it shows volume, a filter result rating (green, yellow or red) and the complaint rate. It doesn’t measure inbox placement or check authentication.

SNDS changed in 2026:

• It moved to a new portal in June 2026. Bookmarks to the old address redirect, but scripts using old automated download links stopped working shortly after.
• IP status and IP data reports are now available through a REST API, and Microsoft changed some calculations and columns at the same time, so compare trends across the switchover carefully.
• Spam-trap hit counts were removed from the data report in July 2026.
• Access to IP ranges now has to be re-confirmed periodically.

The Junk Mail Reporting Program (JMRP) is Microsoft’s complaint feedback loop. Reports now include selected headers rather than the full original message, so match complaints to recipients using the Message-ID or a token in your headers, not the visible address.

Microsoft’s guidance for high-volume senders also asks you to actively manage the reputation of your outbound IPs, which is what these two tools are for.

Blocklists

Public blocklists, such as those run by Spamhaus, list IPs and domains associated with spam. Some receivers consult them, and a listing on a major one can cause widespread rejections, usually with a bounce message naming the list. Check them when bounces spike or rejections mention a listing.

Keep them in proportion, though. Gmail’s filtering relies mainly on its own data, so a clean blocklist check doesn’t mean Gmail trusts you, and many small, obscure lists have little effect on delivery.

Reading the symptoms

• Problem at one provider only: a reputation issue specific to that provider. Compare engagement and complaint data for its recipients.
• Sudden rejections everywhere: authentication breakage or a major blocklist listing. Check DNS and DMARC reports first.
• Slow decline over months: usually list decay and growing inactive segments.
• Decline after a specific send: a new list source, a large audience expansion or a frequency change.
• Deferrals with rate-limit messages: you’re sending faster than your reputation supports. Slow down rather than retrying harder.

Recovery comes from changing the inputs, then giving providers time to observe the change. Our deliverability improvement service covers how that’s structured.