# Warming up a brand-new sending domain

> A new domain has no reputation, which filters treat with suspicion. Authenticate first, start with your most engaged recipients and grow steadily.

- Published: 2026-09-18
- Author: Koltrix Team
- Category: Deliverability
- Source: https://koltrix.com/blog/new-domain-warm-up

You registered a fresh domain for a new product, or decided to move your mail off the domain everyone already knows. Your sending provider's IPs are warm, your DNS is correct, and messages still land in spam.

A new domain has no history, and receivers judge domains as much as they judge IPs.

## Why a new domain needs warming

Modern spam filtering ties much of its reputation data to authenticated domains. Once a receiver can verify through DKIM and DMARC that a message comes from `example.com`, it builds a history for that domain: how much it sends, how recipients react, whether it hits spam traps. That history follows the domain across IPs and providers.

A domain with no history has nothing to vouch for it. Worse, newly registered domains are a favorite tool of spammers and phishers, who register, burn and discard them. Many filters therefore treat a young domain with extra caution regardless of which IP it sends from.

Domain warm-up is different from IP warm-up. On a shared pool, the IP side is already handled. What you are building is the domain's own track record.

## Step 1: get authentication perfect first

A new domain cannot afford ambiguous signals. Before sending any real mail:

- **SPF** authorizes your sending provider for the envelope sender domain.
- **DKIM** signs with your new domain (`d=newdomain.example`), using a 2048-bit key.
- **DMARC** is published, at least `p=none`, with aggregate reports flowing to a mailbox you read.
- **Alignment** works: the From domain matches the DKIM domain, or the SPF domain under relaxed alignment.
- **MX records** exist and the domain can receive mail. Replies and bounces need somewhere to go, and some receivers check that a sender domain accepts mail.
- **A website** on the domain explains who you are. Some filtering systems look at whether a domain has a real web presence.

Gmail and Yahoo require all of this from bulk senders, and Microsoft requires SPF, DKIM and DMARC for high-volume senders to Outlook.com. There is no reason to start a new domain without it.

## Step 2: let the domain age a little

There is a widely held view among deliverability practitioners that domains registered only days ago are treated more skeptically than domains a few weeks or months old. Receivers do not publish the details, but if you control the timing, register the domain and set up DNS, a website and a mailbox some weeks before you need to send volume from it. At minimum, do not register a domain on Monday and launch a 100,000-recipient campaign from it on Tuesday.

## Step 3: start with mail people want and expect

The first messages from a new domain should be the ones most likely to be opened and least likely to be reported:

- Transactional mail: receipts, password resets, account notifications.
- Replies to people who emailed you.
- Messages to recipients who opted in recently and recognize your brand.

Avoid starting with cold outreach, re-engagement campaigns to old lists or large newsletters. Those carry the highest complaint and spam trap risk.

## Step 4: ramp volume over weeks

A sensible approach for a domain that will eventually send tens of thousands of messages a day:

| Week | Daily volume from new domain | What to send |
|---|---|---|
| 1 | Low hundreds | Transactional mail and highly engaged recipients |
| 2 | Up to a few thousand | Add recent opt-ins |
| 3 | Up to around 10,000 | Engaged subscribers from the last 60 to 90 days |
| 4 and beyond | Grow toward full volume | Wider active audience, still excluding long-inactive addresses |

These are not official figures; no provider publishes a domain warm-up table. Use them as a shape and adjust to what you observe.

## Step 5: if you are migrating from an old domain

Moving mail from an established domain to a new one throws away the old domain's reputation. If you must do it, for a rebrand for example:

- **Run both in parallel.** Keep sending most mail from the old domain while the new one ramps, and shift streams over gradually.
- **Move the best stream first.** Transactional mail builds the new domain's reputation fastest.
- **Tell recipients.** A brief notice from the old domain that mail will start coming from the new one reduces "who is this?" complaints.
- **Keep the old domain authenticated.** Do not let SPF, DKIM or DMARC lapse on the old domain; it can still be spoofed, and replies will still arrive.

## Consider a subdomain instead

If the new domain exists mainly to separate a mail stream, you may not need a new domain at all. A subdomain such as `news.example.com` starts with its own domain-level history but benefits from its relationship to an established parent. Many receivers consider the organizational domain when evaluating a subdomain, though the exact behavior is not published. For stream separation, a subdomain is usually the better tool; a brand-new registered domain is for genuinely new brands.

## What to monitor

- **Google Postmaster Tools:** verify the new domain early so you can watch spam rate and authentication data as soon as volume is high enough to appear.
- **DMARC aggregate reports:** confirm that every message passes with aligned DKIM.
- **Placement:** check where mail lands in a few personal test mailboxes, and watch engagement rates by receiving provider.
- **Complaints and bounces:** both should be very low on a new domain sending to engaged recipients. A spike means the audience widened too fast.

## Common mistakes

- **Launching big on day one.** A large first campaign from an unknown domain is the classic pattern filters are built to catch.
- **Cold outreach from a fresh domain.** It combines the highest-risk content with the lowest trust.
- **Skipping DMARC because the domain is "just for marketing."** Bulk sender rules apply regardless.
- **No inbound mail.** A domain that cannot receive replies looks less legitimate and loses useful feedback.
- **Hopping domains to escape bad reputation.** Receivers increasingly recognize the pattern, and the underlying behavior follows you.

## Checklist

- SPF, DKIM with your new domain, DMARC with reports, and alignment verified.
- MX records and a real website on the domain.
- Some lead time between registration and volume sending, where possible.
- First sends limited to transactional mail and highly engaged recipients.
- Volume ramped over several weeks.
- Postmaster Tools and DMARC reports watched from day one.

## Bottom line

A new domain starts with no reputation and with the suspicion that comes from being young. Authenticate it perfectly, give it a real presence, start with mail people expect, and grow volume over weeks. If all you need is stream separation, a subdomain of an established domain is usually the faster path.
