Warm Up a New Domain for Cold Email: 21-Day Ramp

A new domain usually needs 21–28 days before it should carry regular cold email. If you skip authentication, ramp too fast or ignore complaint signals, Gmail and Yahoo can send mail to spam before you learn anything useful. This plan gives you the DNS setup, daily warm-up volume, outreach caps and stop signals to use before scaling.

Use this as the practical version of a domain warm-up plan. If you want the sending, replies and spam rescue handled for you, connect the mailbox to BobWork Email Warm-up after the DNS checks. You can also verify records with the free SPF checker, DKIM checker and DMARC checker before sending.

What should you set first?

Set DNS before warm-up. Warm-up cannot fix a domain that fails authentication.

You need SPF, DKIM and DMARC on the exact sending domain. If you send from jane@try.example.com, check try.example.com, not only example.com.

SPF tells receivers which servers may send for the domain. DKIM signs the message with a private key. DMARC tells receivers what to do when SPF or DKIM does not align.

Start with a simple DMARC policy. For a new cold email domain, p=none is the normal first step. It lets you monitor authentication without asking receivers to quarantine or reject mail while you are still testing.

Google’s sender guidelines set authentication and complaint-rate expectations for Gmail delivery. Google says senders should keep spam complaint rates below 0.10% and avoid reaching 0.30% or higher. Yahoo also publishes sender requirements for authentication and complaint handling.

Primary references:

• Google email sender guidelines
• Yahoo sender requirements
• Google DKIM setup for Workspace

Use one SPF record only. Multiple SPF TXT records on the same host can cause SPF failure. If you use Google Workspace plus a sending platform, merge them into one record.

A typical SPF record can look like this:

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

That example is not universal. Use the includes required by your provider. Check the provider’s current documentation before publishing.

For DKIM, generate the key inside your mail provider or sending platform. Google Workspace users usually go to Admin console → Apps → Google Workspace → Gmail → Authenticate email. Other providers use their own menu paths.

For DMARC, publish a TXT record at _dmarc.yourdomain.com.

A starter record can look like this:

v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com; adkim=s; aspf=s

Strict alignment is useful when the sending domain is stable. If you use several sending services and are not sure about alignment yet, start less strict and tighten after testing.

DNS can appear quickly, but propagation commonly takes minutes to 48 hours. Do not start the ramp until your checks pass.

How should you warm up new domain for cold email?

Warm-up has one job: create a normal sending and receiving pattern before you ask strangers to reply.

A new domain has no sending history. Providers see a sudden jump in outbound volume as risk. That risk increases when the domain sends similar messages, gets few replies, hits invalid addresses or gets marked as spam.

Warm-up does not replace good targeting. It does not make a scraped list safe. It also does not guarantee inbox placement. It helps the mailbox build routine engagement signals and gives you a way to spot problems before full outreach.

BobWork Email Warm-up starts each mailbox at 3 emails per day, adds 2 per day, and caps at 30 per day by default. The cap is editable per mailbox up to 100, but a new domain should not need that early.

Sends are spread between 09:00 and 18:00 in the mailbox’s own time zone. Weekends run at 30% of weekday volume. About 40% of received warm-up mail gets a reply, and threads end after three messages.

The default pool is a shared warm-up network. You can switch to a private pool per account under Mailbox pool → Pool mode. A private pool needs at least two mailboxes. One mailbox is enough in the shared network.

The free pool does the repetitive part automatically: sending short plain-text office notes, replying to some of them, rescuing warm-up mail found in spam, and archiving warm-up threads after 24 hours. It only touches mail with the engine’s own hidden header, or a known subject for Zoho API senders.

Real mail is never read, moved or answered.

If you are new to the mechanics, read what an email warm-up network does before connecting production mailboxes. For a wider ramp, use the email warm-up schedule guide.

What is the 21-day ramp?

This plan assumes a new domain, one to three mailboxes, correct DNS and no previous cold email history.

Use warm-up volume first. Introduce real outreach only after the mailbox has normal activity. Keep campaign content plain. Avoid links, images, heavy tracking and attachments during the first weeks.

The numbers are per mailbox. If you run two mailboxes on the domain, do not simply double the risk without checking the domain-level pattern.

The day-14 gate matters. In BobWork, a mailbox is ready for outbound when it has warmed for 14+ days, has a 7-day warm-up spam rate of 3% or less, and has received at least 30 warm-up emails.

For a new domain, treat that as the earliest possible green light, not a reason to scale hard. A safer plan is to begin small on days 15–21 and keep the full campaign for week four.

If you want a generated version of the ramp, use the free email warm-up schedule generator. It helps you plan dates without guessing the daily steps.

When can outreach start?

The first cold emails should look like normal business mail.

Use one sender identity per mailbox. Do not change display names, signatures, domains and tracking settings every day. Constant changes make it harder to isolate the problem when delivery drops.

Start with the cleanest segment you have. Use contacts that match your audience, role and region. Remove catch-all addresses if you cannot verify them. Avoid old leads, scraped personal addresses and role accounts such as info@ or sales@ during the first test.

Keep early emails short. Plain text is enough. One clear reason for writing is better than a long sequence with links, images, calendar embeds and tracking pixels.

Avoid link-heavy signatures. A logo, five social links and a calendar link create more variables. Add them later after the mailbox has stable results.

Do not send the same message from every mailbox at the same minute. Spread sending through the working day. BobWork spreads warm-up mail between 09:00 and 18:00 in the mailbox’s time zone; use the same idea for real outreach.

A practical ceiling after warm-up is 30–50 real outreach emails per mailbox per day. For a new domain, build towards that slowly. If you need more volume, add mailboxes or domains instead of pushing one mailbox too hard.

Keep warm-up running during campaigns. BobWork’s published practice is to keep warm-up at 10–15 per day during active campaigns. That creates ongoing normal activity without letting warm-up volume dominate the mailbox.

If you use Gmail or Google Workspace, this Gmail warm-up guide gives provider-specific steps. If your new domain uses Google Workspace, also check the Google Workspace spam fix guide.

What signals matter?

The most useful signal is whether receiving mailboxes find your warm-up messages in spam. BobWork measures that directly in the receiving mailbox. It does not use third-party seed lists.

The dashboard shows spam rate as the share of a sender’s warm-up mail found in spam over seven days. Healthy is a health score of 85 or above. Watch is 60–84. At risk is below 60. Blocked means login or permission failed.

Pause a mailbox for a few days if its warm-up spam rate rises above 5%. Do not keep increasing volume while the signal is getting worse.

Do not judge delivery from one test email to yourself. Personal tests are useful for checking whether mail sends, not for measuring reputation.

Avoid changing five things at once. If spam rate rises after you add a tracking domain, new template, new list and higher volume on the same day, you will not know which one caused it.

For a broader diagnosis, use why emails go to spam and the email blacklist checker. A blacklist result is not always the cause, but it is worth checking when a new domain performs badly.

How do you fix problems?

If SPF fails, fix it first. There should be one TXT record beginning with v=spf1 on the sending host. Merge provider includes into that one record.

If DKIM fails, check the selector. BobWork checks common selectors daily, including google, zmail, default, selector1, selector2, k1, s1, mail, dkim, lark, feishu and zoho. If your provider uses another selector, use the selector it gives you.

If DMARC fails, check alignment. The visible From domain must align with either the SPF-authenticated return-path domain or the DKIM signing domain, depending on your setup.

If spam rate rises, stop real outreach first. Keep a low warm-up level, or pause the mailbox if it is above 5%. Review the last change you made. Common causes include:

• Volume jumped too quickly.
• List quality dropped.
• The template added links or heavy tracking.
• Authentication changed.
• The domain is too new for the campaign size.
• Replies are mostly negative.

If bounces appear, suppress bad addresses immediately. A new domain should not be used to test questionable lists. Run small, verified segments first.

If complaints rise, stop sending to that segment. Google’s guidance is clear: keep spam complaint rates below 0.10% and avoid 0.30% or higher. Do not try to average out complaints by sending more mail.

If you change sending infrastructure, warm up again. Moving from one provider to another can change DKIM, SPF, IP pools, headers and routing. Treat that as a new test period.

For provider-specific setup, use the relevant guide: Zoho warm-up, SendGrid warm-up, Mailgun warm-up or Amazon SES warm-up.

What should you do now?

Use this checklist before the first campaign goes out. The goal is not to make the domain perfect. It is to remove obvious reasons for spam placement before you test real prospects.

A new domain does not need aggressive volume. It needs clean authentication, gradual sending, normal replies and fast reaction when the data turns bad.

BobWork Email Warm-up is free for up to 20 mailboxes per account, with no credit card and no time limit. It supports Gmail and Google Workspace, Zoho Mail, Lark Mail, Yahoo Mail, iCloud Mail, Amazon SES, SendGrid, Mailgun and any IMAP plus SMTP mailbox. Outlook and Microsoft 365 are not supported yet.

Set SPF, DKIM and DMARC first. Check the records with the free tools. Then connect the mailbox to BobWork Email Warm-up, let the ramp run for at least 21 days on a new domain, start outreach carefully, and scale only when the signals stay healthy.

Frequently asked questions