Domain reputation and IP reputation are the two scores mailbox providers use to decide inbox placement, and they are not interchangeable. IP reputation tracks the sending server address that hands your mail to the receiver. Domain reputation tracks the domain in your From address and the domains you authenticate with. In 2026, Gmail and most large receivers weigh domain reputation more heavily than IP reputation, which changes how you should plan a dedicated IP, a domain migration, or a warm-up.
Reads public DNS only. Nothing is stored unless you save the domain to an account.
The short version: your IP earns trust for the machine that connects, your domain earns trust for the brand behind the message. A clean IP cannot rescue a domain that sends spammy mail, and a strong domain can carry a brand-new IP through warm-up faster than it used to. The two only work together when your authentication aligns them, which is the part most senders get wrong.
What each reputation actually measures
IP reputation is scored at the connection layer. When your server opens an SMTP session, the receiver already knows the connecting IP and has history on it: how much mail it sends, spike patterns, spam-trap hits, complaint rates, and whether it appears on blocklists. This is a property of the machine, not your brand. If you send from a shared pool, you inherit the behavior of every other sender on that IP.
Domain reputation is scored at the identity layer. Receivers look at the organizational domain in your From: header and the domains you sign with, then attach a running history to them: engagement, complaint rates, spoofing attempts, and how consistently you authenticate. Because the domain travels with the message no matter which server sends it, this is the score that follows your brand.
Two signals feed domain reputation that have nothing to do with your IP. The first is the DKIM signing domain (the d= value in your signature). The second is the domain in the Return-Path used for SPF. When those match your visible From domain, you get DMARC alignment, and alignment is what lets a receiver credit the reputation to the right identity. If you want the mechanics, see SPF vs DKIM: what is the difference and DMARC relaxed vs strict alignment.
Domain reputation vs IP reputation: the comparison
| Dimension | IP reputation | Domain reputation |
|---|---|---|
| What it scores | The sending server address | The brand identity in From and DKIM |
| Portability | None. Change IP and you start over | Full. Follows you across any IP or ESP |
| Who you share it with | Everyone on a shared pool | Only you, unless subdomains delegate |
| Recovery time | Days to a few weeks with steady volume | Weeks to months once damaged |
| Main inputs | Volume, spikes, spam traps, complaints, blocklists | Engagement, complaints, spoofing, auth consistency |
| Reset by migration | Yes, moving IP resets it | No, moving IP does not touch it |
| 2026 Gmail weighting | Secondary | Primary |
The portability row is the one that matters most for planning. IP reputation is fragile but replaceable. If a dedicated IP gets burned, you can request a new one and warm it. Domain reputation is durable but hard to rebuild. A domain that has been used to send spam, or that has been actively spoofed, can carry that history for months, which is why protecting the domain matters more than protecting any single IP.
The 2026 reality: Gmail weighs the domain
Gmail's stated model is that domain reputation is the dominant factor and IP reputation is secondary, especially for senders on shared infrastructure. The reason is practical. Spammers rotate IPs constantly, so an address-based score is easy to game. A domain with real DNS records, consistent authentication, and a history of wanted mail is far harder to fake.
This has three consequences. First, a fresh dedicated IP no longer needs the punishing multi-week warm-up it once did, provided you send from an established domain that already has good standing. Second, moving to a new ESP does not reset your domain reputation, so a bad reputation follows you and a good one protects you. Third, subdomain strategy matters: sending marketing mail from news.yourbrand.com while transactional mail flows from your primary domain keeps a promotional complaint spike from bleeding into password resets and receipts.
You can watch domain reputation directly in Google Postmaster Tools, which reports a Bad/Low/Medium/High domain reputation band. Set it up before any migration so you have a baseline. See how to set up Google Postmaster Tools.
Shared vs dedicated IP: a decision guide
The right choice depends on volume and consistency, not prestige. A dedicated IP is not automatically better.
Choose a shared IP when
Your volume is under roughly 100,000 messages a month, or your sending is irregular. A dedicated IP needs steady volume to hold a warm reputation. Send too little and receivers treat each batch as an unknown, which hurts placement. On a reputable shared pool run by a good ESP, you borrow the aggregate reputation of many well-behaved senders and never have to warm anything. For most small and mid-size senders this is the correct answer.
Choose a dedicated IP when
You send high, consistent volume (well into the hundreds of thousands per month), you need full control over your sending reputation, or compliance requires isolation from other senders. The tradeoff is that you own every problem: a bad campaign hits only you, and you must sustain volume to keep the IP warm. Plan a gradual warm-up ramp regardless of the 2026 domain weighting, because receivers still throttle brand-new IPs. Our domain and IP warm-up guide covers the ramp schedule.
Either way, segment by mail stream. Do not mix bulk marketing and transactional mail on the same IP or the same subdomain, because a complaint spike on one poisons the other.
How authentication ties the two together
Reputation is worthless to a receiver that cannot trust who sent the message, and that is what authentication provides. SPF authorizes the sending IP for your Return-Path domain. DKIM cryptographically signs the message for your signing domain. DMARC then checks that at least one of those authenticated domains aligns with the visible From domain, and tells receivers what to do when neither does.
Here is why this connects IP and domain reputation. When SPF passes and DKIM aligns, the receiver can confidently assign the message's behavior to your domain's reputation history rather than treating it as anonymous. Without alignment, your carefully built domain reputation cannot be credited to the mail, and you fall back to weaker signals. A minimal enforcing DMARC record looks like this:
v=DMARC1; p=reject; rua=mailto:dmarc@yourbrand.com; adkim=s; aspf=s
The p=reject policy also protects domain reputation from the outside. Spoofers who blast spam using your From address damage your domain's standing directly, and an enforced DMARC policy shuts that down. If you are not there yet, walk through how to move DMARC from none to reject. If your mail authenticates but still lands in spam, the cause is almost always reputation or alignment rather than the IP itself, covered in why emails go to spam.
Protecting both scores in practice
Keep IP reputation healthy by sending consistent volume, honoring unsubscribes fast, suppressing hard bounces, and staying off spam traps by never mailing purchased or stale lists. Check your sending IPs and domain against major blocklists periodically with how to check if a domain is blacklisted.
Keep domain reputation healthy by authenticating every stream with aligned SPF and DKIM, enforcing DMARC, and separating mail types across subdomains. Watch the Postmaster Tools reputation band and treat any drop from High to Medium as an early warning to cut low-engagement segments before it worsens. Because the domain score is the one you cannot easily reset, it deserves the most protection.
Frequently asked questions
Does changing my IP reset my domain reputation?
No. Moving to a new IP or a new ESP resets only the IP reputation. Your domain reputation is attached to the domain in your From and DKIM signature, so it follows you regardless of which server sends the mail. A damaged domain reputation cannot be escaped by switching infrastructure.
Which matters more for Gmail inbox placement in 2026?
Domain reputation. Gmail treats the domain as the primary trust signal and the sending IP as secondary, particularly for senders on shared pools. This is why a well-established domain can carry a new dedicated IP through warm-up faster than it used to, and why a spoofed or abused domain hurts you no matter how clean your IP is.
Do I need a dedicated IP for good deliverability?
Not usually. If you send under about 100,000 messages a month or your volume is irregular, a reputable shared pool gives better and more stable placement because you inherit the aggregate reputation of well-behaved senders. Dedicated IPs pay off only at high, consistent volume where you want full control.
How long does it take to recover a damaged reputation?
IP reputation typically recovers in days to a few weeks with steady, clean sending and low complaints. Domain reputation is slower, often weeks to months, because it reflects a longer history of engagement and complaints. Fix the root cause first, then rebuild with engaged recipients only.