Cold email domain warmup timeline: week-by-week guide

Last updated: August 2026 · Ryan Mercer, SDR turned cold email consultant, 8 years outbound

---

TL;DR — 7 things to know before reading

• A sending domain and its inboxes need 4–6 weeks of warmup before cold campaigns can launch safely; full maturity takes 10–12 weeks, per Instantly's cold email benchmarks
• Warmup builds domain reputation with Gmail, Outlook, and other mailbox providers through positive engagement signals (sends, opens, replies) that establish the domain as a legitimate sender before cold outreach begins
• Skipping or shortening warmup is the single most common cause of poor inbox placement for new cold email operations — campaigns launched from unwarmed inboxes often achieve 20–30% inbox placement instead of 90%+
• Instantly manages automated warmup for all connected inboxes; Inframail provisions Microsoft 365 inboxes with automatic DNS so warmup starts on a trusted IP baseline from day one
• Quarvio delivers verified contacts for when warmup completes — so domains are ready to receive campaigns without bounce-rate damage on day one of cold sends
• Do not reduce warmup sends to zero when cold campaigns begin; warmup should run continuously at maintenance level (5–10/inbox/day) for the life of the sending domain because ongoing positive signals offset the natural negative signals from cold outreach over time
• When adding new inboxes to an established domain, those inboxes need only 2–4 weeks of warmup rather than the full 4–6 weeks required on a brand-new domain, because the domain's existing Postmaster reputation supports faster development for new inbox additions

---

Our take

The warmup timeline question most cold email practitioners ask is: "How soon can I start sending?" The correct answer depends on what they mean by "sending." With Instantly's automated warmup network running from day one, sending starts immediately — but the sends are warmup emails exchanged within the network, not cold outreach to prospects.

Cold campaign sends to prospects require the warmup period to have established sufficient positive engagement history. Launching campaigns before that history exists forces the sending domain to compete for inbox placement without reputation support. The result is predictable: high spam filter rates, low open rates, and a reputation signal that takes longer to repair than the warmup period would have taken to complete.

This guide covers the exact week-by-week timeline for a new sending domain and its inboxes, what the warmup process is doing at each stage, and how to know when a domain is genuinely ready for full cold campaign volume.

Why warmup is required before cold sends

New sending domains begin with no reputation history. Mailbox providers evaluate incoming email from unknown domains with heightened scrutiny: when a brand-new domain starts sending email to large numbers of addresses, the behavior pattern is indistinguishable from a spam operation until positive signals accumulate.

The warmup process creates those signals. Automated warmup networks like Instantly's exchange emails between network participants — sending, opening, and occasionally replying — in patterns that build the sending domain's record of positive engagement. Over 4–12 weeks, that history accumulates to the point where cold outreach emails are evaluated by Gmail against a domain with an established track record, not as mail from an unknown new domain.

The three factors warmup addresses:

Domain reputation: The domain's standing with Gmail and other providers, reflected in Google Postmaster Tools as High, Medium, Low, or Bad.

IP baseline: Inframail provisions Microsoft 365 inboxes, which send from Microsoft's shared IP infrastructure with pre-established trust. This means new inboxes start warmup on a trusted IP rather than zero.

Sending pattern legitimacy: Warmup creates a gradual volume ramp that looks like a growing legitimate sender, not a sudden spike from a new domain.

Week-by-week warmup timeline

Week 0: provision and configure (day 1 setup)

Before any warmup sends begin, the infrastructure must be correctly configured.

Tasks:

• Register sending domain (separate from primary business domain)
• Provision Microsoft 365 inboxes via Inframail with automatic SPF, DKIM, and DMARC configuration
• Connect inboxes to Instantly and verify authentication records are passing
• Enroll all inboxes in Instantly's warmup network
• Add domain to Google Postmaster Tools for reputation monitoring

Per the Mailgun SPF, DKIM, and DMARC guide, all three authentication records must pass before warmup begins. Inframail configures these automatically; verify each is passing in MXToolbox before proceeding.

Volume: 0 cold sends. Warmup network sends begin at low volume (5–10/inbox/day).

---

Weeks 1–2: low-volume warmup only

The domain is new. No cold campaign sends. Warmup network sends only.

What is happening:

• Instantly's warmup network sends 10–20 emails per inbox per day to network participants
• Network participants open, click, and occasionally reply to warmup emails
• These engagement signals begin building the domain's reputation with Gmail and other providers
• Google Postmaster Tools begins receiving data for the domain (may show "Not enough data" initially)

Inbox placement: Low (domain has no history). Warmup network manages around this by sending within the network where inbox placement is guaranteed.

Cold campaign sends: None.

Signs everything is working: Warmup emails showing in inbox (not spam) for the Gmail accounts in Instantly's warmup network. Postmaster Tools shows data beginning to populate.

---

Weeks 3–4: warmup volume ramp

The domain has 2–3 weeks of positive engagement history. Warmup volume increases.

What is happening:

• Warmup sends increase to 20–30 per inbox per day
• Domain reputation in Postmaster Tools may begin showing as Medium or High
• Spam complaint rate should be near zero (all warmup sends are to network participants who will not complain)
• Domain age (2–3 weeks) is beginning to register as an established sender, not brand-new

Cold campaign sends: Still none for production quality. Some practitioners send 5–10 test emails to known contacts in weeks 3–4 to verify inbox placement, but this is not cold outreach volume.

Signs everything is working: Postmaster Tools showing Medium or High domain reputation. Bounce rate on warmup sends: 0%.

---

Weeks 4–6: soft launch (limited cold sends)

Domain has sufficient warmup history for limited cold outreach. Begin conservative cold sends alongside continued warmup.

Volume:

• Warmup network: continue at 20–30 per inbox per day
• Cold campaign sends: begin at 10–20 per inbox per day (well below the 30–50 safe ceiling)
• Total sends per inbox: 30–50 per day combined

Per Instantly's cold email benchmarks, 30–50 emails per inbox per day is the safe ceiling for fully warmed inboxes. At the soft launch stage, staying well below this ceiling while warmup continues building additional reputation is the correct posture.

Contact list requirements: Use only verified contacts. Quarvio provides pre-verified B2B contacts — high bounce rates at this stage can permanently damage a domain before it has accumulated enough positive history to absorb the signal.

Signs everything is working: Cold sends achieving 80%+ inbox placement (check via test inbox placement tools or by sending to a seed inbox list). Postmaster Tools showing High domain reputation. No spam complaint spikes.

---

Weeks 6–10: full launch

Domain has 6+ weeks of warmup history and a track record of low complaints and positive engagement. Scale to full cold campaign volume.

Volume:

• Warmup network: continue at maintenance level (10–20 per inbox per day)
• Cold campaign sends: ramp to 30–50 per inbox per day
• Total per inbox: stay within 50 per day combined

Monitoring (weekly):

• Google Postmaster Tools: domain reputation should be High and stable
• MXToolbox blacklist checker: verify the sending domain is not on major blacklists
• Instantly analytics: review per-campaign bounce rate (should stay below 2%) and spam complaint rate (below 0.1%)

If reputation drops: Reduce cold campaign volume to 10–20 per inbox per day. Pause campaigns on any domain showing Medium or Low reputation. Resume warmup-only sends until reputation recovers to High.

---

Weeks 10–12: full maturity

The domain is fully mature. Per Instantly's cold email benchmarks, full warmup maturity is reached at 10–12 weeks.

What changes at full maturity:

• Domain has a stable, established reputation history
• New inbox additions warm faster because the domain's reputation supports them
• Full 50 cold sends per inbox per day is safely achievable
• Warmup network participation can be reduced to minimum maintenance level

Monthly maintenance (ongoing):

• Continue warmup network participation at low volume (5–10 per inbox per day) indefinitely
• Weekly Postmaster Tools review
• Monthly MXToolbox blacklist check
• Quarterly domain rotation: begin warming replacement domains 2 months before current domains age out

---

Summary timeline table

Source: Instantly's cold email benchmarks and Instantly's cold email benchmarks — verified June 2026

Common warmup mistakes that delay or damage the timeline

Starting cold sends too early: Launching cold campaigns in weeks 1–3 before reputation is established. Generates spam filter signals before positive history can offset them.

Turning off warmup after campaigns launch: Warmup should run in the background continuously, not stop when cold campaigns begin. Warmup sends provide ongoing positive engagement signals that offset the natural spam signals from cold outreach.

Adding contacts from unverified lists: High bounce rates from invalid addresses damage domain reputation at any stage but are especially harmful during early warmup when the domain has minimal positive history to absorb the signal.

Over-sending during soft launch: Sending 40–50 cold emails per inbox per day in weeks 4–6 before the domain has reached the warmup volume that supports this rate. Gradual ramp protects the domain.

Not monitoring Postmaster Tools: Reputation problems caught in week 5 are fixable in 1–2 weeks. Reputation problems discovered in week 10 because Postmaster was never checked require much longer recovery.

What practitioners say

"We made the mistake of launching cold campaigns at week 3 on our first domain setup. Reply rate was 1.8% after two weeks — we assumed the copy was the problem and spent a month rewriting sequences. Eventually we found that our inbox placement was below 30% on Gmail. The domain had Medium reputation and was filtering most of our sends. We had to pause campaigns for 3 weeks to recover. When we set up the next three domains through Inframail and Instantly and followed the full 6-week warmup timeline, inbox placement was above 90% on day one of cold sends." — G2 reviewer, Instantly reviews on G2

Instantly holds a 4.9/5 rating from 2,800+ verified reviews on G2, with automated warmup infrastructure and domain health monitoring cited as the primary infrastructure tools for maintaining inbox placement across new and existing domains.

Warmup timeline configuration reference

The following settings should be verified before warmup begins and again before soft-launch cold sends start. Correctly configured settings are the difference between warmup that progresses on schedule and warmup that stalls at Medium reputation for weeks.

Inbox provisioning settings

Warmup network sends by week

Configure these in Instantly's warmup settings. All volumes are per inbox per day.

Source: Instantly's cold email benchmarks — verified June 2026

Per-inbox sending limits to configure in Instantly

Monitoring schedule

Domain retirement planning

Begin warming replacement domains at month 9–10 so replacement inboxes reach full maturity before the retiring domain exits production. A 10–12 week lead time is required.

Troubleshooting common warmup timeline problems

Problem 1: domain stuck at Medium reputation for 3+ weeks

Symptoms: Google Postmaster Tools shows Medium reputation consistently. Inbox placement tests return 70–80% rather than 90%+. Cold campaign reply rates are low despite sending to a clean list.

Root causes: Spam complaint rate slightly elevated above 0.05% from soft-launch sends. Hard bounce rate above 1% from unverified contacts. Sending volume increased too quickly in weeks 4–6 before sufficient warmup history had accumulated.

Fix: Pause cold sends entirely for 1–2 weeks. Continue warmup network sends only at 20–30/inbox/day. Audit the contact list used in soft-launch sends — if not pre-verified, replace with contacts from Quarvio. Re-introduce cold sends at 5–10/inbox/day when Postmaster returns to High. Ramp more gradually than the first attempt: increase by 5 sends/inbox/day per week maximum.

Prevention: Use only pre-verified contacts for soft-launch sends. Begin cold sends at 10/inbox/day in week 4, not at 20. Check Postmaster Tools weekly and respond to any Medium reputation signal immediately rather than continuing to scale.

---

Problem 2: warmup emails landing in spam on recipient inboxes

Symptoms: Checking warmup email placement in Instantly shows spam placement for a portion of warmup network recipients. Warmup score is flat or declining.

Root causes: Authentication failing — SPF or DKIM records not correctly configured or not yet propagated. Domain appears on a spam blacklist. DMARC policy missing, causing some providers to apply stricter filtering.

Fix: Run the sending domain through MXToolbox's SPF, DKIM, and DMARC checkers. If any record is failing, resolve the authentication configuration issue before resuming warmup. Check MXToolbox blacklist checker for the domain. If the domain is newly registered, wait an additional 24–48 hours for DNS propagation to complete fully.

Prevention: Verify all three authentication records pass in MXToolbox immediately after Inframail provisioning, before enrolling inboxes in warmup. Inframail configures SPF, DKIM, and DMARC automatically, but DNS propagation takes up to 48 hours — verify records are live before starting.

---

Problem 3: inbox placement below 80% at week 6 soft launch

Symptoms: Test emails sent to a seed inbox list during weeks 5–6 show spam placement for 20%+ of recipients. Cold campaign reply rates are significantly below expectations for a soft launch.

Root causes: Warmup was paused or interrupted during weeks 1–5. Cold sends launched too early (weeks 2–3) and generated negative signals before sufficient positive reputation was built. Contact list used in early sends had high bounce rate.

Fix: Extend the warmup-only period by 3–4 additional weeks. Confirm warmup is running and active in Instantly. Check Postmaster spam rate data for the period when cold sends were active. If early sends caused the problem, remove that contact segment from the sequence and restart with verified contacts only. Run inbox placement tests again at week 9–10.

Prevention: Do not launch soft-launch cold sends until Postmaster shows High reputation, regardless of how many calendar weeks have passed. Use an inbox placement testing tool at week 5 before committing to cold sends at volume.

---

Problem 4: bounce rate spike in first soft-launch campaign

Symptoms: First cold email campaign in weeks 4–6 generates bounce rate above 3%. Postmaster reputation drops from High to Medium within days.

Root causes: Contact list includes unverified or outdated addresses. List contains a high proportion of role-based addresses (info@, admin@, support@) with above-average bounce rates. List was sourced from an aggregator that has not refreshed data recently.

Fix: Pause the campaign immediately. Bounce rates above 3% during soft launch damage the domain before it has the positive history needed to absorb negative signals. Replace the contact list with pre-verified contacts from Quarvio. Resume at 5–10 cold sends per inbox per day with the verified list. Monitor Postmaster daily for the first week of resumed sends.

Prevention: Never send to unverified contacts during soft launch. The domain's reputation buffer at weeks 4–6 is thin — it cannot absorb the bounce-rate damage that an unverified list generates at volume.

---

Problem 5: warmup score not increasing after 2 weeks

Symptoms: Instantly shows warmup is enabled but the warmup score is flat or barely moving after 14+ days. Postmaster shows no data or very limited data volume for the domain.

Root causes: Warmup emails are landing in spam for network participants rather than inbox, meaning network engagement is low. Inboxes are enrolled in warmup but not actively participating in the network. Authentication failure is preventing warmup emails from being delivered to network participants.

Fix: Check the warmup activity log in Instantly for each inbox to confirm sends are actually happening. Verify authentication records are passing in MXToolbox. If warmup sends are occurring but landing in spam, check for blacklisting. Reconnect inboxes in Instantly and re-enroll in warmup if the activity log shows stalled sends.

Prevention: Verify authentication before enrolling in warmup. Warmup score increases only when warmup network sends achieve inbox placement — a failing authentication record prevents this entirely.

---

Problem 6: Google Postmaster Tools shows "Not enough data" at week 3

Symptoms: After 3 weeks of warmup, Postmaster Tools still displays "Not enough data" for domain reputation. No usable data for monitoring decision-making.

Root causes: Domain not correctly verified in Postmaster Tools (the DNS TXT verification record not added or not confirmed). Warmup network sends are not reaching Gmail addresses at sufficient volume. Postmaster data lags by 1–2 weeks even with correct configuration.

Fix: Verify that the Postmaster domain verification step is fully complete — the DNS TXT verification record must be added to the domain's DNS settings and confirmed in Postmaster. Postmaster requires enough sends to Gmail addresses to generate statistical data, which typically accumulates by weeks 4–5 with correct setup. Wait until week 4 before treating "Not enough data" as a problem requiring intervention.

Prevention: Complete Postmaster domain verification on day one of setup. Verification takes 24–48 hours for the DNS record to propagate — if left until week 3, data will appear a further 2 weeks later.

---

Problem 7: reputation drop in week 10 when scaling to full cold send volume

Symptoms: Domain was at High reputation through weeks 6–9. After increasing cold sends to 40–50/inbox/day in week 10, Postmaster shows Medium reputation within 1–2 weeks.

Root causes: Volume increase was too large in a single step (20 → 50/inbox/day in one jump). Contact quality at full volume is lower than at soft-launch volume — lower-priority segments with less precise ICP targeting entered the sequence. Warmup sends were reduced too aggressively simultaneously with the cold send volume increase.

Fix: Reduce cold sends back to 25–30/inbox/day. Increase warmup sends to 15–20/inbox/day. Allow Postmaster to return to High before increasing cold volume again. Audit the contact segment that entered the sequence during the volume increase for quality issues.

Prevention: Ramp from 20 to 50 cold sends/inbox/day over 3–4 weeks rather than in one step. Keep warmup sends at 15–20/inbox/day during any volume ramp — do not reduce to minimum maintenance until the new volume level has been stable at High reputation for 2+ weeks.

---

Problem 8: domain blacklisted during the warmup period

Symptoms: MXToolbox blacklist check shows the sending domain on one or more blacklists (Spamhaus, Barracuda, SORBS). Inbox placement rates drop significantly. Postmaster shows Low or Bad reputation.

Root causes: An early cold send campaign was sent to a low-quality list that included spam trap addresses. Domain was purchased with prior bad history that was not checked before use. Warmup emails generated spam complaints from network participants (uncommon but possible if the domain has a prior negative reputation).

Fix: Pause all sends immediately. Submit delisting requests to each blacklist the domain appears on — most major blacklists provide self-service delisting for first-time listings. Identify and fix the root cause before submitting delisting requests. After delisting, resume warmup-only sends at low volume and rebuild reputation over 4–8 weeks. If the domain cannot be delisted or has persistent bad history, retire it and begin with a fresh sending domain.

Prevention: Check every sending domain at MXToolbox blacklist checker before starting warmup. Never send cold campaigns from a domain that has not completed the minimum warmup timeline.

---

Advanced warmup timeline tactics

Staggered inbox provisioning for continuous sending capacity

Rather than waiting for all inboxes to complete warmup before launching any campaigns, provision inboxes in waves to create a continuous pipeline:

Wave 1 (week 0): Provision inboxes 1–3 across domain one, begin warmup. Wave 2 (week 3): Provision inboxes 4–6 across domain two, begin warmup. Wave 3 (week 6): Provision inboxes 7–9 across domain three, begin warmup.

By week 6:

• Inboxes 1–3 are at full launch capacity (30–50 cold sends/inbox/day)
• Inboxes 4–6 are at soft launch (10–20 cold sends/inbox/day)
• Inboxes 7–9 are in early warmup (0 cold sends)

Total week 6 cold sending capacity: 120–210 sends/day, growing to 360–450 sends/day by week 12. This approach is significantly more operationally efficient than provisioning all inboxes simultaneously and waiting the full 10–12 weeks before any cold sends begin.

Recovery protocol after a reputation event

When a domain suffers a reputation event that drops Postmaster to Low or Bad:

Phase 1 (weeks 1–2): Full stop on cold sends. Continue warmup-only sends at 10–15/inbox/day. Submit blacklist delisting requests if applicable. Identify and eliminate the root cause.

Phase 2 (weeks 2–5): Warmup rebuild. Increase warmup sends to 20–30/inbox/day. No cold sends until Postmaster returns to High for two consecutive weekly checks.

Phase 3 (week 5+): Cautious re-launch. Begin cold sends at 5–10/inbox/day with verified contacts only. Increase by 5 sends/inbox/day per week maximum. Monitor Postmaster daily for the first two weeks.

Total recovery timeline: 5–8 weeks for moderate events. Severe events (major blacklisting, spam complaint rate above 0.5%) typically require retiring the domain rather than attempting recovery.

Using Postmaster data to make data-driven launch decisions

Rather than relying solely on calendar weeks, combine Postmaster data with inbox placement tests:

Green light indicators for soft launch:

• Postmaster domain reputation: High or Medium for 2+ weeks
• Spam rate: below 0.1%
• Warmup score in Instantly: stable or increasing
• Inbox placement test on Gmail seed addresses: 80%+

Green light indicators for full launch:

• Postmaster domain reputation: High for 3+ consecutive weeks
• Spam rate: below 0.05%
• Bounce rate on soft-launch sends: below 1.5%
• Inbox placement test on Gmail: 90%+

Yellow flag — delay and recheck in 1–2 weeks:

• Reputation fluctuating between Medium and High week-over-week
• Spam rate between 0.05% and 0.1%
• Any bounce rate above 2% on soft-launch sends

Maintaining reputation through volume changes

Volume changes are the most common trigger for unexpected reputation events on domains that were previously stable.

Scaling up: Increase cold send volume by no more than 30% of current volume per week. Moving from 20/inbox/day to 26/inbox/day the following week is safe; jumping to 50/inbox/day is not.

Scaling down: Abrupt reductions in cold send volume are less risky than volume spikes. Maintain warmup sends at maintenance level even during extended cold send pauses.

Taking a break of 2+ weeks: Increase warmup sends to 20–25/inbox/day during the pause to compensate for reduced cold send signals. Resuming after a long pause where warmup was also stopped is similar to starting the domain over from zero reputation.

---

Five operational warmup frameworks

Each framework below describes a specific operational scenario with the warmup approach that applies to that exact context.

Framework 1: Single-domain first-time setup for a new cold email operation

The most common scenario: a business starting from zero with one sending domain and 3 inboxes, needing to reach full campaign capacity as quickly as responsibly possible.

Week 0 (Day 1, full setup):

• Register sending domain at a reputable registrar. Use a .com variant of the business name with an outreach-relevant prefix (e.g., getmeetingwith-[businessname].com). Never use the primary business domain for cold sends.
• Provision 3 Microsoft 365 inboxes via Inframail. Inframail configures SPF, DKIM, and DMARC automatically during provisioning.
• Wait 24–48 hours, then verify all three authentication records pass in MXToolbox before proceeding.
• Connect all 3 inboxes to Instantly and enroll in the warmup network. Set warmup volume to 10–15 sends/inbox/day.
• Add domain to Google Postmaster Tools. Complete the DNS TXT verification record and confirm verification.

Weeks 1–4 (warmup only):

• No cold campaign configuration or contact imports yet. Warmup runs automatically.
• Week 2 check: confirm warmup score is increasing in Instantly. Check Postmaster for any data appearing.
• Week 4 check: Postmaster should show data for the domain. Ideally showing Medium or High reputation. If showing Low, extend warmup-only period by 1–2 weeks and check authentication records.

Weeks 4–6 (soft launch):

• Import first contact batch from Quarvio. Verify contacts are business email addresses, correct job title and company data.
• Set Instantly campaign limits to 15–20 sends per inbox per day maximum. Configure 3-email sequence with reply detection enabled.
• Monitor Postmaster daily for the first 2 weeks of cold sends. If reputation drops to Medium, pause cold sends and continue warmup-only for 1–2 weeks before resuming.

Week 6+ (full launch):

• Increase to 30–40 cold sends per inbox per day. Total capacity: 90–120 sends per day across 3 inboxes.
• Continue warmup at 10–15/inbox/day indefinitely.
• Weekly Postmaster check and monthly MXToolbox blacklist check.

---

Framework 2: Multi-domain parallel warmup for an agency scaling to 10,000+ sends per month

An agency launching outbound campaigns for multiple clients simultaneously needs to warm multiple domains in parallel without cross-contaminating reputation signals. Each domain must be independently warmed and independently monitored.

Parallel domain structure:

• Domain 1–3: Client A campaigns (3 inboxes each)
• Domain 4–6: Client B campaigns (3 inboxes each)
• Domain 7–9: Internal warmup reserve (warming new domains in advance of client demand)

All domains begin warmup on the same day when possible (Day 0). This creates a synchronized timeline where all domains approach soft-launch and full-launch capacity simultaneously, simplifying operational monitoring.

Weekly monitoring protocol for parallel domains:

Set a recurring weekly review covering all domains in one session. Create a tracking spreadsheet with columns: domain name, warmup start date, current week, Postmaster reputation (weekly reading), warmup score (weekly reading), cold send volume, bounce rate, spam complaint rate, blacklist status (monthly check).

Flag any domain showing Medium or Low reputation or warmup score plateau for immediate investigation before the next cold send.

Client domain isolation: Never share sending domains across clients. Client A's campaigns from Domain 1–3 have no connection to Client B's campaigns from Domain 4–6. If Client A's domain suffers a reputation event, it has no effect on Client B's delivery. This isolation is both a technical protection and a client relationship protection.

---

Framework 3: Post-restriction domain recovery warmup

When a domain has been restricted by Gmail due to spam complaints, high bounce rates, or other policy violations, recovery warmup differs from new domain warmup. The domain has negative reputation history that the warmup must overcome rather than a neutral starting point.

Phase 1 — Stop and diagnose (Week 1):

• Pause all cold sends from the restricted domain immediately.
• Run MXToolbox blacklist checker for the domain. Note all active listings.
• Review Postmaster data for the restriction period: what was the spam complaint rate? What caused the spike?
• Identify root cause: unverified contact list, ICP misalignment causing spam reports, opt-outs not being honored, or a volume spike.
• Do not submit blacklist delisting requests until the root cause is fixed. Delisting without fixing the root cause results in relisting within weeks.

Phase 2 — Fix and delistment (Weeks 1–2):

• Fix the root cause identified in Phase 1.
• Submit delisting requests to each blacklist operator. Most major lists (Spamhaus, Barracuda, SORBS) provide self-service delisting for first-time offenses.
• Confirm the domain is delisted before resuming any sends. Allow 48–72 hours after delisting before the first warmup sends.

Phase 3 — Recovery warmup (Weeks 2–6):

• Resume warmup-only sends at conservative volume: 10–15/inbox/day.
• Check Postmaster weekly. Monitor for reputation progression: Bad → Low → Medium → High.
• Do not resume cold sends until Postmaster shows Medium for 2 consecutive weeks AND High for 1 week.
• If reputation does not progress beyond Low after 6 weeks of recovery warmup, the domain history may be too damaged to recover. Consider retiring the domain and starting fresh.

Phase 4 — Cautious re-launch (Week 7+):

• Resume cold sends at 5–10/inbox/day maximum with verified contacts only.
• Increase by 5 sends/inbox/day per week maximum. Do not ramp at the same rate as a new domain.
• Monitor Postmaster daily for the first 3 weeks of resumed cold sends.

---

Framework 4: Domain rotation and replacement warmup pipeline

For operations running at 5,000+ monthly sends per domain, a continuous rotation cycle ensures no domain accumulates damaging negative signals. The rotation pipeline requires warming replacement domains in advance of retiring current domains.

Rotation schedule (for a 3-domain portfolio):

At any point in this rotation, the operation always has at least one fully warm domain in peak production and one domain in active warmup.

Retirement protocol:

• Month 9–10: Begin warming the replacement domain immediately. The 10–12 week warmup timeline requires this lead time.
• Month 11: Reduce cold sends on the retiring domain to 25% of full volume. Redirect volume to the replacement domain once it reaches soft-launch capacity.
• Month 12–13: Pause cold sends on the retiring domain entirely. Continue warmup maintenance on it at 5/inbox/day for 4–8 weeks before retiring it completely.

This approach prevents the volume gap that occurs when a domain is retired without a replacement ready at full capacity.

---

Framework 5: High-volume scale-up from 500 to 5,000 sends per day

Scaling from a small operation (1–2 domains, 3–6 inboxes) to a high-volume operation (10–20 domains, 30–60 inboxes) requires a structured warmup expansion plan rather than provisioning all new domains simultaneously.

Why not provision all domains at once: Warming 10 new domains in week 1 of a scale-up creates a monitoring burden that allows individual domain problems to go undetected. A structured phased expansion is more manageable and allows learnings from early domains to inform later provisioning.

Phase 1 (Months 1–2): Foundation domains

• Provision 4 sending domains, 3 inboxes each (12 inboxes total).
• Warm all 4 domains in parallel.
• Begin soft-launch cold sends at month 2 on the first 2 domains.
• By end of month 2: 2 domains at full launch (180–300 sends/day combined), 2 domains completing warmup.

Phase 2 (Months 2–4): Expansion

• Provision 4 additional sending domains as Phase 1 domains reach full maturity.
• Total domains at month 4: 8, of which 4 are at full production and 4 are in warmup.
• Full production capacity by end of month 4: 720–1,200 sends/day.

Phase 3 (Months 4–6): Scale

• Provision final 4–8 domains for target volume.
• Total domains at month 6: 12–16 at varying warmup stages.
• Full production capacity at month 6: 2,160–4,000 sends/day.

Monitoring at scale: Assign warmup domain monitoring to a dedicated team member above 10 active domains. A weekly domain health spreadsheet tracking Postmaster reputation, warmup score, bounce rate, and spam complaint rate for all active domains is the minimum monitoring requirement. Above 20 domains, automate Postmaster data collection where possible and set alert thresholds to flag any domain dropping below High reputation within 24 hours.

---

Our actual stack

Frequently asked questions

How long does domain warmup actually take before cold campaigns can start?

The minimum warmup period before starting any cold sends is 4 weeks. Soft-launch cold sends (10–20 per inbox per day) are appropriate from week 4–6. Full cold campaign volume (30–50 per inbox per day) is appropriate from week 6 onward. Full maturity — where the domain has a stable, established reputation that supports consistent high inbox placement — is reached at weeks 10–12.

Can I speed up the warmup timeline?

No. Warmup duration is determined by the rate at which mailbox providers accumulate engagement data about the sending domain. Sending warmup emails at higher volume than the timeline recommends does not accelerate reputation development and may generate spam filter signals that slow it. The timeline in this guide reflects the minimum responsible warmup timeline, not a conservative estimate.

Do I need to keep warmup running after cold campaigns launch?

Yes. Warmup should run continuously in the background throughout the life of the sending domain. Cold outreach generates natural negative signals (non-opens, occasional complaints) that warmup's positive engagement signals offset. Domains where warmup was turned off after campaigns launched show reputation degradation over time compared to domains where warmup runs continuously.

What happens if I need to reach prospects before the warmup period is complete?

Use inboxes on domains that have already completed warmup. If the current operation has no warmed domains yet, the warmup timeline is not negotiable — launching cold sends from an unwarmed domain achieves inbox placement rates too low to generate meaningful results. The 4–6 week investment in warmup is the prerequisite for cold email performance, not optional preparation.

How many inboxes can I run through warmup at the same time?

There is no technical limit in Instantly — the warmup network handles any inbox count automatically. The practical constraint is monitoring capacity. Each domain in warmup needs a weekly Postmaster review. For 1–5 domains, a 15-minute weekly check is sufficient. For 10–20 domains simultaneously, a structured domain tracker spreadsheet with weekly review is required to ensure no domain's problems go unnoticed. Above 30+ domains, consider delegating monitoring responsibilities to a dedicated team member with a formal weekly audit protocol.

Does warmup work differently for Microsoft 365 vs Google Workspace inboxes?

The warmup mechanics work similarly across both providers, but Inframail's Microsoft 365 inboxes start from a stronger IP reputation baseline. Microsoft's shared sending IP infrastructure has established trust with mailbox providers through millions of legitimate senders. New inboxes provisioned via Inframail benefit from this baseline, which typically means slightly faster initial Postmaster data development compared to starting on lesser-known shared IP infrastructure. The warmup timeline applies to both, but Microsoft 365 via Inframail generally shows faster early progression.

What is the right warmup send volume at full maintenance stage after week 10?

At full maturity (week 10+), warmup network sends should continue at 5–10 per inbox per day indefinitely. This maintenance level provides ongoing positive engagement signals that offset the natural negative signals from cold outreach (non-opens, occasional spam complaints). Stopping warmup entirely after maturity is one of the most common mistakes in long-running cold email operations — domains where warmup is discontinued show measurable reputation degradation after 3–6 months compared to domains where warmup runs continuously at maintenance level.

Can I run warmup on a domain that already has a poor reputation to recover it?

Yes, but the recovery process differs from initial warmup. The root cause of the reputation problem must be identified and fixed first: authentication errors, spam complaint spikes from a bad contact list, or blacklisting. Once fixed, warmup-only sends at 20–30/inbox/day for 4–8 weeks rebuild reputation. Google Postmaster Tools is the instrument for monitoring recovery — watch for progression from Low to Medium to High over consecutive weekly checks. If the domain is blacklisted, submit delisting requests to relevant blacklist operators before beginning recovery warmup. Severe reputation damage may require retiring the domain rather than attempting recovery.

Does the warmup timeline differ for the first inbox on a domain vs inboxes added later?

Yes, and in the sender's favor for later additions. When adding new inboxes to a domain that has been in active production for several months, those new inboxes benefit from the domain's established reputation. New inboxes on an established domain typically need 2–4 weeks of warmup rather than the 4–6 weeks required on a brand-new domain. The domain's Postmaster data continues accumulating based on all sends from all inboxes, meaning new inbox sends are evaluated against the domain's existing positive history.

What does the warmup score in Instantly measure and what level is needed before launching cold sends?

Instantly's warmup score reflects the engagement quality of warmup network sends — specifically whether warmup emails are landing in inbox (not spam) for network participants and receiving engagement (opens, replies). A score of 80+ is typically considered strong. However, warmup score alone should not be the launch criterion. Use Google Postmaster Tools domain reputation (High for 2+ consecutive weeks) as the primary green light, with inbox placement testing on a Gmail seed list as secondary confirmation. Warmup score is most useful as an early indicator that something is wrong — a falling score in weeks 1–4 signals an authentication or spam placement problem.

What signals confirm warmup is complete and full cold send volume is safe?

The four-signal readiness checklist: (1) Google Postmaster Tools shows High domain reputation for 2+ consecutive weekly checks; (2) spam rate in Postmaster is consistently below 0.05%; (3) bounce rate on soft-launch sends is below 1.5%; and (4) an inbox placement test on Gmail seed addresses shows 85%+ inbox placement. When all four are met at week 6+, scaling to 30–50 cold sends per inbox per day is appropriate. Calendar weeks matter less than the data — some domains meet these criteria at week 5, others at week 8–9.

Does sending warmup emails at higher volume than recommended speed up the timeline?

No — and excessive warmup volume often slows progression by generating volume-spike signals. The timeline is governed by how quickly mailbox providers accumulate reputation data about the sending domain, not by raw warmup email count. Sending 60+ warmup emails per inbox per day in weeks 1–2 does not cause Gmail to trust the domain faster. At excessive volumes, the pattern resembles a new-domain volume spike — the exact behavior spam filters flag. Follow the recommended progression: 10–20 warmup sends/inbox/day in weeks 1–2, increasing to 20–30 in weeks 3–4. The timeline cannot be compressed, only followed correctly.

---

Warmup builds domain reputation. Verified contacts protect it.

The warmup timeline invests weeks in building domain reputation. Sending to unverified contacts with high bounce rates can damage that reputation in days. Quarvio delivers pre-verified B2B contacts so every campaign send is to a valid address from the first cold send on a newly warmed domain.

Start your order on Quarvio →