IP reputation vs domain reputation: what matters more

Email marketers often hear: “Your sender reputation is bad.” But sender reputation is actually two separate scores: IP address reputation and domain reputation. They are built differently, checked with different tools, and carry different weight with mailbox providers. Here's what each one means and where you should spend your energy.

What IP reputation is

Every email leaves from a specific IP address. Mailbox providers track the history of each IP: how many messages arrive, what percentage bounce, how many spam complaints come in, whether the IP hits spam traps. All of that feeds into a numerical score called IP reputation.

If you send through an ESP on a shared IP, that address is split among dozens or hundreds of other senders. Your deliverability depends on their behavior too. One sender with a dirty list and a high bounce rate, and the IP takes a hit—along with your campaigns.

On a dedicated IP, you own the history. Your sends shape the reputation. That's control, but it also means any bounce spike or complaint surge lands entirely on you.

What domain reputation is

Domain reputation ties to the domain in your From address and the domain in your DKIM signature. It is a more durable signal than IP reputation: your domain does not change when you switch ESPs or IP pools, so providers build up a long history around it.

Gmail, Outlook, and Yahoo have all shifted primary filtering weight to the domain over the past two years. The reasoning is straightforward: IPs are cheap to rotate, domains are not. Spammers cycle through thousands of IPs but expose themselves through the domain. DKIM locks a cryptographic signature to that domain, making it a reliable identifier.

Domain reputation is shaped by the same factors as IP reputation, plus a few more:

• Bounce rate. A high hard-bounce rate tells providers you are mailing a dirty list.
• Spam complaints. Every click on “Mark as spam” is logged against your domain.
• Spam traps. Hitting provider-operated traps damages reputation faster than almost anything else.
• Engagement. Open rate, clicks, replies. Gmail tracks whether recipients open your messages or delete them unread.
• Authentication. SPF, DKIM, DMARC. Without them, sends do not accumulate positive domain history because providers cannot attribute them to you.
• Domain age. New domains start at zero. Providers treat them with suspicion until enough positive signals build up.

Why domain reputation carries more weight in 2026

Five years ago, IP reputation was the primary filtering signal. That has changed. Google's Postmaster Tools documentation explicitly states that domain reputation takes priority when determining placement: whether a message lands in the inbox, Promotions tab, or spam folder.

A few things drove that shift. Cloud ESPs share IP pools across thousands of customers, which made per-IP scoring unreliable. Spammers got good at rotating IPs to sidestep IP-based blocks. And DKIM gave providers a cryptographic anchor to a domain—one that cannot be faked without DNS access—making domain-level scoring far more precise.

IP reputation decides whether your message is accepted by the receiving server. Domain reputation decides where it ends up after that.

IP reputation still matters. If your IP appears on major blocklists like Spamhaus or Barracuda, the receiving server rejects the connection before it ever looks at your domain. But once the SMTP connection is accepted, domain reputation is what determines whether the recipient sees your message.

IP warm-up: when you need it and how to do it

Warm-up only applies when switching to a dedicated IP. On a shared IP, the pool already has an established reputation and no warm-up is required.

The idea: start with a small volume and double it every two to three days. Day one, 200 emails. Day two, 400. Day three, 800. Send to your most engaged subscribers first—people who opened or clicked in the past 30 days. Their positive responses show providers that real mail is coming from the new IP.

The whole process takes 2–6 weeks depending on your target volume. Planning to send 500k per month? Closer to six weeks. For 50k, two weeks is usually enough.

How to check both reputations

For IP reputation: Sender Score from Validity (free), Talos Intelligence from Cisco, MXToolbox Blacklist Check. These show whether your IP appears on blocklists and assign a score from 0 to 100.

For domain reputation: Google Postmaster Tools is mandatory if any part of your list is on Gmail. It shows domain reputation (High, Medium, Low, Bad), spam rate, and authentication failures. Microsoft SNDS gives the equivalent data for Outlook. Both are free.

Check regularly: weekly for active senders, monthly if you mail less often. Reputation drops are visible before they turn into deliverability problems—but only if you are actually looking at the data.

Where to focus your effort

If you send through an ESP on a shared IP—which describes most companies mailing fewer than 100k contacts—your IP reputation is largely outside your control. It depends on the ESP's enforcement policies. Choose an ESP that vets customers and removes bad actors quickly. Postmark, Mailgun, and Sendsay are known for strict moderation, and that strictness is a feature, not a drawback.

Domain reputation is entirely yours to manage. These five factors drive it, ranked by impact:

When a dedicated IP actually makes sense

A dedicated IP is worth it in three situations. First: your volume consistently exceeds 50k messages per month. Below that threshold, the IP does not accumulate enough data to build a stable reputation, and providers treat it with suspicion.

Second: your ESP does not enforce quality standards, and you are seeing deliverability drops despite a clean list. That is a sign shared-IP neighbors are pulling down the pool's reputation.

Third: predictable delivery is critical for your use case, especially transactional messages. Order confirmations, password resets, and payment notifications should not depend on what strangers on the same IP are doing.

In every other situation, a shared IP at a reputable ESP works just as well—often better. Postmark and Mailgun actively monitor their pools, block violators fast, and sustain IP reputation at a level most small senders could not match on a dedicated IP.

The foundation of both reputations: a clean list

Whether you are on a shared IP or a dedicated one, invalid addresses are the primary threat. Each hard bounce tells the receiving provider: this sender does not know who they are mailing. Ten percent bounces in a single campaign can drop your domain from High to Medium in Google Postmaster Tools within a day. Recovery takes weeks.

Lists decay. Based on data from email validation runs, 20–25% of addresses go invalid within 12 months: people change jobs, abandon mailboxes, companies shut down. If you have not verified your list in six months, roughly a quarter of your sends are going nowhere and damaging your reputation on the way.

Validation before a send removes dead addresses before they cause damage. Upload your list, get results, remove risky addresses, send to the clean segment. Bounce rate drops below 1%, domain reputation improves, messages reach the inbox.

This applies equally to every infrastructure setup. Shared IP, dedicated IP, self-hosted SMTP—a clean list improves deliverability across the board, because your domain is the constant and its reputation reflects the quality of your sends.