How do you warm up a new sending domain safely?

Warm up a new sending domain by publishing SPF, DKIM, and DMARC first, then increasing volume gradually to recipients who actually open and reply. A brand-new domain has no sending history, so mailbox providers treat it with caution until it earns a reputation. The goal of a warmup is not to trick a filter; it is to give each provider a steady, authenticated, low-complaint signal over days and weeks so that reputation forms on real engagement rather than on a sudden burst.

At a glance

Quick takeaways

• Authentication comes first: a domain with no SPF, DKIM, and DMARC has nothing to build reputation on.
• Reputation is earned per sending domain, so a new domain always starts from zero regardless of your company's history.
• Start small and raise volume gradually, sending to your most engaged recipients before anyone cold or dormant.
• Watch the spam complaint rate — Google asks senders to stay under 0.10% and never reach 0.30%.
• A warmup is a controlled sending practice, not a placement guarantee: judge it by real inbox and engagement outcomes.
• Domain reputation and IP reputation are separate; warming a domain does not warm a shared or dedicated IP for you.

Why does a new sending domain need warming up at all?

Mailbox providers score inbound mail partly on the sending domain's reputation, and a domain you registered last week has none. Providers cannot tell a legitimate new business from a spammer's throwaway domain by name alone, so they start cautious: early mail from an unknown domain is more likely to be filtered, rate-limited, or deferred until the domain proves itself.

Warming up means building that proof deliberately. When a new domain sends a modest, steady volume of authenticated mail that recipients open, reply to, and rarely mark as spam, each provider gradually raises the trust it assigns. Skip the ramp and blast tens of thousands of messages on day one, and you hand providers the exact pattern they associate with abuse — which is how new domains land in spam or get deferred wholesale.

Reputation attaches to the domain, not to your company or your other domains. If you have sent successfully from example.com for years and now add mail.example.com or a fresh examplemail.com, the new name still starts near zero. For the wider picture of how providers form these judgments, see what domain reputation is.

What has to be in place before you send anything?

Authentication is a prerequisite, not a later optimization. Publish and verify all three core records before the first message leaves the domain:

• SPF authorizes the servers allowed to send for the domain. Confirm the record with the SPF checker and keep it within the ten-DNS-lookup limit.
• DKIM signs each message so receivers can confirm it was not altered in transit. Validate the published key with the DKIM checker.
• DMARC ties the two together with alignment and tells receivers what to do when a message fails. Start at p=none to observe, then move toward enforcement. Inspect the policy with the DMARC checker.

If you send bulk mail, the current Google and Yahoo requirements make this non-negotiable: any domain sending 5,000 or more messages a day to Gmail is permanently classified as a bulk sender and must pass DMARC with alignment and offer one-click unsubscribe on marketing mail. See the Yahoo bulk sender requirements for the specifics. Run the whole domain through the Email Security Score to confirm the controls are published correctly before you begin.

How should you ramp the volume?

There is no single official timetable, so treat any day-by-day schedule as a starting shape rather than a rule. The principle providers do state is consistent: start low and increase gradually while delivery stays healthy. Google's guidance to senders facing deferrals is to pause, test with a single message, and raise volume only after successful delivery — the same discipline applies to a cold start.

A workable ramp for a new domain looks like this:

1. Days 1–3: send tens of messages a day to internal addresses and your most engaged recipients — people who reliably open and reply. Confirm authentication passes and nothing is deferred.
2. Week 1: grow into the low hundreds per day, still to your most engaged segment. Watch the spam rate and bounce mix.
3. Weeks 2–3: roughly double the daily volume each step as long as complaints stay low and opens hold up. Add progressively less-engaged recipients only once the engaged core is stable.
4. Weeks 4+: continue doubling toward your target volume. Reserve dormant or never-engaged addresses until last, because they generate the most complaints and unknown-user bounces.

Two rules override the schedule. First, if the spam rate climbs or providers start deferring, stop increasing and hold — or step back — until it recovers. Second, ramp per receiving provider: Gmail, Yahoo, and Microsoft form reputation independently, so healthy Gmail delivery does not mean Outlook is ready for the same jump. If your mail already lands well at one provider but not another, the Outlook-versus-Gmail spam guide covers why placement diverges.

What should you measure during a warmup?

Volume is the input; deliverability signals are the output that tells you whether to keep raising it. Track these together rather than trusting any single number:

• Spam complaint rate. The most important guardrail. Google asks senders to keep it under 0.10% and to never reach 0.30%. Enroll the domain in Google Postmaster Tools to read the rate Google itself measures.
• Bounces. Rising hard bounces mean list-quality problems that damage reputation; sustained soft bounces can mean throttling. The soft bounce versus hard bounce guide explains how to read the difference.
• Engagement. Opens and replies from real recipients are the positive signal reputation is built on. Falling engagement as you add volume is a sign you ramped past your genuinely interested audience.
• Authentication pass rates. SPF, DKIM, and DMARC should pass on effectively all mail. DMARC aggregate reports surface any sending source that is failing alignment.

For the broader set of levers behind these numbers, see how to check and improve your email domain reputation and the overview of what email deliverability is.

Common issues with domain warmup

My warmup mail is landing in spam even though volume is low

Low volume alone does not build trust if the fundamentals are missing. Confirm SPF, DKIM, and DMARC all pass and align, that your content is not triggering spam heuristics, and that early recipients are engaged rather than scraped. A clean, authenticated, wanted message at low volume is what earns reputation — quantity cannot substitute for those.

Can I skip the ramp by using an automated warmup service?

Automated warmup tools exchange messages between mailboxes to simulate engagement, but that traffic is not your real audience and providers increasingly discount or penalize it. It can measure a health signal, but it does not prove that your actual campaigns will reach the inbox. For an honest look at the limits, read does email warmup work.

How long does warming up a new domain take?

Plan for several weeks to reach a steady state, longer for high target volumes. The timeline is driven by how fast you can raise volume while keeping complaints low and engagement high — not by a fixed calendar. If signals degrade, the safe response is to slow down, which extends the schedule.

Do I need to warm up the IP address too?

Domain reputation and IP reputation are tracked separately. On a shared IP pool run by an email platform, the IP may already be warm, but your domain still starts cold. On a dedicated IP, you are warming both at once, which is slower and less forgiving. Know which model your sending platform uses before you plan the ramp.

How does Palisade fit into a domain warmup?

A warmup only works on top of correct authentication, and getting SPF, DKIM, and DMARC published and aligned across every sending source is where new domains most often stall. Palisade automates that layer — deploying and monitoring the DNS records and reading the DMARC aggregate reports so you can see, source by source, whether the mail you are ramping is actually authenticating. Before your first send, run the domain through the Email Security Score to confirm the foundation is in place; the warmup is what you do once that check is green.

Related reading

• Does email warmup work?
• How can you check and improve your email domain reputation?
• What is email deliverability?