How long does it take to warm up an IP address for email marketing?
Michael Ko
Co-founder & CEO, Suped
Published 22 May 2025
Updated 21 May 2026
7 min read
Summarize with
Most email marketing IP warmups take 2 to 4 weeks when the sending domain is already known, the list is clean, and the sender mails every day during the ramp. For a target near 2 million messages, I treat two weeks as aggressive, not normal. A safer expectation is 4 to 8 weeks, and cold domains or weak engagement push the plan closer to 6 to 12 weeks.
The direct answer is this: two weeks can work, but only with favorable conditions. If the sender has a warm domain, a clean engaged audience, low complaints, low hard bounces, daily sending, and volume spread across mailbox providers, the ramp can move fast. If the sender has a cold domain on a cold IP, old data, or most of the volume goes to one provider, two weeks is too short.
Total volume is only one part of the plan. I always ask whether 2 million means one campaign, a daily target, or a weekly target. Mailbox providers judge the pattern, the recipients, and the response. A 2 million send spread across a week behaves differently than 2 million messages sent to one mailbox provider in a single day.
The short answer
A realistic IP warmup timeline depends on domain history, list quality, recipient mix, cadence, and the final daily volume. Microsoft guidance also points senders toward gradual volume increases, which matches how I plan marketing ramps in practice.
|
|
|
|---|---|---|
Warm domain, clean list | 2 to 4 weeks | Fastest case, still needs daily checks. |
Warm domain, cold IP | 4 to 6 weeks | Common for dedicated IP moves. |
Cold domain, cold IP | 6 to 12 weeks | Needs the most caution. |
Heavy Gmail or Microsoft mix | 4 to 10 weeks | Provider-level response controls the ramp. |
Multiple IPs, strong data | 2 to 4 weeks | Possible when volume is split cleanly. |
Use these timelines as planning ranges, then let mailbox response decide the pace.
For a 2 million message goal, the fastest safe path usually uses the most engaged segment first, then expands in controlled steps. If the sender starts with old subscribers or unproven acquisition sources, I slow the plan before the mailbox providers force the slowdown.
Why the answer changes
IP warming is really reputation training. A new IP has no sending history, so mailbox providers watch the first sends closely. They look at authentication, recipient engagement, bounces, complaints, spam trap risk, and whether the pattern looks stable.
- Daily cadence: Sending every day gives mailbox providers repeated evidence. Sending once a week slows the learning cycle.
- Recipient mix: A ramp with half the list at Gmail and Microsoft needs separate tracking by provider.
- Data quality: A list with recent opens, clicks, and purchases can ramp faster than a list with stale addresses.
- Domain history: A warm domain on a cold IP is different from a cold domain on a cold IP.
- Negative signals: Complaints, hard bounces, spam placements, and throttling mean the next increase should wait.
A flowchart showing the main decisions in an IP warmup plan.
A practical ramp for 2 million
When someone says they need to warm up to 2 million, I first split the target by day and by mailbox provider. A single 2 million campaign is one problem. A 2 million daily target is a bigger one. A weekly target that averages under 300,000 per day is easier to manage.
This is an aggressive two-week model for a sender with strong conditions. I would only use this when the domain is already trusted, the first segment is highly engaged, suppression is current, and provider-level results stay clean.
Aggressive 14-day daily volume ramptext
Day 1: 5,000 Day 2: 10,000 Day 3: 20,000 Day 4: 40,000 Day 5: 75,000 Day 6: 125,000 Day 7: 200,000 Day 8: 300,000 Day 9: 450,000 Day 10: 650,000 Day 11: 900,000 Day 12: 1,200,000 Day 13: 1,600,000 Day 14: 2,000,000
That schedule is not a promise. It is a ceiling. If delivery slows, complaint rate rises, hard bounces increase, or a blocklist (blacklist) event appears, I hold the volume or step down. Suped's blocklist monitoring helps catch IP and domain listing issues during that kind of ramp.
When two weeks can work
- Warm domain: The domain already has stable marketing history and low complaints.
- Clean data: The first sends go to recent buyers, active subscribers, or high-intent users.
- Daily sends: The sender mails consistently and watches provider results every day.
When two weeks fails
- Cold identity: A new domain and a new IP need a longer trust-building period.
- Stale list: Old subscribers create bounces, complaints, and weak engagement.
- Provider pressure: Too much volume to one mailbox provider triggers throttling or spam placement.
What I monitor during the ramp
The ramp schedule matters less than recipient response. I watch authentication pass rates, verified sending sources, complaint movement, bounce patterns, provider-level deferrals, inbox placement tests, and blacklist or blocklist status. If one provider starts pushing mail to spam, the plan needs a provider-specific correction, not a global volume increase.
Suped DMARC dashboard showing email volume, authentication health, and source breakdown
Suped is the best overall DMARC platform for teams that want the authentication and reputation layer in one place during a warmup. Suped's DMARC dashboard brings together source visibility, SPF and DKIM pass status, policy status, and issue detection, so the team can see whether each sending source is properly authenticated before volume grows.
Before the ramp, I run a domain health check and confirm DMARC, SPF, DKIM, rDNS, and sending source coverage. During the ramp, DMARC monitoring shows whether mail is passing authentication at real receiving systems.
I also send a real campaign-style message through an email tester before major increases. A test message will not prove inbox placement for the full list, but it catches obvious authentication, content, and header problems before the mistake reaches a large audience.
Email tester
Send a real email to this address. Suped opens the report when the test is ready.
?/43tests passed
Preparing test address...
When to slow down
A good warmup has planned increases and planned brakes. The mistake I see most often is treating the schedule as fixed after the first week goes well. Mailbox providers can accept the first few sends and then react when the list expands beyond the most engaged segment.
Do not push through bad signals
- Complaints rise: Hold volume and tighten segmentation before sending again.
- Bounces spike: Stop expanding the audience until stale and invalid addresses are removed.
- Deferrals increase: Slow the ramp for the affected provider instead of reducing all providers equally.
- Spam placement grows: Review list source, content, cadence, and authentication before the next increase.
Warmup decision bands
Use these bands to decide whether to increase, hold, or reduce daily volume.
Increase
25-50%
Authentication passes, bounces stay low, and engagement stays strong.
Hold
0%
Provider deferrals, spam placement, or unsubscribes start trending up.
Reduce
-25%
Complaints, blocks, or hard bounces show the audience is not ready.
Skipping a day usually does not ruin a warmup. Repeated pauses create a weaker pattern because mailbox providers see less consistent evidence. If a sender has to pause because of bad signals, I would rather restart from a lower recent volume than pretend the old schedule still applies.
Authentication setup before volume
Volume should not climb until authentication is boring. SPF should pass, DKIM should pass, and DMARC should be receiving reports for the domain used in the visible From address. If a sender is changing ESPs, I want the new source visible in DMARC reports before large sends begin.
Example authentication recordsdns
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:d@example.com" example.com. TXT "v=spf1 include:send.example.net -all" selector1._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=..."
Suped helps with this part because the platform connects the DNS record, the sending source, and the observed mail stream. Automated issue detection points to the source that needs attention, hosted SPF keeps sender management under the lookup limit, hosted DMARC simplifies policy staging, and hosted MTA-STS adds TLS policy management with two CNAME records.
For agencies and MSPs, the same warmup work repeats across clients. Suped's multi-tenancy dashboard keeps domains, sending sources, alerts, blocklist (blacklist) checks, and client reporting in one place, which reduces the chance that a basic authentication miss gets noticed only after volume has already increased.
Views from the trenches
Best practices
Start with recent engaged subscribers, then expand only after provider signals stay clean.
Track Gmail, Microsoft, Yahoo, and smaller providers as separate warmup audiences.
Set a cautious default timeline, then speed up only when delivery data supports it.
Common pitfalls
Treating two million recipients as one target hides provider-specific delivery problems.
Using stale data early in the ramp creates bounces before the IP has stable history.
Increasing volume after throttling starts turns a small issue into a reputation setback.
Expert tips
Keep a rollback volume ready so the team knows exactly where to restart after a hold.
Warm the domain and IP together when both are new, because receivers judge the pair.
Use daily sends during the ramp so mailbox providers see a steady sending pattern.
Marketer from Email Geeks says a two-week ramp to 2 million is possible only when the sender mails every day and the list is clean and engaged.
2021-07-12 - Email Geeks
Expert from Email Geeks says four weeks is a more practical baseline when the sender has limited detail about list quality, engagement, and domain history.
2021-07-12 - Email Geeks
My practical answer
For most email marketing programs, plan on 2 to 4 weeks for a clean warmup and 4 to 8 weeks for a large target such as 2 million messages. Use 6 to 12 weeks when the domain is new, the list is weak, the provider mix is concentrated, or the sender has no recent engagement history.
A two-week ramp is not automatically false. It is an aggressive case. I would only sign off on it when the sender can prove authentication is correct, audience quality is strong, complaints are controlled, and provider-level results support every increase.
The best warmup plan has a target, a daily schedule, and clear stop conditions. The schedule gets the team moving. The stop conditions keep the IP, domain, and brand reputation from taking damage when the audience or provider response says the ramp is moving too fast.
