Domain warmup and safe sending volume

A domain registered on Monday and sending 500 cold emails on Tuesday follows a pattern receivers have seen a million times, and it is the pattern of a spammer burning domains. Warmup is not a trick. It is the process of building a sending history that separates a real operation from that pattern. This guide covers why new domains carry risk, a ramp schedule that holds up in practice, per-inbox limits, and where domain age fits in a launch decision.

What domain warmup is

Warmup is a period of low, gradually increasing sending volume on a new domain and its inboxes before real campaign traffic starts. During warmup the domain accumulates the signals receivers use to score senders: consistent volume, real engagement, low bounces, no spam complaints.

Reputation at Gmail and Microsoft is tracked per domain and per IP, and for cold email through Google Workspace or Microsoft 365 the domain is the part you own. A new domain has no history, and no history is itself a risk signal.

Why it matters for a cold email launch

• Volume spikes from new domains are the top spam heuristic. Zero to hundreds of messages per day on a 3-day-old domain matches the disposable-domain pattern, and filters respond within days, not weeks.
• Early damage compounds. High bounces in week one, from an unverified list, teach receivers the wrong thing about the domain while it has no positive history to offset it. Some of that scoring persists for months.
• A burned domain costs more than the 12 dollars. Replacement means new DNS setup, new inboxes, new warmup, and 3 or more lost weeks. For an agency, it also means explaining the delay to a client.
• Blacklists watch new-domain behavior. Spamhaus DBL and similar lists flag newly registered domains that jump straight to bulk volume. Delisting is covered in the blacklists guide, but not getting listed is cheaper.
• Recent sender history can override age. An older domain or IP is not automatically safe if it has recent abuse events or repeat blacklist history.

A ramp schedule that works

Baseline assumptions: a fresh domain, 2 to 3 inboxes on it, authentication (SPF, DKIM, DMARC) verified before the first message.

• Week 0, before any sending: DNS records live and verified, inboxes created, profile photos and signatures set. Let the domain sit registered for at least 2 weeks before real campaigns if the timeline allows it.
• Weeks 1 to 2: 5 to 10 messages per inbox per day. Warmup traffic and genuine one-to-one mail. Replies matter more than volume.
• Weeks 3 to 4: 15 to 25 per inbox per day. First small campaign batches to verified addresses are fine at the end of this window.
• Weeks 5 to 6: 30 to 40 per inbox per day, approaching steady state.
• Steady state: 30 to 50 per inbox per day, no more. Higher numbers per inbox are where accounts get flagged. Scale with more inboxes and more domains, not more volume per inbox.

Rules that override the schedule: never more than double volume week over week, hold or reduce volume if bounces exceed 2 percent or any spam complaints appear, and keep sending consistent day to day rather than bursting.

Warmup pools that fake engagement between member inboxes are widely used, and Google’s terms prohibit simulated engagement, so treat them as a risk decision rather than a default. Consistent low-volume real sending is the part that is unambiguously safe.

Per-inbox daily limits

Steady-state numbers that hold up in 2026:

• 30 to 50 cold emails per inbox per day. This is the working ceiling for Google Workspace and Microsoft 365 inboxes doing outbound.
• Provider hard caps are far higher (Google Workspace allows 2,000 recipients per day) but the hard cap is not the risk line. Filtering starts long before the cap.
• Follow-ups count. 30 new prospects plus 20 follow-ups is a 50-send day.
• Space sends across the working day with randomized intervals. 40 messages in one minute reads differently than 40 across 8 hours.

To plan capacity backwards: a 6,000-contact campaign at 40 sends per inbox per day across a 4-step sequence needs roughly 10 to 12 inboxes on 4 to 6 domains to complete in a month. Buying that infrastructure is cheaper than burning one domain.

Domain age

Age is a passive signal but a real one. Filters and blacklist operators score newly registered domains as higher risk, typically for the first 30 days and to a lesser degree for 90.

• Under 2 weeks: do not launch campaigns. Warmup only.
• 2 to 4 weeks: small volumes acceptable with clean lists and full authentication.
• 30 days and older: age stops being a meaningful negative on its own.

OutboundQA checks domain age as one of its launch signals: a very new domain does not fail a launch by itself, but combined with missing authentication it moves a verdict toward Do Not Launch. Buying domains 4 to 6 weeks ahead of need is the cheapest fix in cold email.

Sender history and IP abuse risk

Age tells you how long the domain has existed. Sender history tells you what happened around the sender before this launch.

Before using an aged domain, inherited SMTP relay, or shared sending pool, check for:

• recent abuse events in the last 30 to 90 days;
• historical blacklist events and whether they repeated;
• highest incident severity and when it was last seen;
• IP abuse signals if you control or configure the SMTP egress path;
• repeated current-check failures in your own monitoring history.

These signals should not be treated as a fake inbox-placement score. They are launch-risk evidence. A clean trend supports a normal ramp. A worsening trend, recent high-severity abuse, or repeat blacklist history is a reason to slow the ramp, switch infrastructure, or hold the launch until the sender has cleaner history.

Common mistakes

1. Skipping warmup because the timeline is tight. The 3 weeks saved get repaid as a burned domain plus 3 or more weeks of replacement.
2. Warming the domain but launching with an unverified list. A 10 percent bounce rate undoes clean warmup in 2 days.
3. Scaling volume per inbox instead of adding inboxes. 200 per day from 2 inboxes fails where 40 per day from 10 inboxes works.
4. Bursting. 5 quiet days then 300 sends on Friday is a spike pattern regardless of the weekly average.
5. Using the main company domain. Warmup exists because domains can be damaged. Send cold from separate domains so the brand domain is never the one at risk.
6. Treating warmup as finished forever. An inbox idle for a month needs a short re-ramp, not day-one full volume.

FAQ

How long does warmup take? 2 to 4 weeks to first careful campaigns, 5 to 6 weeks to steady state. Shorter timelines trade directly against risk.

Do warmup tools replace the ramp? No. They supplement early volume and engagement, and they carry policy risk on Google. The ramp discipline is the part that protects the domain.

Does domain age reset if I change DNS or providers? No. Age runs from registration. Moving a domain between inbox providers does not reset it, though sending reputation is partly provider-specific.

Can I check a domain’s age and risk before buying inboxes for it? Yes. The domain reputation checker reads age, current blacklist status, and authentication signals in one pass. The full OutboundQA report can also include sender-history signals from monitoring history and optional IP abuse intelligence.

Warmup readiness is part of what OutboundQA verifies before a launch, alongside the full cold email infrastructure checklist. Check a domain’s observable risk with the domain reputation checker before the first campaign goes out.