Domain vs IP reputation: which one actually matters

Picture a Gmail server, the moment your email lands at its door. Before that mail is shown to a human, Gmail makes a filtering call — inbox, promotions, spam, blocked outright. Most marketers imagine that decision is graded against a single "sender reputation" score. It isn't. Two parallel scores get computed, weighted, and combined.

IP reputation is tied to the sending IP address — the numerical address (like 192.0.2.10) of the mail server that pushed your message out. It reflects the behaviour of whoever uses that IP. Complaint rates, bounce rates, spam-trap hits — all the mechanical signals. On a shared-IP plan (where your ESP — the platform that sends your email, like Braze or Klaviyo — pools you with other senders on the same address), that's your behaviour plus everyone else's in the pool.

Domain reputation is tied to the sending domain — the bit after the @ in your From: address, plus the domain that signs your mail via DKIM (a cryptographic signature mailbox providers use to verify the sender). It reflects how recipients react to mail from you specifically. Opens, complaints, unsubscribes — all keyed to who you are, not where the mail came from.

Does IP reputation still matter? Yes — just less than it did five years ago. It still shapes initial delivery decisions, and it's the thing protecting you from noisy neighbours on a shared pool. What changed is that it's no longer the primary lever.

The simplest way to understand the split: IP reputation is about the address, domain reputation is about the brand. Move house and your address changes — but the brand follows you. That single asymmetry explains almost every practical difference between them.

The practical implication: if you switch ESPs and bring the same domain, your domain reputation moves with you. It's yours. Your IP reputation does not — the new ESP ships from different IPs and you warm from scratch (warming = ramping volume gradually so providers learn to trust the address). Which is exactly why modern senders invest disproportionately in the domain side. It's the portable asset.

Building a domain reputation from zero to "Medium" on Google Postmaster Tools (Gmail's free dashboard for senders) takes three to six months of consistent, positive signal. Getting to "High" and holding it is a twelve-months-plus commitment. It moves slower than IP reputation in both directions — harder to build, harder to destroy — which is the trade-off that makes it valuable.

The breakage modes are different because the inputs are different. IP reputation goes wrong mechanically, in days. Domain reputation goes wrong behaviourally, over weeks. Knowing which is which tells you whether to call your ESP or look at your list.

IP reputation breaks when you ship too much volume too fast from a cold IP, when a noisy neighbour in your shared pool hits spam traps (dead addresses providers seed to catch list-buyers), or when an internal list-buying incident produces a trap spike the ESP notices before you do.

Domain reputation breakswhen user-level behaviour turns negative. Complaint rates climb, engagement falls, spam-folder placement creeps. It's less mechanical and more behavioural — users marking you as spam, or just never opening, drags the domain regardless of which IP pushed the mail out.

The worst offenders, roughly in order: complaint rate over 0.3%, sending to dormant addresses that never engage, spam-trap hits, and SPF/DKIM/DMARC alignment failures (the three authentication standards mailbox providers check to verify mail genuinely came from you). The IP warmup guide handles the IP side; the list hygiene policy defends the domain side. Both matter. They take different tools.

Imagine your marketing team has a rough send. Subject line lands wrong, complaint rate spikes, the domain takes a hit. Now picture the next user who hits "forgot password" — and the reset mail goes to spam because it's coming from the same domain that just got flagged. That's the failure mode subdomains exist to prevent.

This is probably the most under-used deliverability lever in the industry. Five minutes of DNS configuration (the records that tell mail providers who's authorised to send for a domain), and a marketing incident can no longer poison your password-reset mail. Senders at scale run three subdomains as a baseline — marketing, lifecycle, transactional — each carrying its own reputation profile.

The root domain (brand.com itself) does contribute a small halo effect, but the subdomain is where the real filtering weight sits. Use that. At any moderate scale the answer to "should I subdomain?" is yes.

The annoying part of deliverability is that the people grading you don't share their gradebook. Mailbox providers don't publish your reputation score — they show you proxies. Knowing which proxy maps to which score saves a lot of time staring at the wrong dashboard.

For IP reputation:your ESP's delivery dashboard — bounce rate and spam rate segmented by IP. SenderScore and Talos give a 0–100 approximation of what Gmail and Microsoft are seeing. Useful, not authoritative.

For domain reputation: Google Postmaster Tools is the single best source. It shows a four-tier rating — Bad, Low, Medium, High — for Gmail specifically. Microsoft SNDS (Smart Network Data Services, their equivalent dashboard) exists but is mostly IP-focused. For everyone else, domain reputation is implicit in delivery rates, and seed-list inbox-placement tools (services like Litmus or GlockApps that send to test addresses across providers) are how you approximate it.

The Deliverability Management skill has the monitoring cadence end to end — weekly Postmaster pulls, monthly trend review, daily checks during incidents.

The whole guide collapses to a single priority order. Most teams have it backwards.

Protect domain reputation first.It's slower-moving, harder to recover, and it's the portable asset. Bad user signals — complaints, unsubscribes, dormant sends — damage it and take months to heal. Your list hygiene policy, unsubscribe flow, and frequency discipline are all really protecting the domain.

Manage IP reputation second. IP recovers in weeks if you throttle volume and send to engaged users. Most of it is handled by your ESP anyway, assuming a dedicated IP with a proper warm-up. Shared-IP senders have less control over it, which is the main argument for graduating to a dedicated IP once volume justifies it.

The dedicated vs shared IP guide has the volume threshold for that call.