How to Warm Up an Email Domain for Cold Outreach (90-Day Playbook)

Why Domain Warmup Decides Whether Cold Email Works

Receiving servers at Google, Microsoft, and Yahoo do not trust new domains. A brand new domain with no sending history looks indistinguishable from a throwaway spam domain, so the default treatment is the spam folder or outright rejection. Domain warmup is the process of building enough sending history, engagement, and authentication trust that receiving servers start routing messages to the primary inbox.

The cost of skipping warmup is brutal. Operators who launch cold campaigns from a fresh domain typically see open rates collapse from 60 percent on day one to under 10 percent by day five as spam filters update. The domain reputation takes weeks to recover, and in some cases it never does, which means buying a new domain and starting again.

Warmup also protects the broader business. Cold email shares risk with billing receipts, customer onboarding emails, and password resets if all of it sends from the same domain. A single spam complaint cascade can route transactional mail to spam, which is a much bigger problem than a slow cold campaign. The fix is structural: separate domains, dedicated subdomains, and a controlled warmup curve.

This guide walks through the five steps that turn a new domain into a reliable cold sender, plus the common mistakes that wreck the process. For the wider infrastructure picture covering ESP choice, mailbox provisioning, and rotation, see the companion guide on how to set up cold email infrastructure.

Step 1: Set Up SPF, DKIM, and DMARC Records

Authentication is the foundation. Receiving servers use three DNS records to verify that an email actually came from the domain it claims to come from. Get these wrong and every other step in this playbook fails, no matter how careful the warmup is.

SPF (Sender Policy Framework)

SPF tells the world which mail servers are allowed to send on behalf of the domain. It lives as a TXT record on the root of the sending domain (or subdomain) and lists the authorized IP ranges or hostnames.

For a Google Workspace mailbox on mail.brand.com, the SPF record looks like:

v=spf1 include:_spf.google.com ~all

Use ~all (soft fail) during initial setup, then move to -all (hard fail) once everything is verified. Common mistake: stacking multiple include: statements that breach the 10 DNS lookup limit, which silently invalidates SPF entirely. Use an SPF flattening tool if more than three sending services are involved.

DKIM (DomainKeys Identified Mail)

DKIM cryptographically signs every outbound message with a private key. Receiving servers fetch the matching public key from DNS to verify the signature. Without DKIM, messages can be forged in transit and authentication fails.

Generate a DKIM key inside Google Workspace under Apps, Google Workspace, Gmail, Authenticate email. The console produces a TXT record with a selector (typically google._domainkey) and a long public key value. Publish that record on the sending domain DNS, wait an hour for propagation, then click "Start authentication" in the Google admin console.

For sending volumes above 5,000 messages per day, use a 2048 bit DKIM key instead of the default 1024 bit. The longer key is required by Google and Yahoo bulk sender rules.

DMARC (Domain-based Message Authentication)

DMARC ties SPF and DKIM together and tells receiving servers what to do when authentication fails. It also generates aggregate reports so the sender can see how messages are being authenticated in the wild.

Start with a relaxed monitoring policy on the sending subdomain:

v=DMARC1; p=none; rua=mailto:dmarc@brand.com; pct=100; aspf=r; adkim=r

Run that for two weeks to gather data via the rua reports. Once the reports confirm 100 percent authentication success, tighten the policy to p=quarantine and eventually p=reject. Receivers reward domains with a published reject policy.

To validate setup, use the Mailsfinder deliverability checker which runs SPF, DKIM, and DMARC lookups in one pass and flags common misconfigurations like multiple SPF records or missing DKIM selectors.

Step 2: Use a Dedicated Subdomain for Cold Email

The single most important architectural decision in cold email is to never send cold outreach from the primary brand domain. Cold email carries inherent deliverability risk because prospects mark some percentage of messages as spam. That risk should be isolated.

Subdomain or separate domain

Two patterns work. The first is a subdomain of the main brand:

• Main domain: brand.com (used for billing, transactional, marketing)
• Cold subdomain: mail.brand.com or outreach.brand.com (used only for cold)

The second is a separately purchased domain that visually echoes the brand:

• Main domain: brand.com
• Cold domain: getbrand.com, trybrand.com, or brand-app.com

Both isolate risk. The separate domain pattern goes one step further by isolating DNS, IP allocation, and even billing infrastructure. Most teams running cold at scale use 3 to 10 separate domains, each with multiple mailboxes, rotating sends across them.

Why subdomains share reputation (and why that is fine)

Some operators worry that subdomain reputation bleeds into the parent domain. In practice, receiving servers treat subdomains as related but distinct identities. A spam complaint on mail.brand.com mildly affects brand.com reputation but does not destroy it. Compare that to sending cold directly from brand.com, where a single spam complaint cascade can route billing receipts to spam.

The conservative choice is a separate domain. The pragmatic choice is a subdomain. Either beats sending from the root domain.

Set up the subdomain properly

Create the subdomain at the DNS provider. Add an MX record pointing to the email host (Google or Microsoft). Publish independent SPF, DKIM, and DMARC records on the subdomain itself. Provision mailboxes under the subdomain: harsh@mail.brand.com, sara@mail.brand.com.

Do not forward replies from the subdomain to the main inbox via DNS rules. Instead, manage replies inside the cold email tool or use IMAP forwarding inside the mailbox settings. DNS level forwarding interferes with reply detection in most sequencer tools.

Step 3: Run a Warmup Tool for Four Weeks

Once authentication is published and the subdomain is live, connect the mailbox to a warmup tool. Warmup tools automate the process of building sending history by exchanging realistic conversations with thousands of seeded inboxes inside their network.

How warmup tools actually work

The tool sends a small daily volume of conversational messages from the new mailbox to other mailboxes inside its warmup network. Those recipients open the message, reply, and mark it as important or move it out of spam. Over time, this creates the engagement signals that Google, Microsoft, and Yahoo use to decide whether to trust the sender.

A typical warmup curve looks like:

• Week 1: 5 to 10 sends per day, slowly climbing
• Week 2: 15 to 25 sends per day
• Week 3: 30 to 40 sends per day
• Week 4: 40 to 50 sends per day, mixed with first real cold sends in week 5

The right tool matters less than running one consistently for four full weeks. Cutting warmup short is the most common reason cold campaigns fail. For a deeper review of the leading options, see the comparison of best email warmup tools.

Tool options at a glance

The three categories of warmup tooling are:

• Bundled with sender: Instantly and Smartlead include warmup inside the same platform used for cold sending. Most popular choice for cold email teams.
• Standalone warmup: Mailwarm and Warmup Inbox work with any sender. Useful for teams that want warmup independent of their sequencer.
• Manual warmup: Trading real conversations with colleagues, signing up for newsletters, sending replies from the mailbox. Works for a single mailbox but does not scale.

Warmup signals to monitor

Most warmup tools provide a deliverability score or inbox placement percentage. Watch for:

• Inbox placement above 85 percent across Google, Microsoft, and Yahoo by week 4
• Reply rate from seed accounts above 30 percent
• Zero spam folder placements in week 3 and 4
• Stable or improving trend, not erratic drops

If the warmup score sits below 70 percent at the end of week 4, extend warmup for another 2 weeks before any real cold sends.

Step 4: Ramp Send Volume Gradually

Week 5 is when real cold email starts. The mistake here is the ramp curve. Going from 0 cold sends in week 4 to 200 cold sends in week 5 looks suspicious to receiving servers and triggers spam filtering even on a properly warmed domain.

The six-week ramp schedule

Use this schedule per mailbox:

• Week 5: 20 real cold sends per day. Keep warmup running in the background at 30 sends per day.
• Week 6: 30 cold sends per day. Warmup at 25 per day.
• Week 7: 50 cold sends per day. Warmup at 20 per day.
• Week 8: 100 cold sends per day. Warmup at 15 per day.
• Week 9: 150 cold sends per day. Warmup at 10 per day.
• Week 10 onward: Hold at 150 to 200 cold sends per day. Warmup at 10 per day permanently.

The safer alternative is to cap at 50 cold sends per mailbox per day forever and scale by adding more mailboxes. Three mailboxes at 50 per day each (150 total) is far safer than one mailbox at 150 per day. Both look the same in spreadsheet terms; only one survives the next six months.

Maintain warmup forever

Do not turn off warmup once cold sending starts. The seeded engagement from warmup tools acts as a counterweight to the lower engagement of real cold campaigns. Keep warmup running at 10 to 15 sends per day indefinitely on every active mailbox.

Mix message types

Receiving servers reward variety. During the ramp, alternate between:

• Plain text cold emails to fresh prospects
• Follow up messages on existing threads
• Warmup conversations from the warmup tool

This pattern looks like a real human inbox. A mailbox that sends 100 identical cold emails per day looks like a bot.

Step 5: Monitor Deliverability Weekly

Warmup is not a set-and-forget process. Once the ramp starts, weekly monitoring catches problems before open rates crash. The earliest signals show up in technical dashboards, not in campaign reports.

Google Postmaster Tools

Free, mandatory, and undervalued. Sign up at postmaster.google.com, add the sending domain, and verify ownership via DNS. The dashboard reveals:

• Domain reputation: High, medium, low, or bad. Cold senders should aim for medium or high.
• IP reputation: Tracks the shared IPs used by the email host.
• Spam rate: Percentage of messages marked as spam by users. Critical metric. Stay below 0.3 percent.
• Authentication: SPF, DKIM, DMARC pass rates. Should be at 100 percent.
• Delivery errors: Bounces, rate limit hits, and TLS issues.

Check the dashboard every Monday. If spam rate climbs above 0.3 percent, pause sending the same day and investigate the recent campaigns for content issues, list quality, or targeting drift.

Microsoft SNDS for Outlook deliverability

Microsoft offers a similar tool called Smart Network Data Services (SNDS). It is less polished than Google Postmaster but provides the same core data for Outlook and Hotmail inboxes. Worth setting up if more than 30 percent of the target list uses Microsoft.

List hygiene as a deliverability lever

Spam complaints get the attention, but the silent killer is bounce rate. A bounce rate above 3 percent during warmup can permanently damage the sending reputation. The fix is list hygiene before import, not after sending.

Verify every list through the Mailsfinder email verifier before loading into the sequencer. The verifier removes invalid addresses, catch-all domains, role accounts, and known spam traps. A clean 1,000 address list outperforms a dirty 5,000 address list every time.

Weekly check-in cadence

Block 30 minutes every Monday morning for the following sequence:

• Open Google Postmaster Tools. Screenshot domain reputation, spam rate, authentication.
• Pull weekly campaign metrics from the sequencer (open rate, reply rate, bounce rate).
• Run any new lists added that week through the email verifier.
• Review warmup tool dashboard for inbox placement score.
• Log the numbers in a tracking sheet so trends are visible over time.

This 30-minute habit catches 90 percent of deliverability problems weeks before they become catastrophes. For a wider audit of the tooling that supports this monitoring, see the rundown of best email deliverability tools.

Common Mistakes That Kill the Warmup Process

Most warmup failures fall into the same handful of patterns. Recognizing them in advance saves the domain.

Sending real cold email too early

The most common mistake. Week 1 inbox placement looks fine because spam filters have not yet classified the domain. Founders see the early open rates, conclude warmup is unnecessary, and start sending real campaigns in week 2. By week 3, receiving servers have updated their classifiers and open rates crash. The domain is then half warm and half burned, which is harder to fix than starting fresh.

Using a dirty list during the ramp

A new domain with 5 percent bounce rate looks like a spammer regardless of warmup quality. Receiving servers use bounce rate as a primary signal for sender legitimacy. The fix is to verify every list before sending, no exceptions, especially during weeks 5 through 10 when the domain is most vulnerable.

Sending generic copy

During warmup, spam filters watch for generic templates. "Hi {first name}, I noticed you work at {company}" patterns are flagged within hours. Even during the ramp, use personalized first lines that reference real research, not template variables. The Mailsfinder team has seen domains burned in 48 hours from a single generic blast of 500 messages.

Skipping the subdomain step

"It is just a test" turns into a permanent setup that puts the entire brand domain at risk. Set up the subdomain on day one, even if the first 100 sends look fine on the root domain. The cost is one DNS edit; the upside is permanent isolation.

Trying to scale too fast

One mailbox at 200 sends per day looks ten times more suspicious than four mailboxes at 50 sends per day each. The same total volume produces wildly different deliverability outcomes. Default to more mailboxes at lower volume each.

Ignoring complaint rate spikes

A jump from 0.1 percent to 0.4 percent spam rate looks small but represents a 4x degradation. Receiving servers respond by aggressively filtering the next 14 days of sends. Pause and investigate any spam rate above 0.3 percent immediately.

Treating warmup as one-time

Warmup is not done at week 10. Keep the warmup tool running at 10 sends per day on every active mailbox indefinitely. The day warmup is turned off is the day the deliverability score starts to decay.

Warmup Tool Comparison

Three categories of tooling cover most warmup needs. Each fits a different stage and team setup.

For most teams, Instantly or Smartlead handles both sending and warmup with no extra integration work. Standalone tools make sense only when there is a specific reason to keep the sender separate, like using a custom built sequencer or a non-cold platform such as HubSpot.

What "Warmed Up" Actually Looks Like

The finish line is not a calendar date. It is a set of measurable signals that say the domain has built enough trust to send cold at scale.

By the end of week 10, expect:

• Inbox placement above 85 percent across Google, Microsoft, and Yahoo
• Domain reputation showing as medium or high in Google Postmaster Tools
• Spam rate under 0.2 percent in Postmaster
• SPF, DKIM, and DMARC at 100 percent pass rate
• Bounce rate under 2 percent across the last 1,000 sends
• Open rates above 40 percent on personalized cold campaigns
• Reply rates above 4 percent on well targeted lists

If any of these metrics are off, the domain is not fully warmed. Pause scaling and extend the ramp by another two weeks. The temptation to push through is strong, especially when there is pipeline pressure, but the cost of burning a domain in week 11 is much higher than waiting until week 13.

Putting It All Together: The 90-Day Calendar

Here is the full warmup playbook on a single timeline:

• Day 1: Buy subdomain or separate domain. Publish SPF, DKIM, DMARC.
• Day 2 to 3: Provision mailboxes. Verify authentication via Mailsfinder deliverability checker.
• Day 4: Connect mailboxes to warmup tool. Start at 5 sends per day.
• Week 1 to 4: Pure warmup. No real cold sends. Ramp warmup volume per the curve above.
• Day 28: Confirm inbox placement above 85 percent in warmup tool dashboard.
• Week 5: First real cold sends at 20 per mailbox per day. Verify every list before import.
• Week 5 to 10: Gradual ramp to 150 to 200 sends per mailbox per day.
• Weekly throughout: Monday Postmaster Tools check. List verification. Trend log.
• Day 90: Steady state at full volume. Warmup running at 10 per day permanently.

This is the playbook in its most compressed form. The detailed mechanics live in the five steps above. Follow them in order, do not skip the boring parts, and the domain will be a reliable cold sender for years.