Email Reputation Systems Explained: How IP and Domain Reputation Determine Delivery

Every email you send carries invisible baggage: the reputation of the IP address it came from and the domain it claims to represent. Mailbox providers use this reputation to decide whether your message reaches the inbox, lands in spam, or gets rejected outright. Understanding how reputation works is fundamental to email deliverability.

What email reputation actually is

Email reputation is a score or classification that mailbox providers assign to sending IPs and domains based on their observed behavior over time. It is not a single number maintained by a central authority. Every major mailbox provider — Gmail, Microsoft, Yahoo, Apple — maintains its own reputation data, and they do not share it with each other.

Think of it as a credit score for email. A good reputation means your messages are trusted and delivered to the inbox. A bad reputation means they are filtered, deferred, or rejected. And like a credit score, reputation is easier to damage than to repair.

IP reputation vs domain reputation

The two primary reputation signals are tied to different identifiers, and they serve different purposes.

IP reputation

IP reputation is the older and more established signal. It tracks the sending behavior of a specific IP address: how much email it sends, how much of that email is spam, how many bounces it generates, and how recipients react to its messages.

Key characteristics of IP reputation:

• Directly observable — The receiving server sees the connecting IP in the SMTP transaction. No authentication is required to identify it.
• Affected by volume — IP reputation is volume-sensitive. Sudden spikes in sending from an IP with a low-volume history trigger suspicion.
• Shared or dedicated — On shared hosting or shared ESP IPs, your reputation is pooled with other senders on the same IP. On a dedicated IP, your reputation is entirely your own.
• Transferable with infrastructure — If you change your sending IP, you start fresh. The new IP has no reputation (which is not necessarily good — see "warming up" below).

Domain reputation

Domain reputation tracks the sending behavior associated with a domain, regardless of which IP address sends the email. It is identified through the From header domain, DKIM signing domain, and envelope sender domain.

Key characteristics of domain reputation:

• Follows the brand — Changing IPs does not reset domain reputation. If your domain has a bad reputation, switching to a new IP will not fix it.
• Authentication-dependent — Domain reputation requires SPF, DKIM, or DMARC to function, because the receiving server needs to verify that the domain is genuinely associated with the message.
• Increasingly dominant — Major providers, particularly Gmail, have publicly stated that domain reputation is weighted more heavily than IP reputation in their filtering decisions.
• Harder to game — Spammers can rotate through thousands of IPs, but domains are more expensive and harder to replace quickly, especially if they need to build authentication records.

How reputation is built

Reputation is built through consistent, clean sending over time. There is no shortcut. The signals that build positive reputation include:

• Low spam complaint rates — This is the strongest signal. Gmail considers anything above 0.1% concerning and treats 0.3% as a hard limit for bulk senders.
• Low bounce rates — Sending to invalid addresses indicates poor list hygiene, which correlates with spam behavior. Keep hard bounce rates below 2%.
• Consistent volume — Predictable sending patterns build trust. A domain that sends 10,000 emails every Tuesday is more trustworthy than one that sends 100,000 out of nowhere.
• High engagement — Recipients opening, reading, and replying to your messages is a positive signal. Gmail and Microsoft both track engagement metrics.
• Proper authentication — SPF, DKIM, and DMARC passing consistently demonstrates that you take email seriously and are who you claim to be.
• Clean content — Messages that do not trigger content filters contribute to positive reputation. Conversely, messages with spam-like content erode it.

How reputation is lost

Reputation can be damaged quickly, sometimes by a single incident:

• Spam complaints — Even a small spike in complaints can cause significant reputation damage. A bad campaign that generates 1% complaints can undo months of clean sending.
• Spam trap hits — Sending to spam trap addresses (addresses specifically created to catch spammers or old addresses repurposed as traps) is a major red flag. It indicates that you are sending to purchased lists or have not cleaned your list in years.
• Blocklist listings — Getting listed on a major DNSBL like Spamhaus signals to all receiving servers that your IP or domain is associated with spam.
• Sending to invalid addresses — High bounce rates suggest you are guessing addresses or using an outdated list.
• Sudden volume increases — Jumping from 1,000 to 100,000 emails in a day looks like a compromised account or a spam run, not legitimate growth.
• Content problems — Consistently sending messages that trigger content filters (even if they are not spam) degrades reputation over time.

Shared vs dedicated IPs

The choice between shared and dedicated IPs has significant reputation implications.

Shared IPs

On a shared IP (common with email service providers and shared hosting), your reputation is pooled with every other sender on that IP. If a neighbor sends spam, your deliverability suffers. Conversely, a shared IP with mostly good senders can benefit low-volume senders who would struggle to build reputation on their own.

Shared IPs make sense when:

• Your sending volume is low (under 50,000 per month)
• You use a reputable ESP that actively monitors its shared pools
• You do not have the resources to manage IP warming and dedicated reputation

Dedicated IPs

A dedicated IP gives you full control over your reputation. Nobody else's sending affects you, but you also bear full responsibility. You must warm up the IP, maintain consistent volume, and monitor reputation yourself.

Dedicated IPs make sense when:

• You send more than 100,000 emails per month consistently
• You need predictable deliverability that is not affected by other senders
• You have the operational capability to warm up and monitor the IP

Warming up a new IP

A new IP address has no reputation, and no reputation is not the same as good reputation. Mailbox providers are cautious about new IPs because spammers frequently rotate through fresh addresses. Warming up an IP means gradually increasing sending volume to build positive reputation.

A typical warm-up schedule for a new dedicated IP:

• Week 1: 500-1,000 emails per day, sent to your most engaged recipients
• Week 2: 2,000-5,000 per day
• Week 3: 5,000-15,000 per day
• Week 4: 15,000-50,000 per day
• Week 5+: Continue doubling until you reach your target volume

During warm-up, send only to your most engaged recipients. These users are most likely to open, click, and not report spam, which builds the strongest possible initial reputation. Sending your full list during warm-up, including unengaged recipients, risks generating complaints and bounces that torpedo the process.

Monitor deliverability closely during warm-up. If you see deferrals (4xx responses) or increased spam folder placement, slow down. The warm-up schedule is a guideline, not a rigid requirement.

Major reputation monitoring tools

Google Postmaster Tools

Google Postmaster Tools (postmaster.google.com) provides visibility into how Gmail views your sending reputation. It shows:

• Domain and IP reputation on a four-tier scale: High, Medium, Low, Bad
• Spam rate (percentage of messages marked as spam by recipients)
• Authentication pass rates for SPF, DKIM, and DMARC
• Delivery errors and their causes

You need to verify domain ownership to access the data. Google Postmaster Tools is the single most important reputation monitoring tool because Gmail is the largest mailbox provider.

Microsoft SNDS (Smart Network Data Services)

Microsoft SNDS (sendersupport.olc.protection.outlook.com/snds) provides similar data for Outlook.com, Hotmail, and Microsoft 365 recipients. It shows:

• Mail volume and spam complaint rates per IP
• Trap hit data (how many spam traps you hit)
• IP reputation status (green, yellow, red)

You need to verify ownership of the IP address range to access SNDS data. This requires being the registered owner or having authorization from the IP block's owner.

Sender Score (senderscore.org)

Sender Score, operated by Validity (formerly Return Path), provides a 0-100 score for your sending IP based on data collected from a network of mailbox providers and ISPs. A score above 80 is generally considered good; below 70 indicates reputation problems.

Sender Score is a useful third-party perspective, but keep in mind that it does not directly influence delivery decisions at any mailbox provider. Gmail and Microsoft use their own internal reputation data, not Sender Score.

Cisco Talos Intelligence (talosintelligence.com)

Talos Intelligence, operated by Cisco, provides IP and domain reputation data from Cisco's security network. It classifies reputation as Good, Neutral, or Poor and provides details on email volume, spam percentage, and blocklist status. Talos data feeds into Cisco email security products, which are widely deployed in enterprise environments.

How reputation affects delivery at different providers

Each major mailbox provider uses reputation differently:

• Gmail — Heavily weights domain reputation. Uses a combination of authentication, engagement, and complaint data. Provides the most detailed sender tools through Postmaster Tools.
• Microsoft (Outlook/365) — Uses both IP and domain reputation. Relies more on IP reputation than Gmail does. Microsoft's SmartScreen filter combines reputation with content analysis. Tends to be more aggressive with deferrals (temporary failures) for new or low-reputation senders.
• Yahoo/AOL — Uses CFL (Complaint Feedback Loop) data heavily. Maintaining a low complaint rate is especially important for Yahoo deliverability.
• Apple iCloud Mail — Less transparent about its reputation system. Uses standard authentication checks and appears to weight both IP and domain reputation. Apple's Mail Privacy Protection makes engagement tracking unreliable for Apple Mail users.

Monitoring your reputation: a practical checklist

Regularly monitoring reputation helps you catch problems before they affect deliverability:

1. Weekly: Check Google Postmaster Tools for domain reputation and spam rate
2. Weekly: Review Microsoft SNDS for IP reputation status
3. Monthly: Check Sender Score for your sending IPs
4. Ongoing: Monitor bounce rates and spam complaint rates in your ESP dashboard
5. As needed: Check DNSBL listings using MXToolbox or MultiRBL when you notice delivery issues

Set up alerts for significant changes. A sudden drop in Gmail domain reputation from High to Medium warrants immediate investigation. For more on keeping your email deliverable, see The Email Deliverability Guide for Small Senders.

The role of TLD reputation

Beyond individual domain reputation, some top-level domains (TLDs) carry their own reputation baggage. Certain TLDs that offer cheap or free registrations have become associated with spam and abuse. Sending from a domain under one of these TLDs can start you at a reputation disadvantage, regardless of your own sending behavior. For more on this topic, see TLD Reputation: Why .xyz and Other Top Domains Get Blocked.

How Cleanbox factors in reputation

Cleanbox incorporates sender reputation data into its spam scoring pipeline. When an email arrives, the sending IP and domain are checked against multiple reputation sources alongside DNSBL lookups, authentication results, and content analysis. Messages from senders with poor IP or domain reputation receive higher spam scores, while established senders with clean histories benefit from lower scores. This reputation-aware approach helps reduce false positives for legitimate senders while catching spam from sources that have not yet appeared on blocklists but have already accumulated negative reputation signals.