> For the complete documentation index, see [llms.txt](https://humanic.gitbook.io/humanic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://humanic.gitbook.io/humanic/getting-started-with-humanic/domain-setup/domain-and-or-ip-warm-up-guide.md).
# Domain and/or IP Warm-up Guide
Warming up a domain or IP refers to the practice of progressively increasing your sending volume to maximize your deliverability. The goal is to send at a consistent rate and avoid any spikes in email volume that might be concerning to inbox service providers.
Whenever you change your sending patterns—whether because you’re using a new domain, a new IP, or a new vendor, or because your volume will increase—you should warm-up your domain and/or IP. A thought-out warm-up plan limits greylisting and delivery throttling, as well as helping establish a good domain and IP reputation.
As your volume increases, you’ll need to monitor your bounce rate to ensure it remains below 4%, and your spam rate below 0.08%. An increase in these rates would be a sign that your warm-up plan needs to be slowed down, and an investigation into the root causes of the increases should start.
Following these rules and metrics will establish a good domain reputation. Each sender has different constraints and needs, so these numbers are meant as a baseline. Our [support team](https://resend.com/help) can work with you on devising a plan adapted to your needs.
## [](https://resend.com/docs/knowledge-base/warming-up#existing-domain)Existing domain
If you’re already sending from an existing domain with established reputation and volumes, you can use the following guidelines to start sending with Humanic
| **Day** | **Messages per day** | **Messages per hour** |
| ------- | -------------------- | --------------------- |
| **1** | Up to 1,000 emails | 100 Maximum |
| **2** | Up to 2,500 emails | 300 Maximum |
| **3** | Up to 5,000 emails | 600 Maximum |
| **4** | Up to 5,000 emails | 800 Maximum |
| **5** | Up to 7,500 emails | 1,000 Maximum |
| **6** | Up to 7,500 emails | 1,500 Maximum |
| **7** | Up to 10,000 emails | 2,000 Maximum |
## [](https://resend.com/docs/knowledge-base/warming-up#new-domain)New domain
Before you start sending emails with a brand new domain, it’s especially important to have a warm-up plan so you can maximize your deliverability right from the start.
| **Day** | **Messages per day** | **Messages per hour** |
| ------- | -------------------- | --------------------- |
| **1** | Up to 150 emails | |
| **2** | Up to 250 emails | |
| **3** | Up to 400 emails | |
| **4** | Up to 700 emails | 50 Maximum |
| **5** | Up to 1,000 emails | 75 Maximum |
| **6** | Up to 1,500 emails | 100 Maximum |
| **7** | Up to 2,000 emails | 150 Maximum |
## [](https://resend.com/docs/knowledge-base/warming-up#warming-up-your-dedicated-ip-with-resend)Warming up your Dedicated IP
In order for a Dedicated IP to be beneficial or useful, you first need to establish a certain sending volume and patterns. Once you’ve established this volume and these patterns, our support can set it up for you. We provide an automatic warm-up process so that you can simply focus on sending.
## [](https://resend.com/docs/knowledge-base/warming-up#what-about-third-party-warm-up-services)What about third-party warm-up services?
We know email deliverability is important, and it can be tempting to use services promising quick fixes. However, using tools that artificially boost engagement can harm your long-term sender reputation. These services often rely on manipulating anti-spam filters, which can backfire as email providers like Gmail adjust their systems. Instead, we recommend focusing on sustainable practices—such as sending relevant content, maintaining a clean list, and using proper authentication. These methods build trust with email providers and improve your deliverability over time.
The warmup feature works by simulating real email conversations between accounts. It’s like having an automated back-and-forth exchange with friends, except your “friends” are other users who also have warmup enabled. These users reliably open your emails and respond with friendly, natural replies.
This activity signals to email providers that your account has genuine engagement, helping your future cold outreach emails reach inboxes instead of spam folders. In short, the warmup process improves deliverability by making your account appear more trustworthy.
Because Humanic is focused on sending emails to opted-in email addresses, it does not offer the warmup feature.
**Pre-Warmup Email Accounts**
New email accounts usually need several weeks of warmup before they can be used effectively. With Pre-Warmed Email Accounts, that process is already done for you, so you can start sending campaigns immediately. At Humanic, we do not provide the facility for free warmup accounts.
Instead, we provide rate limiting, where there is a default number of emails you can send, and these are gradually increased.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://humanic.gitbook.io/humanic/getting-started-with-humanic/domain-setup/domain-and-or-ip-warm-up-guide.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.