--- title: 'Enterprise Brand Email Reputation: Why the IP is Only Part of the Equation' url: 'https://omnivery.com/blog/enterprise-brand-email-reputation-ip-is-only-part' markdown: 'https://omnivery.com/blog/enterprise-brand-email-reputation-ip-is-only-part.md' lang: en date: '2026-10-15' description: "Shared IPs versus Dedicated IPs? It's a big question to consider and its answer is factored into the design of an email program, the selection of an ESP partner, and architecture of a send system. There are benefits for both and there are also risks for both. Omnivery does a great job in comparing …" taxonomy: category: - Deliverability tag: - 'Shared IPs' - 'Domain Reputation' --- # Enterprise Brand Email Reputation: Why the IP is Only Part of the Equation Shared IPs versus Dedicated IPs? It's a big question to consider and its answer is factored into the design of an email program, the selection of an ESP partner, and architecture of a send system. There are benefits for both and there are also risks for both. Omnivery does a great job in comparing the two in their article, [Dedicated vs Shared IPs](https://omnivery.com/resources/guides/dedicated-vs-shared-ip), detailing the considerations to weigh when making your decision, also highlighting some of the overlooked reasons that should get factored in, but often don't. I want to take this a little further today and explore reputation, how its focus has changed, and how it should be factored in when making decisions around dedicated IPs and shared IPs. ## The Reputation Evolution Historically, dedicated IPs were often the go-to solution in the U.S., particularly for larger senders, while shared IP environments have been far more common in Europe, where IP space has traditionally been less abundant. In the U.S., dedicated IPs became an easy way to isolate reputation from a potentially messy sender base, often leading to the advice: "Go dedicated because the risk of others impacting your IP reputation is too great." Advice even I used to give. But email has evolved. Reputation has evolved. What weighs into reputation and when and how much has evolved. Omnivery is very much a reflection of this evolution. Omnivery's confidence in shared IPs comes from nearly [20 years of experience operating and managing shared environments at scale](https://omnivery.com/about). They've long understood that sender reputation is about far more than the IP address alone. Dedicated IPs are an easy way for an ESP to put the keys in the sender's hand and say, "Your destiny is now in your hands. Go forth and send!" Shared IPs take a lot more work from the ESP side to make sure both the IP network and the IP neighborhoods (shared IP pools) are cared for. Not all ESPs want to invest in that model to ensure all IPs are protected. Omnivery very much does. And they do this through a vigorous vetting process, very much a "Know Your Customer" model. Sharing the same approach that financial institutions, fintech companies, regulated businesses and more apply. So why does a Shared IP model for all senders, regardless of size, work so nicely in today's email space, whereas before it could be considered too risky? The truth is, the Shared IP model has always worked even for large senders when the network is kept clean. The risk was never inherently sharing an IP; it was sharing an IP with poorly vetted or poorly managed senders. In addition, domain reputation has picked up steam and is flying by, taking us all with it. The use of domain reputation has been a slow, or what feels like slow, adoption considering the [DKIM authentication RFC](https://www.rfc-editor.org/info/rfc6376/), using the domain as the responsible party for messages, was published nearly two decades ago. The molasses-like movement isn't because domain reputation wasn't seen or important on the receiving side, they've been building their filtering around it for just as long if not longer as DKIM has been around. I've talked to many providers about how IP factors into decisioning, the responses vary "from its importance depends on where in the flow its reviewed" to "its more of an afterthought." However, one exception is when an IP is extremely bad and complaints are not being addressed. In that scenario, the IP will likely get blocked at the gate. Regardless, they all agree, the domain is the present and future. I see the lag as being more on the sender side and in the industry's understanding of what actually drives reputation. IP reputation was often treated as a much larger factor than it really was, while domain identity and branded DKIM remained on the back burner. With IP reputation being such a large factor in an email program's reputational success, a number of ESPs designed their operational and sales model around it, some for legitimate reasons truly believing in separating mail on all levels, and some as a way to offer a premium service. That began to change as mailbox providers put greater emphasis on domain identity and authentication. The real turning point came in October 2023, when [Gmail](https://blog.google/products-and-platforms/products/gmail/gmail-security-authentication-spam-protection/) and [Yahoo](https://blog.postmaster.yahooinc.com/post/730172167494483968/more-secure-less-spam) announced new sender requirements that made domain authentication no longer simply a best practice, but a requirement for many senders. For a lot of organizations, that forced a shift in thinking: reputation isn't just about the IP you're sending from, it's increasingly tied to who you are as a sender. ## How Domain and IP Reputation Differ For years, IP reputation was the gold standard. Domain reputation changed that because it gives mailbox providers a more accurate and persistent way to identify and evaluate the actual sender behind the email. Domains can be tied to the actual sender as well as its ownership and all associated identifiers. It's why major mailbox providers like [Gmail](https://support.google.com/mail/answer/81126?hl=en), [Yahoo](https://senders.yahooinc.com/best-practices/), [Microsoft](https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/strengthening-email-ecosystem-outlook%E2%80%99s-new-requirements-for-high%E2%80%90volume-senders/4399730), [Apple](https://support.apple.com/en-us/102322), [Orange](https://postmaster.orange.fr/index.html), [GMX](https://postmaster.gmx.com/en/requirements-and-recommendations), [BT Internet](https://www.bt.com/help/email/bt-email---best-practices-for-postmasters-and-senders-of-email), and more have designed domain attestation into their sender compliance requirements. I've been thinking about how to better explain why IP weight in filtering has taken a backseat and why domains are so important and factor more into performance. Why a sender's decisions should be more about caring for the domain than what IP setup one should use. Domains are often created as a carbon copy or a near carbon copy of a brand. A brand's digital identity, their digital foundation. A foundation that isn't changed lightly. Most often a domain's owner is different from the owner of the IPs the website is hosted on or the emails are sent with. A user doesn't memorize an IP to visit the brand's site (and nowadays hosting keeps many domains tied to one IP and then does the routing from there) or to check which system sent an email. Instead, they use and look for the domain. The domain is what is trusted as the representation of the brand they are communicating with. Legitimate brands have a vested interest in keeping that domain consistent because their customers are vested in that same domain. In the email world, IPs are tied to the sending system, but a domain can float across send systems over time or at the same time based on the need. I once had a client using ELEVEN different services at the same time. The domain anchors the floating nature of a domain across email infrastructures to understand if the different services are all supporting legitimate traffic or if they are all carrying something that is trying to hide among the volumes. Consistency is not only important for branding and customer identification, but it is also a factor in anti-abuse detection as well as reputation building. IPs are tied to infrastructures, which can be changed by the infrastructure provider or because a new provider is employed making IP identity more dynamic. Domains are everlasting making their identity more static. ## Domain for Reputation, IPs for Technical and Policy Decisions Building positive reputation and trust with your domain creates a more lasting reputation that can better endure its environment. Should you take dedicated versus shared IP infrastructure into consideration? Absolutely. But it should be for the right reasons. Reasons that factor into company policies, sending volumes, throughput, stream category (marketing versus transactional), volume consistency, and more. If you are with the right provider, one that actively protects and manages its network, IP reputation should not be what pushes you away from a shared environment. The bigger consideration is how that provider helps you build, protect, and manage the domain reputation that ultimately represents your brand as a sender. --- ## Navigation - Parent: [Mastering the Inbox](https://omnivery.com/blog.md) - Next: [Gmail's Click Spike Is the New Normal](https://omnivery.com/blog/gmail-click-spike-new-normal.md)