IP Warmup vs Domain Warmup: What's the Difference and When You Need Which
The Confusion That Costs Senders Months of Deliverability
Most email warmup guides treat “warmup” as a single concept. Warm up your email, they say, as though there is one process that handles everything. There is not. There are two distinct reputation systems, and confusing them leads to wasted effort, poor deliverability, and months of inbox placement problems.
IP reputation and domain reputation are tracked independently by inbox providers. They are warmed differently, they degrade differently, and the scenarios that trigger each type of warmup are different.
Understanding which one you need — and which one you can skip — saves weeks of unnecessary warmup time. Getting it wrong means either warming up something that does not need warming (wasting time) or failing to warm up something that does (landing in spam).
How IP Reputation Works
Every email is sent from a specific IP address — a numerical identifier for the server that physically transmits the message. Inbox providers maintain reputation scores for individual IP addresses based on the sending behavior observed from that IP.
What Builds IP Reputation
- Volume consistency — Steady, predictable sending patterns from the IP
- Low bounce rates — Few invalid addresses, indicating a clean sender
- Low complaint rates — Recipients are not marking messages from this IP as spam
- Positive engagement — Opens, clicks, and replies from recipients
What Damages IP Reputation
- Sudden volume spikes — Going from 0 to 50,000 emails is a classic spam signal
- High bounce rates — Indicates purchased or scraped lists
- Spam complaints — Direct negative signal from recipients
- Spam trap hits — Sending to addresses that exist only to catch spammers
Shared IPs vs Dedicated IPs
Shared IPs are used by your ESP to send email for many customers simultaneously. Mailchimp, Klaviyo, GetResponse — they all maintain pools of shared IP addresses. Your emails go out alongside thousands of other senders’ messages. The IP’s reputation is a collective score influenced by everyone sending from it.
Dedicated IPs are assigned exclusively to your account. Only your emails are sent from that IP. The reputation is entirely yours — for better or worse.
| Factor | Shared IP | Dedicated IP |
|---|---|---|
| Reputation source | Pooled from all senders | Your sending behavior only |
| Warmup required | No (ESP maintains it) | Yes (starts at zero) |
| Risk from others | Bad senders on the pool can affect you | None — your reputation is isolated |
| Risk from you | Limited — your volume is a small fraction | Full — every mistake hurts only you |
| Best for | Senders under 50K/month | Senders over 100K/month |
| Cost | Included in ESP pricing | Additional fee ($20-100/month) |
How Domain Reputation Works
Domain reputation is tied to the domain in your From address — the part after the @ sign. When you send from newsletter@emailcloud.com, inbox providers track the reputation of emailcloud.com independently of whatever IP address delivered the message.
Why Domain Reputation Now Matters More Than IP
For most of email history, IP reputation was king. Inbox providers could reliably identify senders by their IP address because most senders operated their own mail servers on fixed IPs.
That changed with cloud infrastructure and shared hosting. Today, a single IP address might send email for hundreds of different companies. IP addresses are recycled, reassigned, and shared constantly. They became a less reliable signal for identifying individual senders.
Gmail led the shift toward domain-based reputation around 2015-2016, and other major providers followed. Today, domain reputation is the primary signal for Gmail, and a significant factor for Outlook, Yahoo, and Apple Mail.
This does not mean IP reputation is irrelevant. It still matters, especially for dedicated IP senders. But for the majority of email senders using shared ESPs, domain reputation is what determines whether your email reaches the inbox.
What Builds Domain Reputation
- Consistent sending history — Regular emails from the domain over weeks and months
- Strong authentication — SPF, DKIM, and DMARC all passing. Check yours with our SPF Checker.
- Recipient engagement — Opens, clicks, replies, and forwards from recipients
- Low complaint rates — Few people marking your emails as spam
- List quality — Sending to valid, active email addresses
What Damages Domain Reputation
- Spam complaints above 0.1% — Gmail’s published threshold for problems
- High bounce rates — Indicates poor list hygiene or purchased lists
- Spam trap hits — Sending to recycled or pristine spam traps
- Sudden volume changes — Especially from dormant domains that suddenly start blasting
- Content that triggers filters — Spammy subject lines, deceptive content, excessive links
When You Need IP Warmup
You need IP warmup in these specific situations:
1. You Got a Dedicated IP From Your ESP
If you upgrade to a dedicated IP on SendGrid, Mailgun, Amazon SES, Postmark, or any other ESP, that IP has zero reputation. No one has ever sent email from it (or worse, someone did and it was not great). You must build reputation from scratch.
How to tell: Your ESP explicitly assigns you a dedicated IP address. They will typically tell you it needs warmup and may offer automated warmup tools.
2. You Are Self-Hosting Email Infrastructure
If you are running your own mail server or using a service like Amazon SES or Postal on your own infrastructure, you are operating on IP addresses that have no established email sending reputation.
How to tell: You control the server and know the IP addresses your mail is sent from.
3. Your Dedicated IP Was Idle for 30+ Days
IP reputation decays. If your dedicated IP has not sent email in a month or more, inbox providers may have cleared its reputation data. You need to re-warm, though the process is faster than starting from zero because the IP has historical sending data.
How to tell: Check your sending logs. If the IP has been inactive, plan for 1-2 weeks of re-warmup.
When You Need Domain Warmup
You need domain warmup in these situations:
1. Brand New Domain
A domain registered recently with no email sending history has zero reputation. Inbox providers have never seen it and default to suspicion.
How to tell: You just registered the domain, or it has never been used for email.
2. Domain Dormant for 6+ Months
Domain reputation erodes faster than most people expect. A domain that has not sent email in 6 months has effectively lost its reputation with most inbox providers. You are not starting from a negative position — you are starting from nothing.
How to tell: Check Google Postmaster Tools. If it shows no data for your domain, reputation has lapsed.
3. Domain Previously Used for Spam
If you acquired a domain that was previously used for spam or bulk unsolicited email, it may carry negative reputation. This is worse than zero reputation — you are starting from a hole.
How to tell: Run a blacklist check. Check Google Postmaster Tools for a “Bad” reputation rating. Search the domain on major blacklist databases.
4. Switching Sending Infrastructure Entirely
If you change everything — new ESP, new IPs, new authentication records — your domain needs to re-establish trust in the context of the new infrastructure, even if the domain itself has history.
How to tell: You are migrating to a new platform and none of the previous sending infrastructure carries over.
When You Need Both (The Hardest Scenario)
The most challenging warmup scenario: a new domain on a new dedicated IP. Neither signal has any reputation. You are a completely unknown entity to every inbox provider.
This happens when:
- Launching a new brand with its own dedicated sending infrastructure
- Starting a cold email operation on a fresh domain with a dedicated IP
- Enterprise organizations setting up new business units with isolated email infrastructure
Timeline: 6-8 weeks minimum. Do not rush this.
IP Warmup Schedule (Domain Already Has Reputation)
If your domain has established reputation but you are on a new dedicated IP, you can ramp faster because inbox providers recognize the domain.
| Week | Day | Daily Volume | Notes |
|---|---|---|---|
| 1 | 1-2 | 500 | Most engaged subscribers (30-day openers) |
| 1 | 3-5 | 1,000 | Expand to 60-day openers |
| 2 | 6-10 | 2,500 | Expand to 90-day openers |
| 3 | 11-15 | 5,000 | Full engaged list |
| 4 | 16-20 | 10,000+ | Approaching target volume |
Key monitoring points: Check bounce rates and Google Postmaster Tools daily. The IP should show “Neutral” or “Medium” reputation by end of Week 1. If it still shows “Low” after 10 days, slow down.
Why this is faster than domain warmup: The domain acts as a trust signal. Gmail and other providers can see that the domain has a positive sending history, even though the IP is new. The IP inherits some credibility from the domain’s reputation.
Domain Warmup Schedule (IP Already Has Reputation or Using Shared)
If you are on a shared IP (your ESP’s pool) or an established dedicated IP, but the domain is new, focus on building engagement signals.
| Week | Day | Daily Volume | Notes |
|---|---|---|---|
| 1 | 1-3 | 20-50 | Internal team, friends, colleagues. Ask for replies. |
| 1 | 4-7 | 50-100 | Most engaged subscribers only |
| 2 | 8-14 | 100-250 | Expand to recent subscribers |
| 3 | 15-21 | 250-1,000 | Expand to 60-day engagers |
| 4 | 22-28 | 1,000-2,500 | Approaching target volume |
| 5-6 | 29-42 | 2,500-5,000+ | Full volume, ongoing monitoring |
Key monitoring points: Domain reputation in Google Postmaster Tools is your primary metric. It should reach “Medium” by end of Week 2 and “High” by end of Week 4. Complaint rate must stay below 0.1% throughout.
Why this is slower than IP warmup: A new domain has no trust signals at all. The IP’s reputation helps somewhat (especially on a shared pool with strong collective reputation), but inbox providers still need to see consistent positive behavior specifically from your domain.
Combined Warmup Schedule (New Domain + New Dedicated IP)
This is the slowest and most conservative schedule. Neither the domain nor the IP has reputation. Every engagement signal must be earned from zero.
| Week | Day | Daily Volume | Focus | Notes |
|---|---|---|---|---|
| 1 | 1-3 | 20 | Seed engagement | Internal team, friends. Every email must get opened and replied to. |
| 1 | 4-7 | 50 | Personal sends | Continue personal emails, sign up for newsletters with the domain |
| 2 | 8-10 | 100 | Most engaged only | Your 30-day openers/clickers if they exist, or warmup service peers |
| 2 | 11-14 | 200 | Careful expansion | Watch bounce rate and complaints closely |
| 3 | 15-17 | 400 | Monitor metrics | Check Google Postmaster — should show some data by now |
| 3 | 18-21 | 750 | Steady ramp | Never more than 2x previous step |
| 4 | 22-25 | 1,500 | Building confidence | Domain reputation should be Medium |
| 4 | 26-28 | 2,500 | Approaching midpoint | IP reputation should stabilize |
| 5 | 29-35 | 5,000 | Higher volume | Expand to less engaged segments |
| 6-8 | 36-56 | 10,000+ | Target volume | Continue monitoring weekly |
Critical rule for combined warmup: If any metric goes red (bounce rate above 3%, complaint rate above 0.1%, reputation drops to “Low”), immediately cut volume by 50% and hold for 5 days. In a combined warmup scenario, recovery from a reputation hit takes longer because you do not have either reputation pillar to fall back on.
How Major ESPs Handle Warmup
Not all ESPs handle warmup the same way. Understanding your platform’s approach determines how much of the warmup burden falls on you.
Mailchimp — Fully Managed Shared Pool
Mailchimp manages a large pool of shared IP addresses and automatically distributes your sends across them. There is no IP warmup for Mailchimp users — the pool’s reputation is already established. Domain warmup still applies for new domains.
What you need to worry about: Domain warmup only. Mailchimp’s shared infrastructure handles IP reputation.
SendGrid — IP Warmup Mode
SendGrid offers dedicated IPs with an automated IP warmup feature. When enabled, SendGrid automatically throttles your sending volume on the new IP, gradually increasing over weeks. Sends that exceed the warmup limit are routed through SendGrid’s shared IP pool as overflow.
What you need to worry about: Enable IP warmup mode when you get a new dedicated IP. Handle domain warmup separately through your sending strategy.
Amazon SES — Sending Quota System
Amazon SES starts new accounts with a low sending quota (typically 200 emails/day) and increases it automatically as you demonstrate good sending behavior. This is effectively forced IP warmup — SES will not let you send more than your quota regardless of your intent.
What you need to worry about: SES handles the volume throttling. Focus on domain warmup and engagement quality. Request quota increases through the SES console as you scale.
Postmark — Pre-Vetted, No Warmup Needed
Postmark takes a unique approach: they vet every sender before allowing them on the platform and maintain extremely high deliverability standards across their infrastructure. New senders do not need IP warmup because Postmark’s shared pool reputation is exceptionally strong.
What you need to worry about: Domain warmup for new domains. Postmark’s infrastructure reputation will help, but your domain still needs to build its own history.
Klaviyo — Shared Pool With Optional Dedicated
Klaviyo uses shared IPs by default and offers dedicated IPs for high-volume senders. On shared IPs, no IP warmup is needed. On dedicated IPs, Klaviyo provides warmup guidance but does not automate the throttling.
What you need to worry about: If on shared IPs, domain warmup only. If on dedicated IPs, both domain and IP warmup.
The Dedicated IP Trap
This is worth emphasizing because we see it constantly: a dedicated IP with no warmup performs worse than a shared IP.
Here is the scenario. A sender is on a shared IP pool through their ESP. Deliverability is fine — 95% inbox placement. They hear that dedicated IPs give “better control” and upgrade. Day one on the dedicated IP, they send their normal volume — 20,000 emails. The IP has zero reputation. Inbox providers see 20,000 emails from an unknown IP and route most of them to spam.
The sender just paid extra money for worse deliverability.
When dedicated IPs make sense:
- You send 100,000+ emails per month consistently
- You have the expertise (or team) to manage IP reputation
- You have a clean, engaged list with strong metrics
- You are willing to invest 4-6 weeks in warmup before seeing normal deliverability
When dedicated IPs do NOT make sense:
- You send fewer than 50,000 emails per month
- You are a new sender with limited email marketing experience
- You have irregular sending patterns (heavy one week, nothing the next)
- You want to “set it and forget it”
The shared IP pool at a reputable ESP has years of built-in reputation. Your brand new dedicated IP has nothing. For most senders, the pooled reputation is more valuable than the control a dedicated IP provides.
Choosing Your Warmup Strategy: A Decision Tree
Use this to determine which warmup process you need:
Question 1: Are you on a shared IP or dedicated IP?
- Shared IP → Skip IP warmup. Your ESP handles it. Go to Question 2.
- Dedicated IP → You need IP warmup. Go to Question 2.
Question 2: Is your domain new, dormant (6+ months), or established?
- New or dormant → You need domain warmup.
- Established (actively sending in the last 3 months) → Skip domain warmup.
Results:
- Shared IP + established domain = No warmup needed (just monitor metrics after ESP migration)
- Shared IP + new/dormant domain = Domain warmup only (4-6 weeks)
- Dedicated IP + established domain = IP warmup only (2-4 weeks)
- Dedicated IP + new/dormant domain = Combined warmup (6-8 weeks)
For a custom warmup schedule tailored to your specific situation, use our Warmup Calculator. It accounts for domain age, current volume, target volume, and sending infrastructure to generate a day-by-day plan.
Monitoring Both Reputations
During warmup, monitor IP and domain reputation separately:
| What to Monitor | Tool | Frequency | Target |
|---|---|---|---|
| Domain reputation | Google Postmaster Tools | Daily during warmup | Medium by Week 2, High by Week 4 |
| IP reputation | Google Postmaster Tools | Daily during warmup | No “Bad” or “Low” rating |
| IP blacklists | Blacklist Checker | Every 3 days during warmup | Clean on all major lists |
| Domain blacklists | Blacklist Checker | Every 3 days during warmup | Clean on all major lists |
| Spam complaint rate | ESP dashboard | Daily | Below 0.1% |
| Bounce rate | ESP dashboard | Daily | Below 2% |
| Authentication pass rate | Google Postmaster Tools | Weekly | SPF, DKIM, DMARC all 95%+ |
If your domain reputation is healthy but IP reputation drops, the problem is IP-specific — you may be sending too much volume too fast for the IP’s warmup stage. Reduce volume and hold.
If your IP reputation is fine but domain reputation drops, the problem is content or engagement — your emails may be triggering spam filters or recipients may be complaining. Audit your content, check subject lines with our Spam Word Checker, and tighten your audience segments.
If both drop simultaneously, you have a fundamental problem — stop sending marketing email, investigate the root cause, and do not resume until you have identified and fixed the issue. Common causes include sending to a bad list, an authentication misconfiguration, or landing on a major blacklist.
Email reputation is a system with two interacting components. Understanding which component needs attention — and when — is the difference between a 4-week warmup that reaches the inbox and a 4-month struggle with the spam folder.
Frequently Asked Questions
Do I need a dedicated IP for email marketing?
Most senders do not. If you send fewer than 50,000 emails per month, a shared IP through your ESP is almost always better. The ESP's pooled reputation (built by thousands of senders) is stronger than your nonexistent dedicated IP reputation. Dedicated IPs only make sense at high volume (100K+/month) where you want full control over your sending reputation.
What is the difference between IP reputation and domain reputation?
IP reputation is tied to the specific server address sending your email. Domain reputation is tied to your domain name (the part after the @ sign). ISPs track both. Historically, IP reputation dominated, but modern filtering (especially Gmail) now weights domain reputation more heavily because shared hosting and cloud infrastructure make IP addresses less reliable as identity signals.
Can I warm up an IP and domain at the same time?
Yes, but it is the hardest warmup scenario. Neither your IP nor your domain has established trust, so you must ramp very slowly. Expect 6-8 weeks minimum. Start at 50-100 emails per day and increase by no more than 50% every 3-4 days. The combined warmup schedule in this guide provides a day-by-day plan.
What happens if I switch ESPs but keep the same domain?
Your domain reputation carries over, but the sending IP changes. This means you need an IP-level warmup (or the new ESP's shared pool needs to build trust for your domain). The warmup is faster than starting from scratch — typically 2-3 weeks — because inbox providers still recognize your domain as a legitimate sender.
Stay ahead of the inbox
Weekly tips on deliverability, automation, and growing your list. No spam, ever.
No spam. Unsubscribe any time. We respect your inbox.