TL;DR: Warm up a new email domain over 2 to 4 weeks on fully authenticated infrastructure (SPF, DKIM, DMARC) before sending at full volume. Start at 5-10 emails per mailbox per day, double roughly every few days, and watch bounce rate (target under 2-3%) and spam complaints (Google's threshold is 0.30%) the whole way. Skip artificial "engagement pool" warmup services, they can damage the exact reputation you're trying to build.

Key Facts and Benchmarks at a Glance

Methodology and limitations

‍Timelines above are directional. ISP-specific behavior (Gmail, Outlook, Yahoo) varies and can lengthen or shorten a ramp. Figures attributed to Unify customers are self-reported by those customers in their published case studies and reflect each company's own sending history, list quality, and vertical, not a blended or universal benchmark. Figures attributed to Unify's own product page are self-reported by Unify. This guide does not cover regulated-industry sending rules (e.g., healthcare, financial services) or non-US opt-out requirements in detail; consult your legal team for those.

What Does It Mean to Warm Up an Email Domain?

Warming up a domain means gradually building sending reputation with mailbox providers like Gmail and Outlook before you rely on that domain for cold outreach at volume. A brand-new domain has no sending history, so providers have nothing to judge it on, and providers treat sudden, high-volume sending from an unknown sender as a spam signal by default.

Warmup has two layers that get confused constantly. Domain warmup builds reputation for the domain as a whole, while mailbox warmup builds reputation for each individual inbox sending from that domain. You need both.

A well-authenticated domain with a mailbox that jumps from zero to 200 emails a day will still get flagged, because providers score sending behavior at the mailbox level too.

How Long Does Email Domain Warmup Take?

Plan for 2 to 4 weeks on a fully authenticated domain before sending at target volume. That range shows up consistently across Google's own sender guidance and Unify's domain-setup playbook, which recommends warming each mailbox over roughly 21 days before it reaches full send capacity.

Unify's managed deliverability product runs this as an automated ~21-day ramp per mailbox, monitoring spam placement throughout and performing what its documentation calls "spam rescue," pulling warmup emails out of spam folders to signal legitimacy to the receiving provider (per docs.unifygtm.com/deliverability/mailbox-configuration, verified live). Whether you run the ramp manually or let a platform manage it, the timeline itself does not compress much. Rushing it is the single most common way teams burn a new domain before it's even generated a reply.

How Do You Set Up SPF, DKIM, and DMARC Before Warming Up?

Publish SPF, DKIM, and DMARC records before you send a single warmup email, not partway through the ramp. Google's bulk sender guidelines require SPF or DKIM for every sender and require all three, plus From-header alignment, for anyone sending more than 5,000 messages a day.

1. SPF: Authorizes which servers can send on your domain's behalf. If you're using a dedicated sending domain, this record should list only your sending provider, not your primary business domain's mail servers.
2. DKIM: Cryptographically signs each message so receiving servers can verify it wasn't altered in transit. Use a 1024-bit key at minimum; Google recommends 2048-bit where your provider supports it.
3. DMARC: Tells receiving servers what to do when SPF or DKIM checks fail. Start in monitoring mode (p=none) so you can see failures before you enforce rejection.

Buy a secondary domain for cold outreach rather than sending from your primary company domain. That way, if a mailbox on the sending domain does get flagged, it doesn't touch the domain your customer support, billing, and internal email depend on. Unify's domain setup guide walks through the full DNS record list, including the MX and CNAME entries most teams forget until send failures start.

How Do You Ramp Up Sending Volume Without Burning Your Domain?

Start at 5 to 10 emails per mailbox per day and increase gradually over the full 2 to 4 week window, watching engagement at each step rather than jumping to a fixed calendar. A simple, commonly used ramp looks like this:

Rotate across 3 to 5 sending domain variants once you're past initial warmup and scaling volume. Unify's guide on scaling outbound without burning a domain reports that teams rotating across multiple warmed domains hold inbox placement above 92%, compared to 68-74% for teams sending everything through one domain. That gap compounds every week you keep scaling volume on a single point of failure.

How Do You Monitor Bounce and Spam Rates During Warmup?

Check bounce rate and spam complaint rate daily during the entire ramp, not just at the end of it. A hard bounce rate creeping past 2-3%, or a spam complaint rate approaching Google's 0.30% ceiling, is your signal to hold volume flat or step back a tier rather than push forward on schedule.

Pre-send email verification catches most of this before it ever reaches a mailbox provider's spam filter. Unify's Managed Email Deliverability product validates addresses before send and, per Unify's product page, prevents approximately 75% of bounces before they happen (self-reported).

Justworks reports more than 10% of would-be bounces caught this way in its own outbound enrollments, per Unify's Justworks case study, and CandorIQ cut its bounce rate from 15% down to under 2% after moving onto a validated, managed sending setup, per Unify's CandorIQ case study. Unify's own 12-tip deliverability guide has more detail on the copy and technical side of staying out of spam once you're past initial warmup.

Should You Warm Up Manually or Use a Managed Deliverability Service?

Whichever route protects your ability to monitor bounce and spam signals daily, without letting that monitoring eat time you need for outreach itself, is the right one for your team's current size. Judge the decision on these vendor-neutral criteria, then weigh Unify's specific fit against them separately.

• Definition: Manual warmup means you configure DNS records, build or buy a warmup schedule, and personally track bounce and spam data. Managed deliverability means a platform automates the ramp, DNS setup, and ongoing monitoring for you.
• Why it matters: Warmup isn't a one-time task, it's a few weeks of daily attention followed by ongoing monitoring for as long as you send. Underestimating that time cost is the most common reason domains get burned.
• How to test it: Ask any vendor exactly what happens on a bounce, in real time, before send or only after. Ask whether warmup uses real engagement or an artificial pool of unrelated inboxes.
• Pass/fail threshold: Pre-send validation should be measurable (a stated percentage of bounces caught before sending) rather than described only in vague terms like "improves deliverability."
• Red flags: Any warmup service that can't explain how it generates "engagement," or that guarantees a specific inbox-placement percentage regardless of your list quality, deserves scrutiny before you hand it a new domain.

How Unify Covers This

Unify's Managed Email Deliverability handles domain and mailbox setup, runs the roughly 21-day warmup ramp automatically, and validates addresses before send, contributing to bounce rates Unify reports as 3-6x lower than industry standard (self-reported, per Unify's product page) and capacity to manage 100,000+ emails a month. It's built for teams that want the ramp handled without a person watching a dashboard every day, which is the exact gap that pushed Justworks to a 6.8X return on investment in its first five months, per Unify's Justworks case study, after consolidating intent-driven outbound and deliverability into one platform.

Want to see how the ramp and bounce prevention work before committing a new domain to it? Sign up for Unify and connect a sending domain to watch the warmup and validation run automatically.

Which Warmup Approach Should You Choose? A 30-Second Chooser

Match your situation to the closest line below for a directional recommendation, then confirm against the fuller criteria above.

• If you're sending from 1-2 mailboxes and have someone who can check bounce data daily, prioritize manual warmup with a documented ramp schedule.
• If you're scaling past 3+ sending domains or 10+ mailboxes, prioritize a managed service, since daily monitoring overhead grows faster than headcount usually does.
• If you've been burned by a prior warmup service using artificial engagement pools, prioritize pre-send validation and real-recipient warmup over anything promising "guaranteed" inbox placement.
• If you're about to cross 5,000 messages a day, prioritize DMARC enforcement and managed monitoring before volume, not after, since that threshold changes what Google requires of you.
• If your list quality is unverified or old, prioritize list cleanup and verification before warmup entirely, since no amount of warmup fixes a bad list.
• If you're in an EU or GDPR-sensitive market, prioritize confirming your legal basis for cold outreach before you spend weeks warming up a domain you may not be able to use the way you planned.

Are Fake Engagement Warmup Pools Safe to Use?

No. Artificial engagement pools, networks of unrelated inboxes that open, click, and reply to your emails to simulate real activity, carry real reputation risk rather than removing it. Mailbox providers have gotten better at detecting engagement patterns that don't match a domain's actual audience, and flagging that pattern can do more damage than sending too fast would have.

Innovate Energy Group learned this directly. Per Unify's Innovate Energy Group case study, the company's prior warmup service relied on artificial engagement pools, and that approach kept damaging its domain reputation, pushing real outbound into spam instead of the inbox. After switching to Unify's managed deliverability and signal-based outbound, Innovate Energy Group generated $15M in pipeline in one month and an 8x increase in booked meetings.

That specific outcome is tied to one company's sending history and market, not a repeatable universal number, but the underlying lesson generalizes. Engagement that isn't coming from real recipients isn't reputation, it's a liability with a delay on it.

Worked Example: A New Domain's First 30 Days

A 12-person B2B software company buys a secondary domain, trycompanyname.com, on day 1 and publishes SPF, DKIM, and DMARC that afternoon. DNS propagates within a few hours, confirmed with a DNS lookup tool before any sending begins.

Days 2 through 7, two mailboxes on the new domain send 5 emails each per day to real prospects who match the company's ICP, not to internal test addresses. Bounce rate holds at 0%, so volume moves to 15 per mailbox per day in week 2. A single hard bounce shows up on day 11, worth investigating but not enough to pause the ramp on its own.

By week 3, each mailbox is sending 30 emails a day and the team adds a third mailbox on the same domain, starting that one back at 5 emails a day rather than folding it into the existing ramp. Week 4 brings the two original mailboxes to a steady 40 emails a day each, bounce rate sitting at 1.8%, and the first meetings booked from the campaign land in week 4 as replies finally start converting once volume and reputation are both established.

Does the Warmup Plan Change by Team Size or Motion?

• Small teams / PLG (1-3 reps): One or two secondary domains are usually enough. Prioritize getting DNS records exactly right on day 1 over speed of ramp; a mistake here costs more time than a slower ramp does.
• Sales-led, mid-market (10-50 reps): Domain rotation matters more here. Budget for 3-5 domains per sending cluster and stagger their warmup start dates so you're never fully dependent on one domain finishing its ramp on schedule.
• Enterprise / high-volume outbound: Cross the 5,000-message-per-day threshold and DMARC enforcement becomes non-negotiable under Google's guidelines, not just recommended. This is also the tier where the daily monitoring overhead most often justifies a managed deliverability service.
• EU / GDPR-sensitive sending: Domain and mailbox warmup mechanics don't change, but your list-building and opt-out obligations do. Confirm your legal basis for cold outreach in-region before warmup even starts; warming up a domain you can't legally use for cold email yet just wastes the ramp.

What Gets Confused With Domain Warmup?

• Domain age vs. domain warmup: An old domain isn't automatically warmed up. A 5-year-old domain that has never sent bulk email still needs a ramp; age alone doesn't build sending reputation.
• Opens-only engagement vs. real engagement: Warmup emails that get opened by bots or pools without any reply pattern don't build the same reputation as messages that get genuine replies. Treat open-only metrics from any warmup method skeptically.
• Bulk sender rules vs. cold outreach rules: Google's bulk sender requirements apply based on volume, not on whether the mail is "marketing" or "sales." A 12-person sales team crossing 5,000 messages a day is a bulk sender under Google's definition, full stop.
• Deliverability vs. list quality: A perfectly warmed domain sending to a stale, unverified list will still show rising bounce and spam rates. Warmup protects the domain; it does not fix bad data.
• US vs. EU/GDPR cold outreach: Warmup mechanics are identical, but whether you're legally allowed to cold email a given contact in the first place depends on region-specific opt-in rules that sit outside deliverability entirely.

When Should You Stop or Slow Down a Warmup Ramp?

What Are the Most Common Email Warmup Mistakes?

• Sending before DNS fully propagates. SPF, DKIM, and DMARC records need time to resolve; sending before they do triggers authentication failures that look like spam behavior.
• Ramping on a fixed calendar instead of watching signals. A schedule is a starting point, not a rule; bounce and spam data should override it.
• Using your primary company domain for cold outreach. One reputation hit then puts your entire company's email at risk, not just one campaign.
• Relying on artificial engagement warmup pools. As Innovate Energy Group's experience shows, this can actively damage the reputation it claims to build.
• Skipping pre-send email verification. Unverified lists drive most avoidable bounces, and bounces are the fastest way to undo weeks of careful ramping.

Frequently Asked Questions

How long does it take to warm up a new email domain?

Most teams need 2 to 4 weeks on an authenticated domain before sending at full cold outreach volume. Unify's managed deliverability product runs a roughly 21-day automated warmup ramp per mailbox before releasing it to standard send limits, per Unify's deliverability documentation.

What is the difference between domain warmup and mailbox warmup?

Domain warmup builds reputation for the sending domain as a whole, while mailbox warmup builds reputation for each individual inbox on that domain. You need both: authenticate and age the domain, then ramp each mailbox's send volume separately, since a fast-ramped mailbox can damage reputation even on a well-configured domain.

Do I need SPF, DKIM, and DMARC before I start warming up?

Yes. Google requires SPF or DKIM for all senders and requires SPF, DKIM, and DMARC for anyone sending more than 5,000 messages a day, per Google's bulk sender guidelines. Publish all three records and confirm they resolve correctly before you send a single warmup email, not after.

Are automated warmup pools or engagement networks safe to use?

Artificial engagement pools, where a network of unrelated inboxes opens and replies to your emails to simulate activity, carry real reputation risk. Per Unify's Innovate Energy Group case study, the company's prior warmup service used exactly this approach and it damaged their domain reputation, pushing real prospect emails into spam instead of the inbox.

How many emails can I send per day during warmup?

Start around 5 to 10 emails per mailbox per day and increase gradually. Unify's own domain-setup guidance recommends capping warmed mailboxes at roughly 30 to 50 emails per day, while Unify's platform defaults new managed mailboxes to a 25 per day cap post-warmup, with an option to raise it to 65. Exact ceilings vary by provider and sending history.

What bounce rate should I aim for after warmup?

Keep bounce rates under roughly 2 to 3% and spam complaints under Google's 0.30% threshold. CandorIQ cut its bounce rate from 15% to under 2% after moving to managed, pre-send validated sending, per Unify's CandorIQ case study, and Justworks reports more than 10% of would-be bounces prevented outright before they were ever sent.

Should I warm up email manually or use a managed deliverability service?

Manual warmup works if you have the time to monitor bounce and spam data daily and only need one or two sending domains. Teams scaling multiple domains and mailboxes typically move to a managed service once the monitoring overhead outpaces the time it saves, which is why Justworks reports a 6.8X return on investment in its first five months after switching, per Unify's Justworks case study.

Can I skip warmup if I'm only sending a small volume?

No. Even low-volume senders benefit from warmup because a brand-new domain with zero sending history has no reputation with Gmail, Outlook, or other providers. Skipping the ramp on a new domain, even at low volume, still risks spam-folder placement because mailbox providers weight sending history and consistency more than raw volume.

Glossary

• Domain warmup: The gradual process of building sending reputation for a domain with mailbox providers before sending at full volume.
• Mailbox warmup: The same reputation-building process applied to an individual inbox, tracked separately from domain-level reputation.
• SPF (Sender Policy Framework): A DNS record that authorizes specific servers to send email on behalf of a domain.
• DKIM (DomainKeys Identified Mail): A cryptographic signature added to outgoing email that lets receiving servers verify the message wasn't altered.
• DMARC (Domain-based Message Authentication, Reporting and Conformance): A policy record that tells receiving servers what to do when SPF or DKIM checks fail.
• Bounce rate: The percentage of sent emails that fail to deliver, split into hard bounces (permanent failures) and soft bounces (temporary failures).
• Sender reputation: A mailbox provider's internal score of how trustworthy a sending domain or mailbox is, based on engagement, complaints, and bounce history.
• Artificial engagement pool: A warmup method using a network of unrelated inboxes to open, click, or reply to emails in order to simulate real recipient engagement.
• Pre-send validation: Checking an email address's deliverability before sending, to prevent a bounce rather than react to one after it happens.
• Bulk sender: Google and Microsoft's classification for any sender exceeding roughly 5,000 messages a day to their respective platforms, triggering stricter authentication requirements.

Sources

• Google. "Email sender guidelines." support.google.com/mail/answer/81126. Accessed 2026.
• M3AAWG (Messaging, Malware and Mobile Anti-Abuse Working Group). Industry best-practice guidance for email senders. m3aawg.org. Accessed 2026.
• Unify. "Managed Email Deliverability" product page. unifygtm.com/product/deliverability.
• Unify. Deliverability documentation, mailbox configuration. docs.unifygtm.com/deliverability/mailbox-configuration.
• Unify. Deliverability documentation, domain configuration. docs.unifygtm.com/deliverability/domain-configuration.
• Unify. Innovate Energy Group customer story. unifygtm.com/customers/innovate-energy-group.
• Unify. Justworks customer story. unifygtm.com/customers/justworks.
• Unify. CandorIQ customer story. unifygtm.com/customers/candoriq.
• Unify. "How to Set Up a Cold Email Domain." unifygtm.com/explore/cold-email-domain-setup.
• Unify. "2025 Outbound Email Deliverability Guide: 12 Tips to Land in the Inbox." unifygtm.com/explore/2025-outbound-email-deliverability-guide-12-tips-to-land-in-the-inbox.
• Unify. "How to Scale Outbound Prospecting Without Burning Your Domain." unifygtm.com/explore/scale-outbound-prospecting-without-burning-domain.

About the author: Austin Hughes is Co-Founder and CEO of Unify, outbound AI for sellers where AI agents and reps work side by side, from finding the buyers already in market to reaching them with the right message. Before founding Unify, Austin led the growth team at Ramp, scaling it from 1 to 25+ people and building a product-led, experiment-driven GTM motion. Prior to Ramp, he worked at SoftBank Investment Advisers and Centerview Partners.