How long does it take to warm up a sending domain?

About four weeks to reach 50,000 messages a day, starting from a few hundred and roughly doubling every two to three days. The timeline is driven by your engagement rather than the calendar — a list of highly engaged recipients warms faster, and a list that produces deferrals or complaints extends it however long it takes.

Do I need to warm up if I use a shared IP?

Yes, because you are warming the domain rather than the IP. On a shared pool your provider manages IP reputation across all their customers, but domain reputation is yours alone, and a brand-new domain sending large volume is treated with suspicion no matter how good the IP is.

What happens if I skip warm-up and send to my whole list?

Typically deferrals and throttling within the first few thousand messages, then spam-folder placement, then — if complaints cross 0.3% — outright rejections. Recovery takes two to six weeks of careful low-volume sending, which is considerably longer than the four weeks warming up would have taken.

Should I warm up a subdomain separately?

Yes. A subdomain inherits some reputation from the parent domain but accumulates its own, so a new marketing subdomain needs its own ramp. That separation is usually worth it: it means a poorly received campaign cannot damage delivery of receipts and password resets sent from the primary domain.

Can I use a warm-up service that sends to seed inboxes?

It is not advisable. These services generate artificial opens and replies between accounts they control, which is engagement manipulation rather than reputation building, and providers have become good at recognising the pattern. Real recipients opening real mail is the only signal that holds up.

Deliverability

How to warm up a sending domain, with an actual schedule

Updated 3 September 2026 · 6 min read · SendKernel

Warming up a sending domain means increasing volume gradually while engagement stays high, so receiving servers build a reputation for you before you need one. A workable schedule starts at a few hundred messages a day to your most engaged recipients and roughly doubles every two to three days, reaching 50,000 a day in about four weeks. The rule that matters more than the numbers: never increase volume on a day when bounces are above 2% or complaints are above 0.1%.

The short version

Warm up the domain, not just the IP. Domain reputation now carries more weight and follows you across providers.
Engagement drives the schedule. Send to your most active recipients first and widen outward.
Double every two to three days, and hold whenever the numbers say hold.
A domain that stops sending goes cold in weeks, so a long gap means warming up again.

What warming up actually does

A receiving server decides what to do with your mail partly on what it already knows about you. A domain with no history is not neutral — it is unknown, and unknown senders that suddenly emit large volumes look like compromised accounts, because that is the most common reason it happens. Warming up replaces that absence of history with evidence: mail from this domain gets opened, rarely bounces, and is almost never reported.

The emphasis has shifted over the last few years from IP reputation to domain reputation. On a shared IP pool — which is what most senders are on and should be on — the IP's reputation is managed by your provider across all their customers, while your domain's reputation is entirely yours and travels with you if you switch platforms. That is the asset you are building.

Before day one

SPF, DKIM, and DMARC published and aligned with your From domain. Warming up a domain that fails authentication accomplishes nothing.
Your list segmented by engagement — who opened or clicked in the last 30 days, 90 days, and beyond. This segmentation is the schedule.
Suppression already applied: past unsubscribes, hard bounces, and complaints excluded before the first send.
A reason for people to open. Warm-up traffic should be your best content, not filler sent to hit a number.

A four-week schedule

Volumes below are per day, and assume you have enough engaged recipients to fill them. If you do not, that is fine — send to the engaged recipients you have and extend the timeline rather than reaching further down the list to hit a target.

Days	Daily volume	Send to	Hold if
1–3	200–500	Opened in the last 30 days	Any bounce over 2% or any complaint at all
4–7	1,000–2,000	Opened in the last 30 days	Bounces over 2%, complaints over 0.1%
8–14	5,000–10,000	Opened in the last 90 days	Bounces over 2%, complaints over 0.1%
15–21	15,000–25,000	All subscribed and not obviously stale	Bounces over 2%, complaints over 0.1%
22–28	35,000–50,000	Full list	Any adverse trend, even inside the thresholds

Cross the 5,000-a-day line and the Gmail, Yahoo, and Microsoft bulk sender requirements now apply to you — authentication, one-click unsubscribe, and the 0.3% complaint ceiling. That happens around day eight on this schedule.

Two adjustments people get wrong. Consistency beats speed: sending every day at a steady volume warms faster than alternating large bursts with silence, even at the same weekly total. And holding is not failure — a day spent at the same volume because complaints ticked up is far cheaper than pushing through and spending three weeks recovering.

What to watch, and what it means

Signal	Reading	Response
Bounces under 2%	List is clean	Continue the schedule
Bounces 2–5%	Stale or unverified addresses	Hold volume, clean the list before widening
Bounces over 5%	The list is not consent-based	Stop. Widening from here damages the domain
Complaints under 0.1%	Healthy	Continue
Complaints 0.1–0.3%	Reaching people who do not want this	Return to your most engaged segment for several sends
Complaints over 0.3%	Rejections begin	Stop entirely and restart warm-up after two to four clean weeks
Deferrals rising	A provider is throttling you deliberately	Hold at current volume — you are moving faster than they will accept

Deferrals are the most useful early signal and the one most often ignored. A 4xx temporary failure from a large provider is not an error, it is a rate limit — the receiving server is telling you your volume is growing faster than its trust in you. Retries will get through; increasing volume the next day will not.

Warm-up problem or list problem?

These need opposite responses, and confusing them wastes weeks. A warm-up problem shows up as deferrals and throttling that ease when you hold volume, with bounce and complaint rates staying low. A list problem shows up as bounces above 2% or complaints above 0.1% from the very first send, and it does not improve with time — going slower just spreads the same damage over more days.

The test is your first 500 messages to your most engaged recipients. If those bounce or generate complaints, no schedule will save you and the list is the thing to fix. If they deliver cleanly and problems only appear as volume grows, you are warming up too fast and the fix is patience.

Staying warm

Reputation decays. A domain that sends nothing for a month or two is effectively cold again and needs a shortened ramp before its next large campaign.
Keep a steady baseline rather than sending only around launches. Regular smaller campaigns hold reputation better than occasional large ones.
Subdomains carry their own reputation and inherit some of the parent's. Splitting marketing onto news.yourdomain.com protects your primary domain, but that subdomain needs its own warm-up.
Prune unengaged recipients on a schedule. Someone who has not opened anything in a year is far more likely to complain than to convert.

Questions people actually ask

How long does it take to warm up a sending domain?: About four weeks to reach 50,000 messages a day, starting from a few hundred and roughly doubling every two to three days. The timeline is driven by your engagement rather than the calendar — a list of highly engaged recipients warms faster, and a list that produces deferrals or complaints extends it however long it takes.
Do I need to warm up if I use a shared IP?: Yes, because you are warming the domain rather than the IP. On a shared pool your provider manages IP reputation across all their customers, but domain reputation is yours alone, and a brand-new domain sending large volume is treated with suspicion no matter how good the IP is.
What happens if I skip warm-up and send to my whole list?: Typically deferrals and throttling within the first few thousand messages, then spam-folder placement, then — if complaints cross 0.3% — outright rejections. Recovery takes two to six weeks of careful low-volume sending, which is considerably longer than the four weeks warming up would have taken.
Should I warm up a subdomain separately?: Yes. A subdomain inherits some reputation from the parent domain but accumulates its own, so a new marketing subdomain needs its own ramp. That separation is usually worth it: it means a poorly received campaign cannot damage delivery of receipts and password resets sent from the primary domain.
Can I use a warm-up service that sends to seed inboxes?: It is not advisable. These services generate artificial opens and replies between accounts they control, which is engagement manipulation rather than reputation building, and providers have become good at recognising the pattern. Real recipients opening real mail is the only signal that holds up.

Check the records before you start warming up

Warming a domain that fails authentication accomplishes nothing. Confirm SPF, DKIM, and DMARC all resolve and align before day one of any schedule.

Check my domain