Sender reputation is the score mailbox providers assign to the IP address and domain you send email from, and it is the single biggest factor in whether your messages land in the inbox or get filtered. In 2026, it is not optional infrastructure. Gmail, Outlook, and Yahoo make filtering decisions in milliseconds based on dozens of reputation signals, and a damaged reputation can take weeks to repair. This guide covers how reputation actually works, how to monitor it, and how to protect it as you scale.
Short answer: Sender reputation is a trust score that mailbox providers calculate for both your sending IP address and your sending domain, based on engagement rates, complaint rates, bounce rates, authentication, and historical behavior. You build it by warming up gradually, sending only to engaged recipients, and keeping complaint rates below 0.1%. You protect it by rotating sending identities, monitoring providers like Google Postmaster Tools daily, and never spiking volume on a cold inbox.
What Is Sender Reputation?
Sender reputation is a composite score that mailbox providers (Gmail, Microsoft, Yahoo, Apple iCloud, and ISPs like Comcast or AOL) maintain internally about every entity that sends email through their systems. It is not a single number you can look up in one place. Each provider keeps its own scoring model, weighted by signals they consider most predictive of spam.
When an email hits a mailbox provider's incoming server, the system pulls up the historical reputation of the sending IP, the sending domain, and any related identifiers, then makes a filtering decision in milliseconds. Good reputation means the inbox. Mediocre reputation means the promotions or junk tab. Poor reputation means silent rejection or hard bounce.
Sender reputation is sticky. A clean record over six months is worth far more than any tactical optimization. A damaged record over two weeks of bad sending can take a month or longer to recover from. This asymmetry is why deliverability work is mostly about prevention, not repair.
Sender reputation is the trust score mailbox providers assign to a sending IP address and sending domain, based on past sending behavior. It determines whether incoming messages are delivered to the inbox, filtered to spam, or rejected outright. Reputation is calculated per provider (Gmail, Microsoft, Yahoo each maintain their own), influenced by authentication, engagement rates, complaint rates, bounce rates, and sending consistency over time.
IP Reputation vs Domain Reputation
Sender reputation has two layers. Understanding the difference is critical because they behave differently and require different protection strategies.
IP reputation is tied to the physical server (or shared IP pool) sending the email. If you send through Google Workspace, you share IPs with millions of other senders. If you send through a dedicated SMTP service like Amazon SES on a dedicated IP, you own that reputation outright. Shared IPs benefit from the pool's collective good behavior but are vulnerable to neighbor abuse. Dedicated IPs give you full control and full responsibility.
Domain reputation is tied to the domain in your From address and your authenticated identifiers (the d= value in DKIM, the return-path domain in SPF). This reputation follows you regardless of which IP you send from. In 2026, domain reputation matters more than IP reputation for most senders. Gmail and Yahoo have been clear about this since their February 2024 bulk sender requirements: they evaluate domains first, IPs second.
This matters because if you switch from Google Workspace to a different sending platform but keep the same domain, your reputation travels with you. If you change domains but keep the same IP, you start fresh from a reputation standpoint at most providers.
| Dimension | IP Reputation | Domain Reputation |
|---|---|---|
| Tied to | Sending server IP address | From-address domain, DKIM d=, SPF return-path |
| Shared or dedicated | Often shared (Google, Microsoft pools) | Always yours (you own the domain) |
| Portability | Stays with the IP | Follows you across sending platforms |
| Recovery time | Days to weeks | Weeks to months |
| Primary weight in 2026 | Secondary | Primary at Gmail, Yahoo, Microsoft |
| Where to monitor | SenderScore, Talos, Spamhaus | Google Postmaster Tools, Microsoft SNDS |
How Mailbox Providers Score Senders
Each major mailbox provider runs its own scoring model, but the inputs are broadly similar. These are the signals that move the needle most in 2026.
Engagement positive signals. Opens, replies, conversation threads, recipients moving your email out of spam, recipients adding you to contacts, and recipients clicking links and staying on the destination page. Replies are weighted heaviest because they are the hardest signal to fake.
Engagement negative signals. Marking as spam, deleting without opening, never opening across multiple sends, and rapid unsubscribes. A single spam complaint per 1,000 emails (0.1%) is the threshold Gmail flags as problematic in Postmaster Tools. Anything above 0.3% triggers active filtering.
List quality signals. Hard bounces (invalid addresses), soft bounces (full mailboxes, temporary failures), and hits against spam traps. Spam traps are addresses that exist solely to identify senders who scrape lists or fail to clean their data. One pristine spam trap hit can blacklist your domain at major filters.
Authentication signals. SPF pass, DKIM pass with proper alignment, and DMARC policy enforcement. Since 2024, missing any of these is a near-instant flag at Gmail and Yahoo for senders above 5,000 messages per day.
Behavioral signals. Sending volume consistency (sudden spikes look like compromised accounts), time-of-day patterns, content variation (identical messages to thousands of recipients look automated), and ratio of cold contacts to warm contacts.
Reputation thresholds that matter: Gmail flags spam complaint rates above 0.1% in Postmaster Tools and triggers active filtering above 0.3%. Hard bounce rates above 2% indicate a dirty list or list scraping. SenderScore values below 70 (on a 0-100 scale) correlate with significant deliverability issues. These are widely referenced industry thresholds; your own benchmarks should sit comfortably below them, not at them.
Tools to Monitor Sender Reputation
You cannot manage what you cannot measure. These are the tools that actually give you visibility into how mailbox providers see you.
Google Postmaster Tools. Free, run by Google, and the single most important reputation dashboard if you send to any meaningful volume of Gmail addresses. It shows domain reputation (Bad, Low, Medium, High), IP reputation, spam complaint rate, authentication pass rates, and delivery errors. You need at least a few hundred Gmail recipients per day for data to populate. Check it daily.
Microsoft SNDS (Smart Network Data Services). The equivalent for Outlook, Hotmail, and Live addresses. Shows complaint rates, spam trap hits, and a color-coded filter status for each IP you send from. Microsoft also runs a separate tool called JMRP (Junk Mail Reporting Program) that forwards complaints to you.
SenderScore. Run by Validity, gives your IP a score from 0 to 100 based on aggregated data from major ISPs. Useful as a single-number health check, less useful for diagnosing specific problems. Free to look up your own IP.
Cisco Talos Intelligence. Tracks IP and domain reputation across the broader email ecosystem, including reputation categories used by enterprise spam filters. Look up your sending IP and domain to see if anything is flagged as Poor or Neutral.
Spamhaus, Barracuda, SORBS, and SURBL. The major DNS-based blocklists. Tools like MXToolbox check all of them in one query. Getting listed on any major blocklist is a deliverability emergency and requires direct delisting requests.
Seed-list testing (GlockApps, MailReach, Mailgenius). These services send test emails to seed accounts at every major provider so you can see exactly where your message landed: inbox, promotions, or spam, at Gmail, Outlook, Yahoo, and AOL. Run a seed test before launching any new campaign and weekly thereafter.
How to Build Reputation from Zero
A new domain and a new inbox have no reputation. This is not the same as a good reputation. Mailbox providers treat unknown senders with skepticism by default, and any aggressive sending pattern in the first 30 days will tank you before you start.
The build phase looks like this:
- Weeks 1-2: Authenticate everything. SPF, DKIM with 2048-bit keys, and DMARC starting at p=none. Run an automated warm-up service that sends 5-15 emails per day to a pool of real mailboxes that open and reply. Send zero real outreach.
- Weeks 3-4: Continue automated warm-up. Begin real outreach at 20-30 emails per day per inbox, targeting only highly relevant prospects to maximize engagement. Replies and opens at this stage build the foundation of your reputation.
- Weeks 5-6: Increase real outreach to 40-50 emails per day per inbox. Keep warm-up running in parallel. Monitor Postmaster Tools daily as data starts populating.
- Week 7 and beyond: Cap at 50-80 emails per day per inbox for sustained cold outreach. Going higher per inbox is technically possible but reduces the engagement-to-volume ratio, which is the metric that actually matters.
How to Protect Reputation at Scale
Once you have built reputation, the goal shifts from earning trust to not losing it. The most common ways agencies and sales teams destroy good reputation:
- Volume spikes. Going from 200 emails per day to 800 overnight looks like an account compromise. Increase by no more than 20-30% in any single day.
- Dirty lists. Bounce rates above 2% kill reputation fast. Run every list through an email verification service before import and expect to remove 10-20% of any list as invalid.
- Spam traps. Never buy lists. Never scrape lists. Use providers that actively scrub their data against known trap networks.
- Ignored unsubscribes. Failing to honor opt-outs converts unsubscribes into spam complaints, which damage reputation 10-50x more than an unsubscribe would have.
- Single-inbox concentration. Running your entire outreach operation from one or two inboxes concentrates all reputation risk in those identities. A single bad week can destroy months of trust.
Sender Rotation: Distributing Reputation Risk
The structural answer to reputation risk is to never depend on a single sending identity. Modern outbound platforms run sender rotation across multiple inboxes and multiple domains, distributing volume so that no individual sender carries enough load to attract negative attention from filters.
A practical rotation setup looks like this: register 4-6 secondary domains (never your primary brand domain), provision 2-3 inboxes per domain, warm all of them in parallel, and rotate sends across the pool. A sequence might originate from inbox A on domain 1 for prospect X, inbox B on domain 2 for prospect Y, and inbox A on domain 3 for prospect Z. Each individual sender stays well under per-inbox limits, and the loss of any single sender (through a deliverability hit, a domain blacklist, or a manual issue) takes out a small fraction of capacity rather than the whole operation.
This is exactly how ACA approaches outbound at scale. Sender pools are managed natively, rotation logic distributes volume automatically across the inboxes you connect, and reputation issues on any individual sender are contained without disrupting active campaigns. Combined with multi-channel routing, where prospects who do not engage on email get reached on LinkedIn, WhatsApp, or Instagram, the total reliance on any single email identity drops sharply. Lower per-inbox volume plus channel diversification plus rotation equals reputation that is structurally protected rather than constantly at risk.
Use a single dedicated sender when: you are a solo founder sending fewer than 30 personal emails per day to highly qualified prospects, and your domain has been warmed and clean for 6+ months.
Use rotation across multiple inboxes and domains when: you send more than 50 cold emails per day, you run outreach for multiple clients, or you cannot afford a single deliverability incident to halt your pipeline.
Frequently Asked Questions
How long does it take to build a strong sender reputation?
Plan on 6-8 weeks minimum from a brand new domain to a sender reputation that can sustain consistent cold outreach at 50-80 emails per day per inbox. The first 4 weeks are warm-up and low-volume real sending. Weeks 5-8 are gradual scale-up with daily monitoring. A reputation built over 6 months is materially stronger than one built in 6 weeks, so the longer you operate cleanly, the more resilient your sending becomes.
What is a good sender reputation score?
On SenderScore, anything above 80 on a 0-100 scale is considered healthy. Above 90 is excellent. In Google Postmaster Tools, you want domain reputation rated High, IP reputation rated High or Medium, and spam complaint rate consistently below 0.1%. These are not single numbers that matter in isolation; they matter as a trend. A 95 SenderScore trending downward is more concerning than a stable 82.
Can I share an IP address across multiple sending domains?
Yes, and most senders do. If you use Google Workspace or Microsoft 365, your IP is shared across millions of other senders by default. The risk is neighbor abuse: bad behavior by other senders on the same IP pool can hurt your deliverability. For most cold outreach use cases, domain reputation matters more than IP reputation in 2026, so a shared good-reputation pool plus a clean domain is workable. Dedicated IPs make sense only at high volume (typically 100K+ emails per month per IP).
How do I recover from a damaged sender reputation?
Stop all cold sending from the affected domain immediately. Identify the root cause: dirty list, volume spike, ignored unsubscribes, content issues, or compromised account. Fix it. Run a 4-6 week re-warm cycle using a warm-up service while sending only to your most engaged contacts. Submit delisting requests if you are on any blocklists. In parallel, set up fresh secondary domains so your active campaigns can continue from clean infrastructure while the damaged domain recovers. Recovery is possible but slow. Prevention is always cheaper.
Does email content affect sender reputation?
Indirectly, yes. Content that triggers spam complaints (heavy HTML, promotional language, misleading subject lines, multiple links, large attachments) drives up your complaint rate, and complaint rate is one of the largest reputation inputs. Content that drives replies (short, relevant, personalized) builds reputation. The content itself is not scored independently; it is the engagement and complaint behavior the content generates that moves your reputation.
What is the difference between sender reputation and email deliverability?
Sender reputation is the underlying score. Deliverability is the observed outcome. You can have decent reputation and still hit the promotions tab due to content patterns; you can have strong reputation and still see bounces due to recipient-side issues. Reputation is the lever you control most directly, and improving it improves deliverability across the board, but they are not the same metric.