There is no universal daily schedule for warming a dedicated sending domain, and no source we reviewed supports one. What the providers do document is a set of principles. Authenticate the domain, keep transactional mail separate from promotional mail, increase volume gradually, and let delivery feedback set the pace. This article turns those principles into an architecture your Node.js application can implement. It does not invent numbers the providers don’t publish.
Domain vs. IP: confirm what you are warming
People say “warm up a domain” to mean two different things, and the two need different work.
As an Amazon Associate I earn from qualifying purchases.
- Sending domain or subdomain: this needs correct DNS authentication and builds its own reputation through the mail it sends.
- Dedicated IP address: this may need a separate, gradual volume ramp. Provider warmup documentation is mostly about this.
SendGrid describes both domain reputation and IP reputation in its deliverability guide, but its warmup guide focuses on the IP. A dedicated domain does not guarantee inbox placement. If you send on shared IPs, the provider has typically already warmed them, and your ramp is mainly about your domain’s reputation and your traffic pattern. Check your provider’s documentation to see which one it is warming for you.
Step 1: Authenticate before the first message
Set up DNS records using your provider’s current instructions, and make sure the visible From domain aligns with the domain that passes authentication.
#1 Best Overall
- Gmail: Google’s sender guidelines require SPF or DKIM for all senders to Gmail accounts. Senders above 5,000 messages per day to Gmail accounts need SPF, DKIM and DMARC. The requirements took effect February 1, 2024.
- Yahoo: Yahoo’s sender best practices include DMARC and alignment for bulk senders.
Requirements vary by volume and message category. Don’t assume rules such as unsubscribe headers apply the same way to purely transactional mail. Read the current Gmail sender guidelines FAQ for the details.
Step 2: Separate transactional from promotional traffic
SendGrid recommends a dedicated transactional subdomain as one way to distinguish transactional messages from marketing (SendGrid, October 5, 2023). For example, send receipts and password resets from a subdomain used only for that purpose. Keep the content recognizably transactional during the ramp, and don’t add promotional material to those messages.
Step 3: Choose your ramp pattern
New application
If volume is low, let real transactional demand grow naturally. Don’t send artificial mail to inflate numbers. Mail to real recipients who expect it is what builds reputation.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Migration from an existing provider
SendGrid recommends gradually shifting established traffic to the new setup. Your application can control this by sending a small share of messages through the new route and raising that share in steps.
Provider-managed IP warmup
Amazon SES’s standard dedicated IP warmup is automated and time-based. Its allocation steadily increases over 45 days, independent of your sending volume. SES notes that warmup time varies between email providers. It also cautions against sending large volumes right after warmup completes. As a post-warmup guide, it suggests around 1,000 emails a day to each provider on each dedicated IP to keep a positive reputation. That figure is SES-specific, not a general threshold. SES and SendGrid also offer managed or automated options as alternatives to manual ramping (see SES dedicated IPs).
SendGrid publishes a sample day-by-day IP schedule but states: “The advice and warmup schedule below is intended to be a suggestion only.” Treat it as an illustration, not a plan.
Step 4: Control the ramp in your Node.js app
No provider documentation we reviewed gives a Node.js recipe for warmup, so this is an architectural inference, not a tested library recommendation. The idea is to put routing behind one function and drive it with configuration rather than hard-coded values.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Keep a config value for the share of traffic (0–100%) sent through the new setup, changeable without a deploy.
- Choose the route per message, ideally with a stable hash of the recipient or message ID so behavior is predictable.
- Prioritize critical mail, such as password resets and verification codes, on the proven route during early steps if you have one.
- Tag each message with the route used, so bounces and complaints can be attributed to the right setup.
- Add a kill switch that returns the share to the previous step or to zero.
- Handle provider bounce and complaint webhooks, and suppress addresses that bounce or complain.
Confirm any API calls against your chosen provider’s current Node.js SDK documentation.
Best Value
Step 5: Let feedback set the pace
Hold or reduce volume when delivery worsens. Watch these signals by mailbox provider, not just in aggregate:
- Bounce rates and deferrals reported by your provider.
- Spam complaints. Google says to keep the spam rate reported in Postmaster Tools below 0.3%. That is a sender guideline, not a warmup target or a delivery guarantee.
- Gmail’s Postmaster Tools reputation views, if you send to Gmail.
The right pace depends on your expected volume, recipient-provider mix, sending history, current reputation and your provider’s warmup implementation. A spreadsheet schedule can’t account for those, so use it only as a starting sketch.
Keep traffic predictable afterwards
Finishing a ramp is not a license to jump to full volume or to send in sporadic bursts. SES specifically warns against large volumes right after warmup. A steady pattern matters most on a dedicated IP. If your volume is too low or too spiky to keep one active, a shared IP pool may suit you better.
Recommended Free Tools
Quick Recap
Choosing a provider for this
| Question to ask | Why it matters |
|---|---|
| Is warmup managed, or standard/manual? | Determines how much routing work your app must do. |
| Can you split traffic between old and new setups? | Required for gradual migration. |
| Is feedback reported per mailbox provider? | Lets you slow down for one provider without stopping everything. |
| Can you sustain steady volume on a dedicated IP? | Low or erratic volume can undermine a dedicated IP. |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
