Domain Reputation vs IP Reputation: What Filters Really Use

Domain reputation vs IP reputation is the difference between two signals mailbox providers track separately — and confusing them is why a sender who does everything right on one still lands in spam. IP reputation attaches to the numeric address your mail leaves from. Domain reputation attaches to the authenticated domain in your From address: the identity that follows you no matter which server or provider actually sends the mail.

This post is about which one filters like Gmail and Microsoft actually weight, why moving between providers resets one and not the other, and when a shared IP pool helps you rather than hurts you. The short version is that the two behave differently under one specific pressure — portability — and that difference decides most real questions people ask about deliverability.

The verdict, up front#

For most senders, domain reputation is the signal to invest in. It is portable, it is what email authentication anchors your identity to, and it is what the major mailbox providers increasingly weight. IP reputation still matters, but it is the more replaceable of the two.

A receiver decides where your mail lands by combining several signals: authentication, the sending IP's history, the sending domain's history, the content, and how recipients engage. IP reputation was the dominant signal for years. Since the 2024 bulk-sender requirements from Google and Yahoo tied high-volume sending to authenticated domains, the domain has become the durable anchor. Google Postmaster Tools reports reputation for the domain and IP that send DKIM-authenticated mail — and as of 2026 Google is retiring its standalone reputation dashboards, on the grounds that reputation is only one of many signals affecting delivery.

The practical upshot is portability. Switch email providers or move to a new IP and the IP signal starts near-blank on the new address, while your domain reputation — good or bad — carries straight over. That single fact answers most of the questions below.

Domain vs IP reputation at a glance#

The two signals differ on what they attach to and, more importantly, on what happens when your infrastructure changes. This table is the whole comparison in one screen; the sections after it explain each row.

How DKIM ties reputation to your domain#

The reason domain reputation is portable is written into the DKIM standard. DKIM (RFC 6376) adds a cryptographic signature to each message plus a 'd=' tag naming the signing domain. The standard calls this the Signing Domain Identifier — a domain name that, in its words, 'refers to the identity claiming some responsibility for the message by signing it.'

That identity is verified by a public key published in your domain's DNS, not by the server's IP address. So the reputation a receiver builds attaches to the domain, not the machine. RFC 6376 even names an 'Identity Assessor' — the part of a mail system that consumes exactly that signed domain identifier to assess reputation. DMARC then requires the visible From domain to align with the authenticated domain, so the address a recipient reads is the one carrying the reputation.

This is why sending the same domain's mail through a new provider does not shed a bad reputation, and why a well-warmed IP under a fresh, unknown domain does not inherit that IP's good standing. The verified identity is the domain, and the domain is what receivers remember.

Where domain reputation is the decisive signal#

Domain reputation wins wherever your sending identity outlives your infrastructure — which, for most senders, is most of the time.

• You change providers. Migrating from one ESP to another, or from self-hosted to hosted, gives you a new IP but the same domain — so your inbox-placement history moves with the domain, not the server.
• You send from several systems at once. A newsletter tool, a CRM and your own mail server can all send as your domain. Receivers roll that behaviour into one domain reputation rather than three separate IP reputations.
• You send low or moderate volume. Below the traffic needed to hold an IP reputation, the domain is the more stable signal — there is not enough mail on any one IP to build much IP reputation at all.
• Blocklists increasingly target domains. Spamhaus runs a Domain Block List (DBL) that lists domains by reputation, separate from its IP zones. A domain on the DBL is filtered regardless of which IP sends it.

Google's bulk-sender rules are scored on the domain#

The clearest sign of where the weight has shifted is how Google counts bulk senders. As of 2026, Google's sender guidelines count bulk-sender status per primary domain, aggregating its subdomains — not per IP and not per subdomain in isolation. A domain that trips the spam thresholds carries that history to every subdomain and every IP it sends from, and Google's guidance does not describe a simple way to age out of it.

That is domain reputation doing the heavy lifting by design. You cannot spin up a fresh subdomain or move to a new IP to escape a domain-level problem; the primary domain is the unit of accountability. Check the current rules on Google's own sender-guidelines page before relying on any specific number here, because this regime has tightened repeatedly since 2024.

Where IP reputation still matters#

IP reputation has not gone away. It is the faster, first-pass signal, and it dominates in specific situations.

High-volume senders on a dedicated IP have an IP reputation that is entirely theirs to build and protect — and receivers watch it closely, because the volume is enough to be meaningful. Brand-new domains with no track record lean the other way: a receiver has little domain history to go on, so it weights the IP and the authentication more heavily, and a reputable shared pool can carry a new domain's first sends.

IP reputation also moves fastest when something breaks. If a mail server is compromised or misconfigured and starts sending spam, the IP is what gets blocklisted first — on Spamhaus's IP zones, for example — and delivery can stop before the domain reputation has time to move at all.

The two are assessed together, not either-or. A strong domain reputation does not fully cancel out a badly blocklisted IP, and a pristine IP does not rescue a domain listed on the DBL. Fix whichever one is actually flagged.

Shared IP vs dedicated IP, and IP warming#

The shared-versus-dedicated choice is where the 'bad neighbour' question lives — and where you have to check what your provider actually gives you, because it varies by plan.

Can a bad neighbour on a shared IP hurt you?#

Yes, in principle — a shared IP's reputation reflects everyone sending on it, so a spammer in the same pool can drag placement down. That is a genuine risk, not a myth.

In practice, a reputable ESP segments its pools by sender reputation, monitors complaint rates, and removes bad actors quickly — and the growing weight on domain reputation blunts the effect for a sender with a clean domain. For most low-to-moderate senders, a well-run shared pool beats an under-warmed dedicated IP, because the pool arrives already warm.

A dedicated IP removes the neighbour risk entirely, but only pays off if you can keep it warm. That means warming it first, and then sustaining volume:

1. 1

   Start small, with your best recipients

   Send only to your most engaged contacts on day one, in the low hundreds. Early engagement is the signal receivers use to trust a cold IP.

2. 2

   Increase volume gradually

   Roughly increase the daily send each few days, as long as complaints stay low and opens stay healthy. A sudden spike from a cold IP looks like a botnet and gets throttled or rejected.

3. 3

   Keep it consistent

   A dedicated IP that goes quiet loses its warmth. Receivers expect steady volume, so an IP you send from once a month never really warms up.

4. 4

   Watch the spam rate

   Track your spam rate in Google Postmaster Tools. Google's sender guidelines ask senders to keep it below 0.3%; pull back if it climbs toward that line.

Does changing ESPs reset your reputation?#

This is the most common real question, and the answer is: switching resets the IP reputation, not the domain reputation.

When you move to a new ESP, your mail leaves from that provider's IPs — a fresh dedicated IP with no history, or a shared pool whose reputation you inherit. Either way, the old IP's history stays behind. Your domain reputation does not move an inch: same domain, same DKIM identity, same standing at every receiver.

The practical consequence of portability#

If you switched ESPs hoping to escape a spam-folder problem, and your domain reputation is the thing that is damaged, the move will not help. You will land in spam on the new provider too — just from a different IP. The domain, and its history, came with you.

So repair the actual signal that is flagged. If the IP is blocklisted, a clean IP or a good pool fixes it. If the domain reputation is the problem, the fix is authentication, recipient engagement, and getting your complaint rate down — none of which a new IP address touches.

Who should focus on which#

Feature-by-feature, this is what decides where to spend your attention.

Where AI Emaily fits — and where it doesn't#

A note on where we sit, because this is exactly the kind of page where a mail client tries to insert itself and shouldn't. We build AI Emaily, an AI-native email client for reading, triaging and replying to your inbox. It is not an ESP, a sending platform, or a deliverability tester — it does not manage your outbound sending IP, warm a dedicated IP, or move your domain's sending reputation. If your job is getting bulk or transactional mail into other people's inboxes, the tools you need are your ESP, Google Postmaster Tools and blocklist checks, not us.

Where the two topics genuinely touch is the receiving side. AI Emaily's spam and phishing defence and its cold-email filter judge the reputation and behaviour of the domains sending mail to you — the same domain-over-IP logic, seen from the inbox rather than the sending server. A cold-outreach operation that rotates IPs but keeps one domain is easier to catch on domain and behaviour than on a single address, and we do not train any model on your mail.

So the honest scope: for sending reputation, the tools on this page are the answer. For the mail that reaches your inbox — triage, drafting in a voice you set, an agent that acts with an approval step and a full audit trail — that is what we do. The overview is on the homepage (/) and current plans are at /pricing. It is a paid product with a 7-day free trial (card required, $0 if you cancel before day seven), not a free tier.