How to Warm Up a New Email Sending Domain

The short answer
Warm up a new email domain by publishing SPF, DKIM and DMARC before your first send, then sending small volumes to your most engaged recipients and increasing gradually as replies and low complaints allow. Plan for two to eight weeks; engagement, not a fixed calendar, sets the safe pace.
How to warm up a new email domain: publish SPF, DKIM and DMARC first, then grow volume from your most engaged recipients as replies allow.
On this page
A brand-new sending domain has no reputation with mailbox providers, so its first messages are treated with suspicion. Learning how to warm up a new email domain means building that reputation on purpose: prove you send wanted mail, in rising volume, before you send at scale.
Most warmup guides hand you a day-by-day volume table. Those numbers are guesses. What actually moves your reputation is who opens and replies, not how many messages you push on day nine. This guide ramps by engagement, not by the calendar.
Skip warmup and you risk more than a slow start. Once a provider files your mail as spam — or classifies your domain as a bulk sender — that judgement is hard, and sometimes impossible, to undo.
Before you start: authentication and a clean list#
Before the first send, publish email authentication in DNS. Providers check it on message one, so it has to be live first, not bolted on later.
At a minimum, publish SPF and DKIM for your sending domain, then a DMARC record. Google requires SPF or DKIM for every sender, and SPF, DKIM and DMARC together once you send more than 5,000 messages a day to personal Gmail accounts. Microsoft applies the same three to high-volume senders to Outlook.com, Hotmail and Live (as of 2026).
Decide what the domain is for before you ramp. A domain sending transactional mail — receipts, password resets — warms differently from one built for cold outreach or marketing, because the recipients and the engagement look different. Match your warmup list and volume to that goal from day one.
- SPF: lists the servers allowed to send for your domain.
- DKIM: signs each message so the recipient can verify it was not altered in transit.
- DMARC: tells providers what to do when SPF or DKIM fail, and where to send reports.
- A monitored postmaster address and a real, human reply-to address on the domain.
DMARC: start in monitoring mode
How long does domain warmup take?#
There is no official timeline from Google, Yahoo or Microsoft. In practice, plan for two to eight weeks. A domain sending a few hundred messages a day to an engaged list can settle in roughly two weeks; one ramping toward tens of thousands takes longer.
Three things set the pace. A clean, opted-in list warms faster than a cold one; a modest target volume warms faster than a huge one; and consistent daily sending warms faster than stop-start bursts. Get those right and the low end of the range is realistic — get them wrong and no schedule saves you.
Treat the calendar as a floor, not a schedule. If complaints climb or replies dry up, you slow down or pause. The domain tells you when it is safe to push more — the plan does not.
How to warm up a new sending domain, step by step#
With authentication live and a goal set, the ramp itself is six repeatable moves. Do them in order, then repeat the last three every day until you reach your target volume.
- 1
Publish authentication and verify it passes
Add SPF, DKIM and DMARC, send one test message, and confirm all three pass in the received headers before any real send.
- 2
Start with your most engaged recipients
Send the first batches to people who know you and reply — teammates, existing customers, opted-in subscribers. Positive engagement is the signal providers weight most.
- 3
Send small and consistent
Begin with a low daily volume and send every day rather than in bursts. Steady, predictable sending reads as legitimate; a sudden spike reads as someone who just bought a domain to spam from.
- 4
Grow volume gradually, gated by engagement
Raise the daily count only while opens, replies and low complaints hold. A common rule of thumb is to roughly double every few days — but slow down the moment the numbers wobble.
- 5
Monitor reputation with the free tools
Enrol in Google Postmaster Tools and Microsoft SNDS. Watch your spam-complaint rate, authentication pass rate and any reputation score every day during warmup.
- 6
Prune and segment as you scale
Remove hard bounces and unengaged addresses before you add fresh recipients. Warmup fails fastest when you pour a stale or scraped list onto a young domain.
Send to people, not seed lists
Warmup by mailbox provider#
The core moves are the same everywhere, but the thresholds and the penalties differ. These are the numbers that matter during a ramp, as of 2026 — check each provider's own page before you rely on them, because they change.
| Provider | Bulk-sender threshold | Authentication required | Watch this during warmup |
|---|---|---|---|
| Gmail | ~5,000/day to personal Gmail accounts — counted per primary domain (subdomains included) and permanent once set | SPF + DKIM + DMARC; one-click unsubscribe on bulk marketing | Spam rate in Postmaster Tools: keep under 0.1%, never reach 0.3% |
| Outlook.com / Hotmail / Live | 5,000/day (enforced from 5 May 2025) | SPF + DKIM + DMARC, aligned; DMARC at least p=none | Non-compliant bulk mail routed to Junk, with outright rejection signalled to follow |
| Yahoo / AOL | 5,000/day (bulk sender) | SPF + DKIM + DMARC; one-click unsubscribe | Complaint rate; follow the Yahoo Sender Hub guidance |
| Any provider | No single number | SPF, DKIM and DMARC live before the first send | Bounces, complaints and replies — the universal signals |
Gmail's bulk-sender status is permanent
What to do when warmup isn't working#
If deliverability drops mid-warmup, stop increasing volume. Diagnose before you send more — pushing harder into a reputation problem only deepens it. Recovery is usually possible if you catch it early, pause, and fix the underlying cause.
- Mail landing in spam: confirm SPF, DKIM and DMARC all pass and align. A single failing check can sink an otherwise healthy domain.
- Rising complaint rate: you are mailing people who did not ask. Cut back to your most engaged segment and slow the ramp.
- Bounces climbing: your list is stale or scraped. Verify addresses and remove hard bounces before the next batch.
- A sudden block after a good start: you probably spiked volume too fast. Return to the previous day's volume and hold there for several days.
- Tempted to start over: rebuild, don't restart. A fresh domain only resets the reputation, not the mistake — the same list and habits will burn the new one just as fast.
The receiving side: where AI Emaily fits#
Warmup is entirely a sending-side job, and AI Emaily is not a sending tool. We are not an email service provider, a warmup service or a deliverability tester, and we do not send bulk mail — so if you need to send from a new domain, a reputable ESP that handles authentication and paces volume for you is the faster route.
What AI Emaily does is the other end of the same problem. Every message you warm up toward has to survive a recipient's filters, and those filters judge sender behaviour and engagement — exactly what warmup works to earn. AI Emaily's spam protection and cold-email filter make that call on the receiving side, sorting wanted mail from noise by how a sender behaves rather than by raw volume. If you want to see the criteria your warmup is trying to satisfy, that is the job we do. We build AI Emaily.
Frequently asked
See it in AI Emaily
Keep reading
Sources

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.