How to Warm Up an Email Domain
Without Landing in Spam
A new sending domain has no reputation. Send too much too soon and inbox providers will filter or block your mail. This guide covers the week-by-week warming schedule, safety thresholds and how NexusProMail automates the entire process.
Quick Answer
Domain warming is the process of gradually increasing email send volume from a new sending domain to build inbox reputation. Inbox providers use sending history to judge whether mail is wanted — a cold domain sending thousands of emails immediately looks like spam. A controlled ramp over 6–8 weeks, starting at 200/day, builds the history needed for reliable inbox placement.
Key Takeaways
- Inbox providers assign domain reputation based on sending history — a new domain has no history and no trust
- Skipping warming and sending high volumes immediately causes widespread filtering or rejection by Gmail and Outlook
- Safe thresholds during warming: hard bounce rate below 2%, spam complaint rate below 0.08%
- If either threshold is breached, pause immediately — do not continue sending until list quality is resolved
- NexusProMail applies a controlled ramp schedule automatically and pauses if safety metrics are exceeded
What Is Domain Warming and Why Does It Matter?
Inbox providers — Gmail, Microsoft Outlook, Yahoo and others — use sending history to make filtering decisions. A domain that has never sent email before and suddenly sends 10,000 messages in a day looks indistinguishable from a spam operation. The result: bulk filtering, deferral or outright rejection.
Domain warming is the deliberate process of building that sending history gradually. You start at low volume, send to your most engaged contacts, and increase volume on a controlled weekly schedule. Over 6–8 weeks, inbox providers build a positive signal about your domain and you can send at full volume with reliable inbox placement.
The two metrics that define whether your warm is progressing safely are hard bounce rate (keep below 2%) and spam complaint rate (keep below 0.08%). Exceed either and volume must stop until the root cause — usually list quality — is resolved.
Domain Warming Schedule — Week by Week
Conservative benchmarks used as a starting point. Accelerate only if bounce and complaint rates are within safe thresholds. Pause and roll back one week if either metric is breached.
| Week | Daily Max | Weekly Total | Bounce Limit | Complaint Limit | Guidance |
|---|---|---|---|---|---|
| Week 1 | 200 | 1,400 | < 3% | < 0.10% | Highly engaged contacts only |
| Week 2 | 500 | 3,500 | < 2.5% | < 0.10% | Continue with engaged segment |
| Week 3 | 1,000 | 7,000 | < 2% | < 0.09% | Introduce warmer portions of list |
| Week 4 | 2,500 | 17,500 | < 2% | < 0.09% | Monitor complaint rate closely |
| Week 5 | 5,000 | 35,000 | < 1.5% | < 0.08% | Expand to broader list segments |
| Week 6 | 10,000 | 70,000 | < 1.5% | < 0.08% | Full ramp for most senders |
| Week 7 | 20,000 | 140,000 | < 1% | < 0.08% | Scale to target volume |
| Week 8 | 40,000 | 280,000 | < 1% | < 0.08% | Full send volume unlocked |
How to Warm a Domain: 5 Steps
Authenticate your sending domain
Set up DKIM, SPF and DMARC records for the domain you plan to warm. Without proper authentication, inbox providers will reject or heavily filter your mail regardless of warming progress. Verify all three records are correct before sending a single email.
Prepare a clean, engaged seed list
Start warming with only your highest-engagement contacts — people who opened or clicked in the last 30–90 days. High engagement in the first weeks signals inbox providers that recipients want your mail. Avoid cold lists, purchased lists or any addresses not recently active.
Send at controlled low volume, then ramp weekly
Begin at 200 sends per day in Week 1. Double or 2.5× volume each week, following the schedule above. Never jump volume more than 3× in a single week. Consistency matters: sending on a predictable daily cadence is better than batching a week's volume into one send.
Monitor bounce rates and complaint rates daily
Hard bounce rate should stay below 2% throughout warming. Spam complaint rate must stay below 0.08%. If either metric breaches its threshold, pause sending immediately for 48–72 hours and investigate list quality before resuming. Do not accelerate volume after a pause — resume at the previous week's level.
Expand to the full list only after 6–8 weeks
Once your domain has 6–8 weeks of consistent, low-complaint sending history and you are reaching your target daily volume with stable inbox placement, you can introduce colder list segments. Continue monitoring. Domain reputation is maintained, not earned once — high bounce or complaint rates will damage a warm domain too.
NexusProMail Warms Your Domain Automatically
Managing a warming schedule by hand — tracking daily limits in a spreadsheet, manually pausing when bounce rates spike — is error-prone and distracting. NexusProMail's built-in warming engine handles the entire process.
Add a new sending domain and the engine applies a controlled ramp schedule automatically. It monitors bounce rate, complaint rate and engagement in real time. If any threshold is exceeded, volume is paused and you are notified — no manual intervention needed.
All deliverability features →Automated ramp schedule
Starts at 500/day and increases weekly following safe benchmarks.
Auto-pause on threshold breach
Stops sending immediately if bounce or complaint rate exceeds safe limits.
Hard bounce suppression
Every hard bounce is automatically added to your suppression list — protecting reputation without manual action.
Warming status dashboard
See current phase, daily volume, bounce/complaint trends and estimated completion date.
DKIM/SPF/DMARC monitoring
Authentication records are checked continuously. You are alerted if any record is missing or broken.
5 Warming Mistakes That Damage Sender Reputation
✗ Sending to the full list on day one
Start with 200/day. Use only recent high-engagement contacts for the first two weeks.
✗ Doubling volume every day
Volume should increase weekly, not daily. Sudden spikes trigger spam filters even on warm domains.
✗ Ignoring bounce and complaint rates
Check both metrics after every send during warming. A spike is a stop signal, not a speed bump.
✗ Warming without proper authentication
DKIM, SPF and DMARC must all be correct before the first send. Authentication failures override reputation.
✗ Resuming at previous high volume after a pause
After a pause, resume at the previous week's level — not where you stopped. Let reputation recover first.
Domain Warming FAQ
What is domain warming?
How long does domain warming take?
What happens if I skip domain warming?
What send volumes should I use each week?
Does NexusProMail handle domain warming automatically?
What is a safe bounce rate during warming?
Should I warm my IP address and my domain separately?
What email content should I use during warming?
Let NexusProMail warm your domain for you
Built-in warming engine. Automatic pause on threshold breach. Deliverability monitoring on every plan.
Also read: Email deliverability guide · API integration guide · Transactional email API · GDPR email compliance