IP Warmup vs Domain Warmup: What Changes Your Sending Plan?

Two teams can both be "warming up email" while adjusting completely different things. One is introducing a new sending address. The other has just added a dedicated IP to its email provider. Copying the same daily schedule between them can leave a fairly important detail out of the plan.

IP warmup gradually introduces traffic through a sending IP address. Domain warmup introduces activity for a sending domain or subdomain. Mailbox warmup concerns an individual sending address. They can happen together, but the controls and evidence are different.

MailSlurp email warmup runs paced messages through your own sending connection and reports delivery observations. When a provider also manages a dedicated-IP ramp, the two schedules need to be understood together. This guide gives you a simple way to identify which part of the sending path is changing.

Three kinds of sending history

An IP address identifies a server on the network. The visible From domain tells the recipient who the message claims to come from, while authentication supplies evidence about that identity. A mailbox is the full sending address, such as updates@example.com.

Change	What needs attention?	Where the relevant controls live
A new mailbox on an existing domain	Address activity, connection and message behavior	Mailbox settings and the sender's warmup program
A new sending domain or subdomain	Authentication, domain history and gradual production activity	DNS, sending provider and warmup schedule
A new dedicated IP	Traffic through that IP and feedback from receiving providers	The provider's IP pool and warmup settings
A move to another provider	Potential changes to IPs, signing, routing and credentials	Both provider configurations and the new sending connection

The rows can overlap. Keeping the From address during a migration doesn't preserve the outgoing server. Adding a mailbox doesn't necessarily allocate a new dedicated IP. The provider migration guide covers the wider before-and-after comparison when several pieces move at once.

Shared IPs and dedicated IPs

A shared IP carries mail for multiple senders. A dedicated IP is allocated for your sending use. That distinction matters because the provider manages the shared pool, while a dedicated-IP plan gives you a specific infrastructure ramp to account for.

With shared sending infrastructure, domain authentication, audience quality, message content and your own volume changes remain relevant. "The provider handles the IPs" still leaves plenty of work at the sender level.

For a dedicated IP, there is an additional question: how much production traffic is actually taking that route? A message submitted successfully to the provider might use another available IP. The provider's routing and delivery logs are the right evidence for that part of the plan.

How SendGrid IP warmup affects the plan

SendGrid's automatic IP warmup limits traffic through a warming IP by the hour. Other available IPs may carry traffic after that limit is reached; without another available IP, messages can be retried. Its schedule is therefore a routing and capacity consideration as well as a reputation measure.

For a SendGrid sender connected to MailSlurp, the useful distinction is straightforward. The MailSlurp program controls its scheduled warmup messages. SendGrid's dedicated-IP settings control the infrastructure those submitted messages use. A count in one system doesn't describe all activity in the other.

The MailSlurp SendGrid connection guide covers the API-key connection and verified sender preparation. A connection test confirms that this path can submit and deliver a test message; provider logs establish which IP handled it.

How Amazon SES warmup fits

Amazon SES documents an automatic warmup process for standard dedicated IP addresses. That process belongs to the dedicated-IP configuration. Its progress should be reviewed with the production traffic using those IPs.

The MailSlurp connection uses regional SES SMTP credentials and a verified sending identity, as described in the SES setup guide. Choosing the correct SES region matters because the endpoint and sending identity need to agree. An ordinary AWS API access key isn't the SMTP password for this connection.

If the SES account uses a different IP arrangement, its corresponding provider guidance is the right reference. A standard dedicated-IP schedule shouldn't be treated as a universal schedule for every SES account.

A sending-path worksheet

Here's a manual worksheet for a team introducing updates@example.com. The address is illustrative; the blank fields are for your own configuration. This is a planning record, not an API payload or an automatic MailSlurp report.

Visible From address: updates@example.com
Sending provider and region:
Shared pool or dedicated IPs:
IP pool/routing configuration:
DKIM signing domain:
SPF/DMARC results from a received message:
Provider IP ramp, if applicable:
MailSlurp warmup current pace and target:
Production messages expected on the same path:
Latest provider delivery response:
Latest completed placement check and destinations:
Next review and owner:

The most useful fields are often the ones that were previously assumed. For example, the campaign owner may expect a new dedicated IP to carry the whole send, while the provider is still routing overflow elsewhere. Writing down the routing arrangement makes that discrepancy visible before the launch meeting.

MailSlurp's connection, schedule and activity views supply the sender-program details. Your provider supplies the IP and production-routing details. A received message and a completed placement check add evidence from farther along the journey.

Why one schedule can't answer every question

MailSlurp's Standard preset targets 20 warmup messages per day over 28 days. That is a sender-program setting. It should not be copied into a dedicated-IP production plan as if 20 messages a day establishes readiness for a much larger campaign.

The same applies in the other direction. A provider's IP warmup completion status describes that provider's process; it doesn't establish where the next campaign will land for every recipient.

The practical review combines three things:

• Provider behavior: routing, throttling, deferrals and delivery responses for the production path.
• Warmup observations: scheduled and accepted sends, controlled receipt and any completed provider placement checkpoints.
• The next real send: its content, expected recipients, volume and handling of bounces, complaints and unsubscribes.

A pending placement check has no completed result yet. An accepted request means the sending provider accepted it. Neither should be silently counted as an inbox placement result. The warmup setup guide explains these observations and the available schedule controls.

What happens when the domain stays the same?

For an SES sender, the Amazon SES warmup guide works through the region, sandbox and SMTP prerequisites before the first test delivery.

If you keep the domain but change providers or dedicated IPs, testing the new route is still useful. The familiar From address can conceal a different signing configuration, return path or outgoing server.

If the IP stays the same but the domain changes, the new domain's authentication and activity need their own review. Its messages may also use new links or templates. Changing one part of the path doesn't settle every other part.

Before increasing production volume, a separate inbox placement test can check the actual campaign through the configured sender. That gives you a closer comparison than relying only on the plain-text warmup content. Provider responses and real recipient feedback then help guide the next increase.

To start the sender program, create a MailSlurp account and connect the provider you intend to use. Keeping the sender schedule, IP routing and placement results visible together makes the next sending decision much easier to explain.