Updated · 8 min read
Domain vs IP reputation: which one actually matters
Every deliverability conversation eventually lands on the same confusion: is my reputation about the IP or the domain? Both, but not equally, and the balance has shifted over the past five years. Understanding the difference changes what you monitor, how you warm up, and which problems you can actually fix.
Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
Two reputation systems, not one
Your sending reputation is actually two parallel systems that mailbox providers evaluate independently and combine into a filtering decision.
IP reputationis tied to the numerical IP address that your mail server sends from. It reflects the sending behaviour of whoever uses that IP — complaint rates, bounce rates, spam-trap hits. It's shared across every domain sending from that IP, which matters in shared-IP ESP environments.
Domain reputation is tied to the sending domain (the From: address) and its authentication records (SPF, DKIM, DMARC). It reflects how recipients react to mail from that domain specifically — opens, complaints, unsubscribes keyed to the domain identity.
In 2020, IP reputation was dominant. By 2026, domain reputation is the heavier weight for Gmail, Microsoft, and Yahoo combined. The industry has shifted to follow the identity, not the infrastructure.
How they behave differently
| Dimension | IP reputation | Domain reputation |
|---|---|---|
| Tied to | Sending IP address | Sending domain (From: + DKIM) |
| Warm-up required | Yes, volume-based | Yes, but slower to build |
| Recovery from spike | Faster (weeks) | Slower (months) |
| Portable across ESPs | No — lost if you move IP | Yes — follows the domain |
| Shared vs dedicated | Shared in small-volume tiers | Always dedicated to you |
| Weight in 2026 filtering | Secondary signal | Primary signal for major ISPs |
The practical consequence: if you switch ESPs and take the same domain with you, your domain reputation survives the move (it's your domain). Your IP reputation does not — the new ESP uses different IPs, and you start over. This is why modern senders invest disproportionately in domain reputation: it's the portable asset.
Where each one breaks
IP reputation breaks whenyou send too much volume too fast from a cold IP, when you're on a shared IP with a noisy neighbour, or when an internal list-buying incident produces a spam-trap spike.
Domain reputation breaks whenuser-level behaviour goes negative — complaint rate climbs, engagement falls, spam-folder placement increases. It's more psychological than mechanical. Users marking you as spam or simply not opening hurts your domain specifically, independent of which IP delivered the mail.
The IP warmup guide covers the IP side; the list hygiene policy protects the domain side. Both matter, but they're solved with different tools.
Subdomains as reputation isolation
,
This is one of the most under-used deliverability levers. The cost is five minutes of DNS configuration; the benefit is that a marketing incident can't poison your password-reset emails. Senders at scale run three or more subdomains — marketing, lifecycle, transactional — each with its own reputation profile.
The top-level domain (the brand.com itself) contributes a small halo effect, but the subdomain is where the reputation actually lives for filtering purposes.
What to monitor and where
For IP reputation:your ESP's delivery dashboard (bounce rate, spam-rate by IP). Third-party tools like SenderScore and Talos give a 0–100 rating. Useful but not authoritative — they approximate what Gmail and Microsoft see.
For domain reputation:Google Postmaster Tools is the single best source — it shows domain reputation as a four-tier rating (Bad, Low, Medium, High) for Gmail specifically. Microsoft has SNDS but it's heavily IP-focused. For other providers, domain reputation is implicit in delivery rates; watch inbox-placement rates via seed-list tools.
The Deliverability Management skill includes the monitoring cadence — weekly for Google Postmaster, monthly for broader trends, daily during incidents.
The rule of thumb
If you're debating where to focus effort:
Protect domain reputation first.It's the slower-moving, harder-to-recover, portable asset. Bad user signals (complaints, unsubscribes, dormant senders) damage it and take months to heal. The list hygiene policy, unsubscribe flow, and frequency discipline all protect domain reputation.
Manage IP reputation second.IP reputation is recoverable within weeks if you throttle volume and send to engaged users. It's also largely handled by your ESP if you're on a dedicated IP with proper warm-up. Shared-IP senders have less control, which is why volume-growth senders should plan to graduate to a dedicated IP.
The guide on dedicated vs shared IP covers the volume threshold for that decision.
Frequently asked questions
- Does IP reputation still matter in 2026?
- Yes, but less than it did five years ago. Major mailbox providers weight domain reputation more heavily for consumer filtering. IP reputation still matters for initial delivery decisions and for protecting shared-IP senders from bad neighbours, but it's no longer the dominant signal.
- What's the single best tool for monitoring domain reputation?
- Google Postmaster Tools — it shows a four-tier domain reputation rating (Bad, Low, Medium, High) specifically for Gmail. For non-Gmail providers, use seed-list inbox-placement tools or watch your ESP's delivery rates segmented by recipient domain.
- If I switch ESPs, do I lose my reputation?
- You lose the IP reputation (new IPs on the new ESP) but keep the domain reputation (same domain, same authentication records). The switch requires an IP warm-up period, but you start with your accumulated domain trust intact — which is why modern senders care about domain reputation more.
- Should I use subdomains for different send types?
- Yes, for any program at moderate scale. Separate marketing from transactional (e.g., marketing.brand.com vs accounts.brand.com). Each subdomain builds its own reputation, isolating an incident in one from affecting the other. The DNS setup is a one-time cost.
- How long does it take to build domain reputation?
- 3–6 months to reach 'Medium' on Google Postmaster with consistent positive signals. 12+ months to reach and maintain 'High'. It builds more slowly than IP reputation but is also more durable — a single bad week doesn't wipe it out the way it can reset IP reputation.
- What hurts domain reputation most?
- Complaint rate above 0.3%, sending to dormant addresses that don't engage, hitting spam traps, and failing SPF/DKIM/DMARC alignment. In that order of severity. The list hygiene policy and unsubscribe flow directly protect against the top three.
This guide is backed by an Orbit skill
Related guides
Browse all →Reputation recovery: the 90-day playbook for dropping from High to Low
Domain reputation at Low or Bad isn't recoverable in a week. It's a 6–12 week project of disciplined sending to engaged users only, while the reputation signals slowly reset. Here's the structured recovery plan.
Email deliverability — the practitioner's guide
Deliverability is the cumulative result of every send decision over the lifetime of a domain. This guide covers the four pillars — authentication, reputation, engagement, and list hygiene — and how to recover when one breaks.
The unsubscribe page is the most important page in your lifecycle program
The page every lifecycle team ignores is the one that quietly decides sender reputation, suppressed-list quality, and the fate of your next quarter's deliverability. A short defence of why it's worth the ten-minute rebuild.
SPF, DKIM, and DMARC explained for lifecycle marketers
Three DNS records decide whether your marketing email is trusted or binned. Gmail and Yahoo have required all three for bulk senders since 2024. This is the practitioner's explainer — what each one does, how they interact, and the configuration that actually works.
Dedicated vs shared IP: the real decision
Every Braze sales conversation pitches the dedicated IP. Most programs don't need one. Here's the volume threshold that actually justifies a dedicated IP, the risks most teams don't anticipate, and when the shared pool is genuinely the better call.
List hygiene: the six-rule policy
List hygiene isn't cleanup; it's a continuous policy that runs automatically. Here's the six-rule policy every lifecycle program should have written down, each tied to a specific deliverability outcome.
Found this useful? Share it with your team.