Domain Reputation vs IP Reputation: Which One Is Hurting Your Email?

Opens drop. Bounces climb. Support says Gmail is “blocking us.” The ESP dashboard shows green checks for SPF and DKIM. Something still hurts, and the something is often split across two scores you cannot see in one place.

Domain reputation is how receivers remember your domain’s mail. IP reputation is how they remember the server that connected. Filters use both. Fixing the wrong one wastes weeks.

What is domain reputation in email?

Domain reputation is the rolling judgement receivers attach to domain names in your mail, especially:

• The From domain your recipient sees.
• The DKIM signing domain (d= in Authentication-Results).
• The envelope domain (Return-Path / MAIL FROM), which feeds SPF and some complaint feedback loops.

Signals that move domain reputation:

Signal	What it means
Spam complaint rate	Users hit “Report spam” on your mail
Spam trap hits	Mail to abandoned addresses that never opted in
Authentication failures	SPF, DKIM, or DMARC misalignment over time
Engagement	Opens and replies (where the receiver can measure them)
Volume spikes	Sudden sends from a cold domain
Policy violations	Missing one-click unsubscribe on bulk, deceptive headers

Gmail exposes domain reputation (High / Medium / Low / Bad) in Google Postmaster Tools once you verify the domain. That view is domain-centric by design for bulk senders.

Domain reputation survives IP changes. Switch ESPs, get a new pool, and your domain history comes with you.

What is IP reputation in email?

IP reputation attaches to the IPv4 or IPv6 address that opened the SMTP session to the receiver.

Signals include:

• Historical spam volume from that IP.
• Blocklist listings (Spamhaus, Barracuda, and others).
• Reverse DNS and HELO consistency.
• Complaint rates for mail sent from that IP, aggregated across all customers on a pool.

If you send through an ESP’s shared pool, you share IP reputation with strangers. A dedicated IP concentrates history on your mail alone, which is good when you warm it carefully and bad when you blast a cold list on day one.

Microsoft SNDS and similar tools expose IP-level complaint and trap data for senders on dedicated or self-hosted ranges. Shared ESP pools rarely give you that visibility unless the provider surfaces it.

Domain reputation vs IP reputation: which matters more?

Neither wins alone. Receivers combine IP and domain signals with authentication results and content features.

Use this rule of thumb:

Symptom	Likely primary lever
Bounce cites blocklist or IP (e.g. Spamhaus, 421 deferral naming an IP)	IP reputation / blocklist
Gmail Postmaster domain reputation drops; IP not listed	Domain reputation, list quality, or auth alignment
Only one ESP path fails	That path’s IP pool or subdomain auth, not whole brand
Everything from the domain fails at all providers	Domain-wide auth break or domain reputation collapse
New domain, old IP pool	Domain is cold; IP may be warm or toxic

Authentication problems are domain problems first. Fix SPF, DKIM, and DMARC before you buy a new IP. Why SPF fails and Gmail sender requirements are the usual starting points.

How do I check my domain reputation?

You do not get a universal public “domain score.” You assemble evidence:

1. Google Postmaster Tools (after domain verification): domain reputation, spam rate, authentication pass rates, delivery errors.
2. DMARC aggregate reports: sudden new sources or failing alignment on your domain.
3. Seed or placement tests: inbox vs spam placement by provider for controlled messages.
4. The email health check: SPF, DKIM, DMARC, and DNS posture on the sending hostname.

Low Postmaster domain reputation with clean authentication often points to complaints or low engagement, not DNS typos. Cross-check complaint rate against list source and frequency.

How do I check my IP reputation?

1. Bounce messages: copy the IP from the error and note whether the text mentions blocklists or “poor reputation.”
2. Blocklist lookup: run the sending IP through the blocklist checker (and watch both IPv4 and the pool your ESP actually uses).
3. ESP support: ask which IP sent the failing campaign and whether the pool changed recently.
4. Headers: on a received message, trace Received: hops to the first external hop your ESP used; that address is what many filters scored.

If the IP is listed, delist and fix the cause before you re-send at volume. Blocklist delisting covers the sequence.

Can you have good domain reputation and bad IP reputation?

Yes. Typical story: your domain looks fine in Postmaster, but Yahoo defers with a volume or reputation code because another tenant on the shared IP misbehaved yesterday.

Fix path:

• Ask the ESP to move you to a cleaner pool or provision a dedicated IP and warm it.
• Reduce volume until deferrals stop.
• Keep domain authentication perfect so the domain signal stays an anchor.

Can you have good IP reputation and bad domain reputation?

Also yes. A warmed dedicated IP still lands in spam when the domain collects complaints, sends to bad lists, or fails DMARC alignment on bulk mail.

Fix path:

• Pause campaigns, not receipts, if streams are split; if not, pause bulk first.
• Remove spam traps and inactive addresses.
• Fix alignment and unsubscribe headers for marketing mail.
• Rebuild volume slowly once complaint rate falls.

Does a shared IP hurt my domain reputation?

Shared IPs hurt delivery first, domain reputation second.

Immediate effect: deferrals and blocks triggered by neighbours on the pool.

Longer effect: if your mail consistently sends through a toxic pool, receivers associate your domain plus that infrastructure with unreliable mail. Dedicated IPs and subdomain splits reduce that coupling.

Small senders on reputable ESP shared pools often never notice. High-volume or complaint-prone senders feel pool luck quickly.

How do I fix bad email reputation?

Work in order so you do not swap IPs while authentication is broken.

1. Fix authentication on every sending path: one SPF TXT per hostname, DKIM live, DMARC at least p=none with working rua.
2. Identify the failing path (marketing vs transactional, ESP vs workspace). Split subdomains if one stream poisons the other (marketing vs transactional subdomains).
3. If bounces name an IP or blocklist, fix IP: delist, change pool, or warm a dedicated IP.
4. If Postmaster domain reputation is low with clean auth, fix list quality: remove cold segments, confirm opt-in, add RFC 8058 unsubscribe on bulk.
5. Measure again with placement tests and Postmaster after 7 to 14 days of conservative volume.

Reputation recovers slower than it drops. One bad weekend can take weeks to unwind; consistency beats heroic single-day fixes.

What to do next

Domain and IP reputation answer different questions. Domain is who you claim to be. IP is which server carried the message. Read bounces and Postmaster together before you change ESPs or buy infrastructure.

Put auth and reporting on autopilot with the weekly deliverability review. When DNS and lists are stable but placement still splits by provider, Outlook spam but not Gmail is a common next read.