KoltrixDomain reputation vs IP reputation: which is hurting you?
Modern filters weigh your domain more heavily than your IP, but both matter. How to tell which one is dragging placement down and what fixes each.
On this page(8 sections)
When mail starts landing in spam, the first question is usually "is our IP blocked?" Increasingly, the better question is "what do receivers think of our domain?" Both reputations exist, they influence each other, and the fix depends on which one is actually dragging you down.
Two reputations, measured differently
IP reputation attaches to the address that connects to the receiving server. It is the older mechanism, dating from the era when spam came from identifiable servers and blocklists listed IPs. Receivers track how much mail an IP sends, how much of it recipients complain about, how many messages hit spam traps, and whether its volume patterns look normal.
Domain reputation attaches to the domains in a message: the From domain, the DKIM signing domain, the envelope sender domain and, for many filters, the domains of links in the body. Authentication made domain reputation reliable. Once a receiver can verify through DKIM and DMARC that a message genuinely comes from example.com, it can build a history for example.com that follows it across IPs and providers.
Why domain reputation now carries more weight
Several shifts moved the emphasis toward domains:
- Shared infrastructure. Most mail is sent through large providers using shared IP pools. An IP's history mixes thousands of senders, so it says less about any one of them.
- IPv6 and cloud sending. Senders can move between IPs easily. A reputation tied only to IPs is easy to escape.
- Authentication requirements. Gmail and Yahoo require bulk senders to authenticate with SPF, DKIM and DMARC and to align the From domain. Microsoft added similar requirements for high-volume senders to Outlook.com in 2025. Those rules exist partly so that domain reputation can be trusted.
- Postmaster dashboards. Google Postmaster Tools reports data per authenticated domain, which tells you how Google itself frames the question.
None of this means IP reputation stopped mattering. A known-bad IP is still a problem, and some receivers lean on IP data more than others. But you cannot fix a domain problem by changing IPs, and switching IPs to escape a domain problem usually just adds a cold-IP problem on top.
Diagnosing which one hurts
Signs of an IP problem
- The IP appears on a major blocklist.
- SMTP rejections mention the connecting IP or a blocklist by name.
- Placement problems affect every domain sending through that IP, including ones with good engagement.
- Microsoft SNDS shows the IP's filter result turning yellow or red.
- The problem appeared right after moving to new IPs or a new pool.
Signs of a domain problem
- Placement problems follow the domain across providers or IP pools.
- Google Postmaster Tools shows rising spam rates for the domain.
- Rejections or filtering mention the domain, or link domains in the content.
- Other domains sending through the same IPs are fine.
- Problems are worse for the stream with weak engagement, such as marketing, while transactional mail on a separate subdomain is unaffected.
A quick comparison test
If you have more than one stream, compare them:
| Observation | Points to |
|---|---|
| Two domains on the same IPs; only one suffers | Domain |
| One domain on two IP pools; both suffer | Domain |
| One domain on two IP pools; only one pool suffers | IP |
| All domains on one IP suffer at once | IP |
| A link domain appears in all affected messages | Link domain |
Do not forget link domains. A URL shortener or a shared click-tracking domain with a poor reputation can drag down mail that is otherwise clean.
Fixing an IP problem
- Find the cause before delisting. A blocklist entry is a symptom: compromised accounts, a bad list import or an open relay.
- Request removal through each blocklist's own process once the cause is fixed.
- Reduce volume temporarily and send only to engaged recipients while the IP recovers.
- For shared IPs, talk to your provider. They control the pool and can move you or address the noisy neighbor.
Fixing a domain problem
Domain reputation recovers through behavior, not configuration:
- Stop mailing people who do not engage. Remove or sunset recipients who have not opened or clicked in months. Unengaged recipients are where complaints and traps come from.
- Cut complaint sources. Make unsubscribing easy, including one-click unsubscribe for bulk mail, and honor requests within the two days Gmail and Yahoo expect.
- Fix authentication gaps. Unaligned or missing DKIM makes it harder for receivers to credit good mail to your domain.
- Separate streams. Put marketing on a subdomain so its reputation does not drag down password resets.
- Ramp back up slowly. After cutting back, increase volume gradually, starting with your most engaged recipients.
Expect recovery to take weeks of consistent good behavior. There is no form to submit to restore a domain's reputation at a large mailbox provider.
How they interact
The two reputations are not independent. Mail from a new, unknown IP gets more scrutiny, so receivers rely more on domain reputation, and a strong domain helps a new IP warm up faster. Conversely, a strong IP cannot fully rescue a domain with high complaint rates. When planning infrastructure changes, think about both: moving to dedicated IPs means building IP reputation from scratch while carrying your existing domain reputation with you.
A diagnostic checklist
- Check major blocklists for your sending IPs and link domains.
- Read SMTP rejection text for mentions of IPs, domains or lists.
- Review Google Postmaster Tools spam rate per domain.
- Review Microsoft SNDS for your IPs, if dedicated.
- Compare streams and pools to isolate the variable.
- Look at recent changes: new IPs, new list sources, new content, volume spikes.
Bottom line
IP reputation and domain reputation both influence placement, but modern filtering leans on the authenticated domain because it follows you wherever you send from. Diagnose by comparing streams, IPs and providers to isolate the variable. Fix IP problems by removing their cause and requesting delisting; fix domain problems by changing who you mail and how often, then waiting for consistent behavior to rebuild trust.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
