IP Warmup for New Mail Servers and Sending Domains
Learn how to warm up a new sending IP or domain, increase email volume safely, monitor reputation and avoid blacklist issues.
Introduction
IP warmup is the process of gradually increasing email volume from a new sending IP address so mailbox providers can observe consistent, legitimate sending behavior. Domain warmup is similar, but focuses on building trust for a new or newly used sending domain.
A new IP or domain has little reputation history. Sending too much too quickly, using cold lists, missing authentication or generating complaints can make the sender look suspicious. Warmup helps build trust slowly while monitoring bounces, complaints, blacklist status and inbox placement.
Quick answer
Warm up a new IP or sending domain by starting with low daily volume, sending first to engaged recipients, keeping SPF, DKIM, DMARC and rDNS correct, avoiding sudden spikes, monitoring bounces and complaints, and increasing volume gradually only when delivery signals stay healthy.
IP warmup
IP warmup means gradually building reputation for a new sending IP address by sending small, controlled amounts of legitimate email before increasing volume.
Domain warmup means building reputation for the domain used in From, return-path, DKIM and links.
- Sending IP reputation
- Domain reputation
- Authentication
- Bounce rate
- Complaint rate
- Engagement
- Sending consistency
- Blacklist history
Warmup is not a trick to bypass spam filters. It is a controlled way to prove normal sending behavior.
IP vs domain warmup
IP warmup
- Applies to: new dedicated sending IP or new mail server.
- Main goal: build trust for the server or network address.
- Important for: dedicated SMTP, VPS mail servers, transactional providers and high-volume senders.
Domain warmup
- Applies to: new domain, subdomain or newly used sending identity.
- Main goal: build trust for the brand or sending domain.
- Important for: new businesses, new marketing domains, new transactional domains and rebranded senders.
If both the IP and domain are new, warmup should be more conservative.
When warmup is needed
Warmup is recommended when:
- Using a new dedicated IP
- Launching a new sending domain
- Moving from one SMTP provider to another
- Starting transactional email from a new server
- Increasing volume significantly
- Recovering after blacklist or spam incident
- Separating marketing from transactional mail
- Using a new subdomain for campaigns
Very low-volume business mail may not need a formal warmup plan, but it still needs correct authentication and clean sending.
Before warmup
Pre-warmup checklist
Confirm these items before sending volume increases.
SPF
Includes the sending service.
DKIM
Signing is enabled.
DMARC
Policy exists.
rDNS/PTR
Correct for dedicated IPs.
HELO/EHLO
Hostname is valid.
Bounce handling
Works correctly.
Unsubscribe handling
Works for marketing mail.
Domain blacklist
Sending domain is not listed.
IP blacklist
Sending IP is not listed.
Recipient list
List is clean.
Tracking domains
Link domains are trusted.
Sending logs
Logs are available.
Do not start warmup until the technical identity is correct.
First recipients
Start warmup with recipients most likely to engage positively.
Best first recipients
- Recent customers
- Active users
- People who recently opted in
- Users who opened or clicked recently
- Transactional recipients expecting the message
- Internal or test recipients for early validation
Avoid during warmup
- Purchased lists
- Scraped contacts
- Old inactive lists
- Unconfirmed subscribers
- Bounced addresses
- Complaint-heavy segments
- Cold outreach at scale
Engagement matters. Sending first to people who ignore or complain can damage reputation early.
Warmup pace
There is no universal schedule that fits every sender. Warmup speed depends on list quality, recipient engagement, domain history, sending type and provider feedback.
- Start low
- Send consistently
- Increase gradually
- Pause increases if bounces or complaints rise
- Avoid sudden spikes
- Separate risky campaigns
- Monitor daily during early warmup
A smaller clean list is better than a large risky list during warmup.
Example schedule
Week 1
Goal: validate setup and send only to highly engaged recipients. Volume: very low, controlled daily volume.
Week 2
Goal: increase slowly if bounce and complaint rates stay low. Volume: small increase.
Week 3
Goal: add more normal recipient segments. Volume: moderate increase.
Week 4+
Goal: move toward normal volume only if delivery remains stable. Volume: gradual increase toward target.
This is not a fixed rule. Adjust based on real delivery signals, provider limits and recipient engagement.
Why this matters
Warmup matters because new senders have little reputation history. A sudden burst of email from a new IP or domain can look like spam, even if the messages are legitimate. Mailbox providers may throttle, defer, filter or reject messages until the sender proves stable behavior.
Warmup is especially important for transactional platforms, SaaS products, newsletters, e-commerce messages and self-hosted mail servers.
How to monitor
Use Blacklist Checker and email diagnostics to monitor reputation during warmup.
- Blacklist status — watch the sending IP and domain.
- Bounce rate — track hard bounces and rejection messages.
- Complaint rate — watch spam complaints where feedback is available.
- Delivery delays — look for throttling or temporary deferrals.
- Authentication — check SPF, DKIM and DMARC results.
- rDNS and HELO — confirm mail server identity is consistent.
- Engagement — monitor opens, clicks and user activity where applicable.
- DMARC reports — review unauthorized sending and authentication failures.
Monitor warmup reputation
Use Blacklist Checker and email diagnostics to monitor reputation during warmup.
New sender:
mail.example.com
Starting checks:
SPF: pass
DKIM: pass
DMARC: active
rDNS: mail.example.com
Blacklist status: clean
Warmup plan:
Start with engaged users.
Send low daily volume.
Increase only if bounces stay low.
Pause if complaints increase.
Daily monitoring:
Hard bounces: low
Spam complaints: low
Temporary deferrals: monitor
Blacklist status: clean
DMARC failures: investigate
This example is illustrative. Adjust warmup pace based on your real recipient quality, provider feedback and sending goals.
Common problems
Sending volume too high too soon
HighA new IP or domain sends more mail than its reputation can support.
Next step: Reduce volume and resume gradual warmup.
Cold list used during warmup
HighOld, purchased or unconfirmed contacts create bounces and complaints.
Next step: Send only to recent and engaged recipients first.
Authentication incomplete
HighSPF, DKIM or DMARC is missing or failing.
Next step: Fix authentication before increasing volume.
No reverse DNS on dedicated IP
MediumThe new mail server does not have a professional PTR record.
Next step: Configure rDNS/PTR and HELO/EHLO consistently.
Bounce rate too high
HighMany recipients are invalid or rejecting mail.
Next step: Clean the list and stop sending to bad addresses.
Spam complaints increase
HighRecipients are marking messages as unwanted.
Next step: Review consent, content, frequency and unsubscribe handling.
Sending pattern is inconsistent
MediumLarge gaps followed by sudden spikes look suspicious.
Next step: Use predictable daily sending during warmup.
Marketing and transactional mail mixed
MediumRisky campaign behavior can affect critical transactional messages.
Next step: Separate mail streams with different domains or providers if needed.
Warmup continues despite bad signals
HighVolume increases even while bounces, complaints or listings appear.
Next step: Pause volume increases and investigate the cause.
Safe warmup steps
-
Step 1: Prepare the sending identity
Configure SPF, DKIM, DMARC, rDNS, HELO/EHLO and bounce handling.
-
Step 2: Start with engaged recipients
Send first to users who recently signed up, purchased, logged in or interacted.
-
Step 3: Send consistent low volume
Avoid sudden spikes and keep early volume predictable.
-
Step 4: Monitor delivery signals
Watch bounces, complaints, deferrals, blacklists and DMARC reports.
-
Step 5: Increase gradually
Only increase volume when signals remain healthy.
-
Step 6: Pause if problems appear
If complaints, bounces or listings rise, stop increasing and investigate.
-
Step 7: Separate risky streams
Keep marketing campaigns separate from transactional or business-critical mail.
-
Step 8: Document the plan
Record sending limits, daily volume, provider feedback and reputation checks.
Transactional vs marketing
Transactional mail and marketing mail should be treated differently.
Transactional email
- Examples: password resets, invoices, order confirmations, alerts.
- Warmup approach: usually lower volume, expected by users, should be highly reliable.
Marketing email
- Examples: newsletters, campaigns, promotions.
- Warmup approach: requires stronger list hygiene, unsubscribe handling and complaint monitoring.
Avoid using risky marketing campaigns to warm up infrastructure used for password resets or invoices.
Self-hosted mail servers need extra care because mailbox providers may distrust new VPS or dedicated server IPs.
- Clean IP history
- rDNS/PTR
- Hostname and HELO
- SPF includes IP
- DKIM enabled
- DMARC exists
- No open relay
- Rate limits configured
- Logs monitored
- Blacklist status clean
For many businesses, using a reputable transactional email provider is safer than running new outbound SMTP from a VPS.
Frequently asked questions
What is IP warmup?
IP warmup is gradually increasing email volume from a new sending IP to build reputation.
Do new domains need warmup?
Yes, if they will send meaningful email volume. New domains have little reputation history.
How fast should I increase volume?
Increase gradually based on delivery signals. There is no single safe schedule for every sender.
Can I warm up with cold outreach?
It is risky. Warmup should start with engaged, expected recipients.
Do SPF, DKIM and DMARC matter during warmup?
Yes. Authentication should be correct before sending volume increases.
Should transactional and marketing mail share the same IP?
Usually not when volume or risk is significant. Separate streams protect critical mail.
What should I do if bounces or complaints rise?
Pause volume increases, clean lists, review content and investigate reputation signals.
Related tools
Use these free tools to verify your configuration after applying changes.
Related guides
Browse all Blacklist & Reputation guides →Need help applying this fix?
Send us your domain, report link or issue details. CheckDomainHealth will review the request and route it to the right technical team if hands-on support is needed.
Was this guide helpful?
Your feedback helps us improve our guides for everyone.
Thanks for your feedback!