To warm up a new email domain: register it a few weeks before you need it and park it with valid MX records, publish SPF, DKIM (2048-bit) and DMARC in that order, then let warmup ramp from 4 messages a day on day 0 to 50 by day 30 before you rely on the mailbox. When you start cold sending, begin low and grow cold volume gradually.
On this page
A fresh domain is a blank slate, and not in the way most founders hope. Gmail, Outlook, and Yahoo all treat domains under 30 days old with deep suspicion, and any single misstep in the first two weeks can attach a negative reputation that sticks for months. The fix is not magic, it is patience, plus a handful of technical steps performed in the right order.
This piece walks through how to warm a new domain from purchase to first cold campaign without tripping the bulk-sender heuristics that send most rookies to the junk folder.
Give a new domain time to settle#
A brand-new domain has no sending history, and mailbox providers treat that with caution. Warmerly's own ramp counts days spent warming, not domain age. A domain registered yesterday with a perfectly tuned DMARC record will still be filtered more aggressively than a five-year-old domain with a sloppy SPF record. If you have the option, buy your sending domains two to three weeks before you need them. Park them with valid MX records pointing at your mail provider and let the WHOIS age tick over.
Avoid buying expired domains for outreach. They carry the reputation of whoever sent from them last, and that history is opaque to you. A clean new registration beats a cheap aged domain with mystery baggage.
The authentication checklist, in order#
Configure these before a single warmup message leaves your mailbox. Order matters because DMARC alignment depends on SPF and DKIM passing, and any reordering creates false positives in your reports.
- MX records pointing at your mail provider. Confirm with dig MX yourdomain.com.
- SPF as a single TXT record at the apex. Keep DNS lookups under 10. End with ~all in production.
- DKIM with a 2048-bit key, published at the selector your provider issues (often google._domainkey or selector1._domainkey).
- DMARC at _dmarc.yourdomain.com starting at p=none with rua reporting to a mailbox you actually read.
- MTA-STS policy file at https://mta-sts.yourdomain.com plus the corresponding TXT record. Gmail and Microsoft increasingly use this as a maturity signal.
- TLS-RPT at _smtp._tls.yourdomain.com so you find out when TLS negotiation fails with a partner.
- A reverse DNS (PTR) record on the sending IP, if you control it. Shared-pool senders skip this.
Once the records are live, send a single message to a Gmail address you control and open the original headers. SPF, DKIM, and DMARC must all read PASS. Alignment mode matters too: strict alignment means the From header domain must exactly match the SPF and DKIM domains, while relaxed permits an organisational match. Most cold senders are fine on relaxed, but know which you have configured.
Warmerly's ramp, day by day#
The single biggest mistake new senders make is ramping volume too fast. Receivers do not just look at total volume, they look at the rate of change. A spike from a handful of sends to dozens in a single day looks like a compromised account, even if the absolute numbers are tiny.
Warmerly's ramp for every mailbox, brand-new domain or not, looks like this:
- Day 0: 4 warmup messages a day.
- Day 3: 8 a day.
- Day 7: 15 a day.
- Day 14: 25 a day.
- Day 21: 35 a day.
- Day 30: 50 a day.
Between those points the number rises in small steps, so there are no sudden jumps. The count runs on the days a mailbox has actually been warming, not on calendar age or domain age, and there are no presets to pick from. If the health score or spam placement slips, that day's volume is cut back. A Gmail mailbox has a ceiling of 40 warmup messages a day, so the later steps are held at 40. An Outlook or Microsoft 365 mailbox has a ceiling of 30 warmup messages a day, so the later steps are held at 30.
New-domain timeline: before day 0, register the domain, park it and publish SPF, DKIM and DMARC; then Warmerly's ramp runs day 0, 4 warmup messages a day; day 3, 8; day 7, 15; day 14, 25; day 21, 35; day 30, 50.
These figures assume one mailbox. If you run multiple mailboxes on the same domain, the per-mailbox volume stays the same but the domain-level total grows, and Gmail watches domain totals at least as closely as per-mailbox ones.
Is your email warmup going too fast? Signs of trouble and what to do#
The most common way senders answer this for themselves the hard way: volume jumped several times over within a week, then soft bounces started arriving from Hotmail and Outlook.com. That pattern is not a coincidence. A jump that size in a few days reads as reputation throttling kicking in, not a fluke. If your send count more than doubled in under a week, treat that alone as a yes.
Beyond the volume jump itself, catch problems early and you can pull the ramp back before reputation calcifies. Watch these signals daily:
- Volume more than doubled week over week. This is the single fastest way to trip filters, independent of the absolute numbers.
- Gmail Postmaster domain reputation dropping from High to Medium. Pause cold sends for 48 hours, keep warmup running.
- Spam-folder rate above 8% in your warmup tool. Reduce volume by half and audit content for link-to-text ratio.
- Soft bounces from Microsoft domains (Hotmail, Outlook.com, Live) clustering together. This is Microsoft's earliest and softest throttling signal, and it usually shows up before Gmail reacts.
- Bounce rate above 2% on cold sends. Stop sending and re-verify your list.
- Complaint rate (Postmaster feedback loop) above 0.10%. This is the line at which Gmail accelerates filtering.
- Sudden absence of DMARC aggregate reports from a previously-reporting provider. Often means your messages stopped passing alignment.
If two or more of these trip in the same week, your domain is in trouble. Stop cold sending entirely, hold or reduce warmup volume back to the last stable level for at least 14 days, and only resume ramping when Postmaster reads High and your warmup health score sits above 80. Resuming at the same aggressive pace that caused the problem just repeats it.
Extra patience at the start saves months of recovery later. Treat the first weeks of a new domain like onboarding, not a launch.
Most warmup tools, Warmerly included, will automate the day-by-day cadence above and surface the warning signals on a single dashboard. Whichever tool you pick, the underlying principle does not change: domains earn trust slowly, and lose it quickly.