# Email Sending Domain Warm-Up: FAQ for Teams Starting From Zero > Answers to the most common questions about warming up a new email sending domain — timelines, volume ramps, authentication, and what to do when things go wrong. - **Published:** 2025-08-19 - **Author:** Clixo - **Reading time:** 5 min read - **Tags:** domain-warmup, deliverability, email-infrastructure, sending-reputation - **Canonical URL:** https://clixo.sh/blog/email-sending-domain-warmup-guide A new sending domain or IP address has no reputation with major email providers. Inbox providers use reputation as a key signal in their filtering decisions, and a domain with no history is treated with suspicion. Send too much too fast from a cold domain, and a meaningful fraction of your mail will land in spam — or get rejected entirely. Warming up a domain is the process of building a positive sending reputation gradually, through consistent sending behavior to an engaged audience. These are the questions teams most commonly have about the process. ## Why does a new domain need to be warmed up? Inbox providers evaluate the reputation of the sending domain and IP address to decide where to deliver each message. Reputation is built from behavioral signals over time: how often your mail gets opened, how rarely it gets marked as spam, whether you maintain clean lists. A brand-new domain has none of this history. From the receiving server's perspective, a new domain suddenly sending thousands of messages is indistinguishable from a spammer who registered a fresh domain to evade an existing block. Warming up communicates that your sending is legitimate and consistent, through a track record of clean, well-received mail. ## How long does a domain warm-up take? Typically four to eight weeks for a new domain, assuming you follow a disciplined ramp schedule and send to engaged contacts throughout. The timeline depends on: - **Target volume:** Higher target volumes take longer to ramp to safely - **List quality:** Warm-up goes faster when your recipients are engaged and complaint rates stay low - **Sending consistency:** Daily sending during warm-up builds reputation faster than sporadic sends - **Provider responsiveness:** Some providers update reputation signals faster than others Expect the warm-up to be a real operational commitment, not a passive background process. ## What does a warm-up ramp schedule look like? A conservative ramp for a domain targeting medium volume (50,000-100,000 emails per month): - **Week 1:** 200-500 emails per day - **Week 2:** 1,000-2,000 emails per day - **Week 3:** 5,000-10,000 emails per day - **Week 4:** 20,000-30,000 emails per day - **Week 5-6:** Ramp to target volume ```mermaid flowchart LR W1["Week 1: 200–500/day"] --> W2["Week 2: 1k–2k/day"] W2 --> W3["Week 3: 5k–10k/day"] W3 --> W4["Week 4: 20k–30k/day"] W4 --> W56["Weeks 5–6: Target volume"] ``` The key is consistency within each day and smooth increases between periods. Doubling volume day over day is too aggressive. A 50-100% increase per week is a reasonable upper bound. ## Which recipients should I send to during warm-up? Your most engaged contacts. These are users who have recently interacted with your product, opened previous email from you (from your previous domain or provider), or explicitly requested communication. Engagement during warm-up is what signals to inbox providers that your mail is wanted. Do not warm up a domain by sending to a cold list or newly acquired contacts. Complaints and low engagement during the warm-up period can permanently damage the domain's reputation before it has had a chance to establish itself. ## Do I need to warm up a shared IP versus a dedicated IP differently? Shared IPs (where multiple senders use the same IP) carry pooled reputation. When you use a shared IP through an established provider, the IP itself already has reputation — you do not need to warm the IP from zero. You still need to warm your **domain**, which has its own reputation separate from the IP. Dedicated IPs require warming the IP in addition to the domain. This is why dedicated IPs at low volumes can hurt deliverability rather than help it: a dedicated IP with minimal sending history looks less reputable than a shared IP with strong pooled history. ## What authentication needs to be in place before I start? Before sending the first warm-up email: - SPF record published and validated - DKIM configured for every service that will send from this domain - DMARC record at `p=none` with aggregate reporting enabled - Google Postmaster Tools set up and domain verified Do not start warm-up without these in place. Authentication failures during warm-up accumulate as negative signals. ## What metrics should I monitor during warm-up? Check these daily: - **Inbox placement rate** — Use a seed list testing tool to see where your mail lands - **Bounce rate** — Hard bounces above 2% are a warning sign; stop and clean your list - **Spam complaint rate** — Anything above 0.08% warrants investigation; above 0.30% can trigger Gmail throttling - **Domain reputation in Postmaster Tools** — Should be "High" or climbing toward it ## What do I do if spam complaint rate spikes during warm-up? Stop sending to the segment that generated the complaints. Review what was in that email: was the content unexpected? Was the list sourced differently from the rest? Was the unsubscribe link working? Do not try to push through a complaint spike by continuing to send. A complaint rate spike during warm-up can cause inbox providers to classify your domain at a lower reputation tier that is difficult to recover from. ## Can I warm up multiple domains at the same time? Yes, but it multiplies the operational overhead. Each domain needs its own ramp schedule, its own monitoring, and its own authentication setup. Teams warming up a primary sending domain and a backup domain simultaneously should track them as separate projects. --- Domain warm-up is one of the more technically detailed parts of email infrastructure, and the cost of doing it wrong is measured in weeks of recovery time. If you are launching a product that will send email at any significant volume, [talk to Clixo](https://clixo.sh/#contact) about getting the infrastructure right from the start. --- Clixo · 1141 W Bryn Mawr Ave, Itasca, IL 60143, US · [hello@clixo.sh](mailto:hello@clixo.sh) [Start a build](https://clixo.sh/#contact) · [All services](https://clixo.sh/services) · [Agent guide (llms.txt)](https://clixo.sh/llms.txt)