To warm up a new email domain, authenticate it, send a small batch to people who expect your email, and increase volume as delivery results stay healthy. Check bounces, complaints, and delays before each increase.
Your domain is verified, the email template is ready, and you have a list of people waiting to hear from you. Sending the whole list at once is tempting, especially when a launch date is close. A gradual rollout gives you time to catch a problem before you send to the rest of the audience.
What is domain warming?
Domain warming is the process of building a sending history by gradually increasing email volume from a domain. Mailbox providers use domain reputation, along with other signals, to decide how to handle your email.
A new sending domain has little email history. Mailbox providers still have to learn how recipients respond to your mail. Correct DNS records help them verify who sent it, but authentication alone cannot guarantee an inbox placement.
If emails from your new domain are going to spam, check authentication and audience quality before raising volume. Warming gives you a controlled way to introduce traffic and learn from the results. It cannot compensate for broken DNS records or email recipients do not want.
Get the domain ready before the first send
Set up SPF, DKIM, and DMARC before you start warming. Then send a real email through the same path your application will use and inspect its authentication results. A domain verification badge is useful, but you also need to know that the email arriving at the other end passes.
DMARC checks whether a domain authenticated through SPF or DKIM aligns with the domain in your visible From address. If those identities do not align, sending more email will not fix the configuration. Our email authentication guide walks through the records and how they fit together.
Choose a sending identity you intend to keep. Use a recognizable sender name and a reply address someone checks. For promotional email, test the unsubscribe link and make sure an opt-out removes the recipient from future promotional sends. Set up one-click unsubscribe where bulk-sender requirements apply.
You can also separate product notifications and promotional email onto different subdomains, such as notify.example.com and news.example.com. That makes it easier to track each stream and control its volume. Treat each new subdomain as a sending identity that needs observation; sharing a parent domain does not guarantee the same delivery results.
Start with people who expect the email
For a product announcement, begin with subscribed customers who recently used the feature you are writing about. For a newsletter, choose recent subscribers who know what they signed up for. Make the first email useful on its own.
Keep old, inactive contacts out of the initial audience. An address in your database does not tell you whether its owner still wants the email. Remove known invalid addresses and honor previous unsubscribes and complaints before selecting a batch.
Suppose you are introducing a new reporting feature. A sensible first audience is customers who requested it and subscribed to product updates. You can check how that send performs before expanding to other interested subscribers. Sending the announcement to every account ever created gives you much less control over the rollout.
Avoid sending extra email solely to fill a warmup quota. The audience's reason to receive it should determine what you send.
Build an email warmup schedule
Start with a small portion of your intended audience and spread the send over time. Review the results before increasing the next batch. Gmail's sender guidance recommends gradual increases, consistent sending rates, and reducing volume when bounces or deferrals appear.
A useful warmup plan records the audience for each batch, its planned volume, and the conditions for increasing it. You can organize the work into stages:
| Stage | What to send | What to check before expanding |
|---|---|---|
| Verify the setup | Test emails through your production sending path | Authentication passes, links work, and the sender is recognizable |
| Establish a baseline | A small batch to recent, interested subscribers | Delivery results and recipient feedback give you a baseline to compare against |
| Expand gradually | More recipients with the same reason to expect the email | Bounces, complaints, and delays remain low as volume grows |
| Reach normal volume | The audience and cadence you intend to maintain | Delivery remains stable across repeated sends at that volume |
Set aside time to review each batch. If your plan increases volume automatically regardless of what happened yesterday, it leaves out the decision that makes warming useful.
For each send, record the date, recipient segment, receiving provider, planned volume, and actual delivery results. Add a decision for the next batch: increase, hold, or reduce. This turns the schedule into a working record you can adjust as you learn.
Check results by receiving provider where your tooling allows it. A healthy overall delivery rate can hide trouble with one part of your audience. Hold back expansion to an affected provider while you investigate its responses.
Keep other changes small during the ramp. Changing the sender address, audience, and email format at the same time makes a delivery problem harder to diagnose. Record what changed so you can compare the next send with the previous one.
Do transactional emails need domain warmup?
Transactional email needs the same authentication and delivery monitoring. The rollout depends on whether you are starting with modest customer-triggered traffic or moving an established, high-volume stream to a new domain.
A password reset needs to arrive while the customer is trying to sign in. Holding it until tomorrow to satisfy a daily warmup schedule defeats its purpose.
For a new product with modest traffic, send transactional email when customers trigger it and monitor delivery from the start. Do not manufacture password resets or receipts to reach a target volume. Plan the rollout around actual product use.
An established product moving a busy email stream to a new domain needs more preparation. Where your setup permits it, move a small portion of traffic first and expand after checking results. Keep the existing sending path available during the transition so a delivery problem does not leave you without a working option.
Schedule broad announcements separately from essential account email. Our guide to transactional and marketing email explains how to distinguish the streams.
Monitor domain reputation and delivery results
Delivery results should decide your next step. Pay attention to the failure reason as well as the count.
- Hard bounces indicate permanent delivery failures. Suppress invalid addresses and investigate a rise before adding more recipients.
- Deferrals mean the receiving server has temporarily declined delivery. Read the response; rate limiting and authentication problems need different fixes.
- Complaints mean recipients marked the email as spam. Revisit the audience and the email's relevance before continuing the ramp.
- Reports of missing email deserve investigation even when your dashboard shows successful delivery. Acceptance by a receiving server does not confirm inbox placement.
For Gmail traffic, Postmaster Tools provides another view of delivery health. Low-volume days may have missing data, so an empty dashboard is not evidence that everything is fine. A low reported spam rate can also hide filtering when fewer emails reach the inbox in the first place.
Google recommends keeping the user-reported spam rate below 0.1% and avoiding 0.3% or higher. Read that figure in Postmaster Tools; a complaint percentage in your sending platform may use different data and a different denominator.
When results worsen, stop expanding. Reduce the affected traffic and investigate the cause. After you fix it, resume cautiously and compare subsequent sends. A calendar reminder is no reason to increase volume while delivery is deteriorating.
How long does domain warmup take?
There is no fixed number of days that makes a domain ready for full volume. Plan around reaching stable delivery at your normal sending volume. A small product sending occasional account notifications has a different task from a service moving a large daily audience to a fresh domain.
Leave room in your launch plan to hold a batch or reduce volume. You may need to correct authentication, remove unsuitable recipients, or investigate a receiving provider's response before continuing. Avoid tying a full-list announcement to a fixed day in the warmup schedule.
Once you reach normal volume, keep monitoring. A long pause followed by a large campaign deserves the same care as your initial ramp. Warming does not grant permanent permission to send any amount of email.
Domain warmup vs. IP warmup
Domain warmup builds a history for your sending domain. IP warmup introduces traffic through a sending IP address. Mailbox providers can evaluate both, so an established IP does not remove the need to monitor a new domain.
If you send through a shared IP pool, your email provider manages the shared sending infrastructure. Focus your own ramp on your domain and recipients. If you are introducing a dedicated IP, coordinate its warmup with your provider alongside the domain rollout.
Put safeguards around the ramp
Your sending platform should help you act on delivery problems. In Samva, bounce and complaint rates can trigger an automatic pause on workspace sending, giving you room to investigate before continuing. These deliverability controls support the decisions you make as your audience grows.
Before your next send, check your authentication records, choose an audience that expects the email, and decide which results would make you pause. That gives you a plan you can use when the first batch comes back with something unexpected.
