Reputation and IP warming series. This is the tactical guide to domain vs IP reputation. For related guides on IP warmup, warmup calculation, and cold IP recovery, see the reputation and warming hub →
Quick reputation reference
Every receiver keeps two reputation scores for every sender: one for the sending IP address, one for the sending domain. In 2024 Gmail and Yahoo shifted the weighting: domain reputation now matters more than IP for most placement decisions. Microsoft still weights IP heavily. Understanding which reputation matters where, how each is measured, and how they interact is the difference between a portable sending operation and one locked into whatever infrastructure got you here.
| IP reputation | Per-IP score; travels with the IP; visible in SNDS, Sender Score, Talos |
| Domain reputation | Per-domain score; travels with the domain; visible in Postmaster Tools |
| 2026 weighting: Gmail | Domain > IP for placement; both for enforcement |
| 2026 weighting: Microsoft | IP > Domain, though domain matters more than it used to |
| 2026 weighting: Yahoo | Domain > IP for placement, similar to Gmail |
| Practical implication | Bad domain reputation follows you across every IP; bad IP reputation stays on that IP |
Who this guide is for
- Compliance team preparing 2024 sender rules audit
- Deliverability lead planning an ESP migration
- Ops team debugging placement issues across providers
What you’ll learn
- How Gmail, Microsoft, and Yahoo weight each reputation type
- Portability implications for ESP migration and IP changes
- The monitoring stack per reputation dimension
The reputation and warming series (4 guides)
1. IP warmup schedule
The day-by-day ramp for new IPs
2. Domain vs IP reputation
READINGWhich score matters where in 2026
3. Warmup calculator
Formulas, Python and tables per target
4. Cold IP recovery
When reputation crashed and you rebuild
Domain reputation vs IP reputation, side by side
| Aspect | Domain | IP | Verdict |
|---|---|---|---|
| Portability across ESPs | Survives migration | Stays with the IP | Domain wins |
| Gmail placement weight | Primary signal (2024+) | Secondary | Domain wins |
| Microsoft placement weight | Growing importance | Still dominant (SNDS) | IP wins |
| Recovery time | 6-12 weeks minimum | 2-8 weeks typical | IP faster |
| Escape via migration | Only new domain (nuclear) | Migrate IP easily | IP wins |
| Long-term asset | Compounds for years | Volatile, redistribution risk | Domain wins |
The dichotomy between domain reputation and IP reputation is one of those distinctions that senders can operate for years without understanding, until the day they migrate ESPs and discover their reputation problem followed them. Or the opposite: they solve a reputation crisis by switching IPs and are baffled when the domain score does not recover. This guide covers what each type of reputation actually measures, how the 2024 receiver shifts changed the game, how to monitor each independently, and how to rebuild when damage strikes.
The two scores, side by side
IP reputation
A per-IP-address score. Every receiver keeps a running record for each sending IP: how much it sends daily, how much is accepted, what the bounce and complaint rates look like, what blocklists it appears on. Metrics:
- Sending volume trend (steady, growing, spiking).
- Acceptance rate (fraction of connections and RCPT TOs accepted).
- Bounce rate per period.
- Complaint rate per period.
- Engagement rate (opens, clicks for tracked mail).
- Blocklist status at Spamhaus, Barracuda, SORBS, and a dozen others.
Visible externally via Sender Score (Validity), Microsoft SNDS, Talos Intelligence, and various blocklist trackers.
Domain reputation
A per-domain score. Receivers track how the sending domain (the From: header domain, or the DKIM signing domain, depending on receiver) performs. Metrics:
- Aggregate sending volume across all IPs for this domain.
- Aggregate acceptance rate.
- Aggregate bounce and complaint rates.
- DKIM signing consistency (is the domain signing all mail?).
- DMARC alignment status.
- Domain-level engagement trends.
Visible externally in Google Postmaster Tools (Domain Reputation dashboard) and, indirectly, in Microsoft Outlook.com’s SmartScreen behavior.
The 2024 shift: why domain now dominates
Historically, IP reputation was the primary signal because IPs were the stable identifier: a sender used one or a few IPs consistently. Domains were treated as secondary; multiple domains could share an IP, and IPs were seen as the “real” sending infrastructure.
Two changes broke this model:
- Shared IP pools became universal. Every major ESP (SendGrid, Mailgun, Postmark, SES) moved most customers to shared IP pools. A single IP now handles mail from hundreds of senders. Per-IP reputation became less useful as a signal about any individual sender.
- Authentication protocols matured. DKIM signatures identify the sending domain unambiguously per message. Receivers can now attribute mail to a specific domain regardless of which IP delivered it. This makes per-domain tracking practical at scale.
Gmail and Yahoo’s February 2024 sender rules codified the shift: DKIM alignment is mandatory, DMARC (at least p=none) is mandatory, and receivers explicitly weight domain reputation for filtering decisions. Microsoft moved more slowly but has trended in the same direction.
Real-world scenarios: which reputation matters for you
You are on a shared IP pool (SendGrid, Postmark, Mailgun free tier)
FOCUS DOMAINThe ESP handles IP reputation for the pool. Your leverage is on domain reputation: keep DKIM signing consistent, monitor Postmaster Tools daily, audit your From: domain across all sending streams.
Monitor: Postmaster Tools Domain Reputation · Skip: per-IP dashboards (pool-owned) · Action: subdomain segmentation by stream
You have a dedicated IP (500k+/month or reputation-sensitive brand)
MONITOR BOTHBoth reputations are yours to manage. IP for Microsoft placement (SNDS remains dominant there); domain for Gmail and Yahoo placement. Sender Score gives you the aggregate view.
Monitor: SNDS + Postmaster + Sender Score · Watch: divergence between Gmail and Microsoft delivery · Action: quarterly DKIM audit
You just migrated ESPs (SendGrid to Mailgun, or SES to Postmark)
POST-MIGRATIONDomain reputation transfers with your sending domain (no rewarm needed on the domain side). New ESP IPs are cold; warm them following the standard 30/60/90 schedule. Gmail placement will feel migration less than Microsoft placement.
Monitor: Postmaster IP Reputation (rebuild) + SNDS (rebuild) · Skip: re-warm your domain · Action: parallel-run 2 weeks if possible
How each is measured, per receiver
Gmail
Domain reputation drives Gmail placement. The Postmaster Tools Domain Reputation dashboard shows one of: High, Medium, Low, Bad. High means inbox placement is likely; Bad means promotions or spam. IP reputation exists in Gmail’s model but is secondary; the IP dashboard shows the same 4-level scale, but placement decisions weight domain more.
Microsoft (Outlook.com, Hotmail, Live)
Microsoft SNDS (Smart Network Data Services) shows per-IP reputation (“Green”, “Yellow”, “Red”). This remains a strong Microsoft signal. Domain reputation matters increasingly, but the SNDS dashboard is per-IP. To monitor domain reputation at Microsoft, use SNDS combined with domain-level bounce and complaint tracking from your outbound logs.
Yahoo (and AOL, Verizon)
Yahoo weights domain reputation similarly to Gmail. No public dashboard equivalent to Postmaster Tools; monitor via aggregate delivery metrics and Yahoo’s Complaint Feedback Loop (see our FBL guide).
Apple iCloud
Opaque. No public reputation dashboard. Domain reputation implicitly matters (iCloud checks DKIM/DMARC). Monitor via aggregate delivery metrics for iCloud recipients.
Smaller providers and B2B
Corporate mail systems (Google Workspace enterprise, Microsoft 365 enterprise, Zimbra, custom Postfix installations) use various proprietary reputation systems. Most weight domain reputation via DKIM/DMARC. IP reputation is typically checked via blocklist queries (Spamhaus, Barracuda) rather than internal history.
Portability: domain reputation as an asset
The single most important operational difference between IP and domain reputation is portability:
IP reputation stays with the IP
If you migrate ESPs or change sending IPs, the old IP reputation stays with the old IP. Your new IPs start with no reputation and need warmup. This is why ESP migration is disruptive; you cannot carry IP reputation forward.
Domain reputation stays with the domain
If you migrate ESPs but keep the same sending domain (say, news@yourbrand.com), your domain reputation transfers. The new ESP’s IPs need warmup, but Gmail’s model already knows and trusts your domain. Migration is significantly smoother.
Practical implication: treat your sending domain as a long-term asset. Do not casually change it, do not proliferate sending subdomains, and do not let any one campaign or partner damage the reputation of your primary sending domain.
Shared IP vs dedicated IP tradeoffs
Shared IP pools (most ESPs by default)
- Pros: Established IP reputation from pool history. No warmup needed at the IP level. Costs less. Low-volume senders benefit from the pool’s baseline reputation.
- Cons: Your reputation is affected by other pool members. A neighbor’s spam problem can cause pool-wide throttling. You cannot fix IP reputation individually.
- Best for: Small to medium senders (<100,000/month), transactional mail, senders without dedicated deliverability ops.
Dedicated IPs
- Pros: Full control of IP reputation. Isolation from other senders. Reputation directly reflects your sending pattern. Better for high-volume marketing where reputation stability matters.
- Cons: Requires warmup from cold state. Requires sufficient sustained volume to maintain reputation (typically 100,000+/month). Higher cost. Damage takes longer to recover.
- Best for: High-volume senders (500,000+/month), senders with dedicated deliverability teams, senders whose reputation stability is a competitive differentiator.
In 2026, the case for dedicated IPs is weaker than it used to be because domain reputation absorbs some of the role IP reputation used to play. Many senders who were on dedicated IPs 5 years ago now find shared pools work fine at their scale, once domain reputation is well-managed.
Monitoring both, in practice
Daily checks
- Google Postmaster Tools: Domain Reputation and IP Reputation dashboards.
- Microsoft SNDS: IP status (Green/Yellow/Red).
- Your outbound log: bounce rate, complaint rate (from FBL), delivery rate, per-recipient-provider breakdown.
Weekly checks
- Blocklist status at Spamhaus, Barracuda, SORBS via blocklist directory tools.
- Sender Score trends.
- Domain-level engagement rate: opens, clicks, replies per receiver domain.
Monthly checks
- DKIM alignment audit (are all outbound sends properly signed and aligned with From: domain?).
- DMARC aggregate report review.
- Cross-provider deliverability comparison (are Gmail delivery and Outlook delivery diverging significantly?).
Rebuilding after damage
If IP reputation crashed
Symptoms: SNDS turns Yellow or Red, Sender Score drops below 70, Postmaster IP Reputation shows Low or Bad. Steps:
- Identify the trigger (list quality issue, content problem, blocklist listing, complaint spike).
- Fix the trigger before any recovery attempt.
- Pause the affected IP for 3-7 days.
- Re-warm to that IP with your most engaged segment only, starting at very low volume (10 percent of previous baseline).
- Rebuild over 2-4 weeks with tight KPI monitoring.
- Alternatively, migrate to a new IP and warm from cold; see the cold IP recovery guide.
If domain reputation crashed
Symptoms: Postmaster Domain Reputation drops to Low or Bad, Gmail delivery drops sharply, Yahoo delivery drops. Steps:
- Same diagnostic: what triggered it?
- Audit authentication: is DKIM signing consistent? Is DMARC alignment holding?
- Reduce volume to your most engaged segment for 2 weeks.
- Verify content is not the trigger (subject line, link count, keyword patterns).
- Rebuild engagement metrics over 4-6 weeks.
- Domain recovery is slower than IP recovery. Plan for 6-12 weeks minimum for full rebuild.
The nuclear option: new domain
Migrating to a new sending domain (like news2@yourbrand.com or a new subdomain) starts domain reputation from zero. This is a last resort because it also throws away all the reputation you have built. Only viable when your existing domain is beyond repair (severe blocklisting, historical spam patterns, permanent DMARC damage). Consider it after 3+ months of failed recovery attempts.
10 common domain/IP reputation mistakes
- Treating IP as the whole reputation story. In 2026, most placement decisions weight domain more. Monitor both.
- Not verifying Postmaster Tools. Setup takes an hour. Data starts flowing in 48 hours. Not being registered means flying blind on Gmail.
- Sending multiple products from one domain. A promotional campaign and a transactional stream from the same domain conflate reputation signals. Segment via subdomains.
- Not signing all mail with consistent DKIM. Domain reputation depends on DKIM consistency. Unsigned mail or mail with rotating DKIM domains dilutes reputation.
- Assuming shared IP means no reputation work. Shared IP handles the IP side; domain reputation still needs monitoring.
- Chasing new IPs when domain is the problem. Migrating IPs when the domain is damaged just delays discovery of the real issue.
- Not tracking per-provider delivery separately. Gmail and Microsoft weight reputation differently. Divergent trends signal receiver-specific issues.
- Sending high-volume campaigns after a warmup pause. Reputation decays if sending pauses for 30+ days. Re-warm before resuming.
- Rebuilding by increasing volume instead of increasing engagement. Volume without engagement makes reputation worse. Engagement quality drives reputation recovery.
- Not documenting reputation events. Six months later, when the next incident hits, you cannot remember what worked last time. Keep a reputation incident log.
Domain vs IP reputation FAQ
If I use a shared IP, do I still need to worry about IP reputation?
Yes, but indirectly. Your ESP manages the pool’s IP reputation collectively. If the pool degrades (a neighbor sends poorly, gets everyone throttled), you feel it. Monitor your delivery rates and, if the ESP allows, check pool reputation via SNDS. If pool reputation problems persist, consider requesting a different pool or moving to a dedicated IP. Meanwhile, focus your own optimization on domain reputation, which is fully in your control.
Which matters more for Gmail: IP or domain?
Domain, for most placement decisions. Postmaster Tools shows both scores; the Domain Reputation score more directly correlates with inbox placement than the IP Reputation score. Both matter for enforcement (if either goes Bad, you have serious problems), but for the daily promotions-vs-inbox split, domain drives it.
Can I share one sending domain across multiple products?
Not ideally. Different product streams have different engagement patterns and different complaint rates; mixing them under one domain conflates reputation. Best practice is subdomain segmentation: transactional from tx.brand.com, marketing from marketing.brand.com, newsletters from news.brand.com. Each subdomain builds its own reputation. The parent domain’s reputation flows in only through DKIM cross-signing or DMARC organizational domain alignment.
How long does damaged domain reputation take to recover?
Longer than IP reputation. IP reputation can recover in 2-4 weeks with careful rebuild. Domain reputation typically takes 6-12 weeks, sometimes longer for severe cases. This is because domain reputation aggregates over more data points and larger time windows. The recovery discipline is the same: cut volume, focus on engaged recipients only, fix authentication, wait for metrics to stabilize before growing. Domain recovery requires patience.
Should I move to a new subdomain if my main domain is damaged?
Considered move, not a knee-jerk. New subdomain = starting from zero reputation, so you throw away any positive equity you had. Only worth it if: (1) the damage is severe (Postmaster shows Bad for 4+ weeks and rebuild attempts are not working), (2) the root cause was infrastructural (compromised account, historical spam patterns you cannot undo), or (3) the business needs a clean start (rebranding, new product launch). In most cases, rebuild the existing domain is faster and preserves the underlying equity.
Does Microsoft weight domain reputation the same as Gmail?
Not yet. Microsoft still weights IP reputation heavily. This is why SNDS (their IP dashboard) is the primary Microsoft monitoring tool. Domain reputation matters more at Microsoft than it did 5 years ago (DKIM/DMARC compliance is now required), but IP remains the stronger signal. If you have a good domain reputation but a poor IP reputation, Gmail may deliver you to the inbox while Microsoft sends you to junk. Monitor both, adjust per receiver.
Final words
Domain and IP reputation are two lenses on the same question: does this sender deserve inbox placement? The 2024/2025 shift moved the weighting toward domain, which changed the game for portable sending operations. A well-managed domain reputation carries you across ESP migrations, IP rotations, and infrastructure changes. A well-managed IP reputation matters for high-volume dedicated setups and for Microsoft delivery.
The mental model to keep: monitor both, but treat domain reputation as your long-term compounding asset and IP reputation as the more volatile short-term signal. Damage to domain reputation is slower to recover; damage to IP reputation is (relatively) easier to escape by moving IPs. Design your sending architecture with the difference in mind.
For the follow-up articles: the warmup calculator gives you the exact formula for volume ramps, and cold IP recovery covers the case where reputation crashed and you need to rebuild an IP from scratch.
For related content, see the IP warmup schedule, Sender Score, Google Postmaster Tools, SPF, DKIM, DMARC, the Google and Yahoo bulk sender rules, and the Deliverability hub.
Reputation compounds on top of list quality.
SMTPing catches invalid addresses, disposables, catch-all traps, role accounts and dead mailboxes before send. Every avoided bounce is one less point of reputation drag. 13 validation types, 25 free daily.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
