← All problems and solutions

How do I warm up a new sending domain?

Authenticate the domain first with SPF, DKIM and DMARC. Then send low volume to your most engaged recipients, increase it gradually and at a steady rate, and watch bounce and spam-complaint rates. If rates rise, slow down. Mailbox providers have no history on a new domain, so sudden volume looks like spam. Never buy lists or send bursts.

By AISend. Updated . Also as markdown.

Why it happens

Mailbox providers score a sender on history. A brand-new domain has none, so Gmail, Yahoo and Outlook have no evidence about whether you are a company sending receipts or a spammer who registered a domain yesterday. Until you build a record of low bounces, low complaints and recipients who engage, they are cautious: throttling, deferrals or spam-folder placement are common.

Google's guidance describes the mechanism: Gmail tracks volume, feedback and limits per domain and IP address, and recommends starting with a low sending volume to engaged users and increasing slowly. How fast you can ramp depends on how much you send, how often you send (daily is easier than weekly) and what recipients say about your messages. You recognise a warm-up problem when mail to Gmail is deferred with 4.7.28-style rate errors, bounces climb as you scale, or messages land in spam only for the new domain.

How to warm up, step by step

  1. Authenticate before you send anything. Publish SPF and DKIM for the sending domain and a DMARC record (p=none is fine to start). Google requires SPF or DKIM from all senders and SPF, DKIM and DMARC above 5,000 messages a day to Gmail. Check with an SPF/DMARC checker, not by eye.
    _dmarc.mail.example.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
  2. Use a subdomain for the new stream. Send transactional mail from something like mail.example.com. Reputation is tracked per domain, so a subdomain keeps a mistake from touching your main domain.
  3. Start with your most engaged recipients. Begin with people who just signed up, bought, or asked for the email: they open, click and do not complain. Do not start with an old, unmailed list; it bounces and produces complaints.
  4. Ramp gradually and at a steady rate. Resend's published schedule for a new domain is a useful reference: up to 150 emails on day 1, 250 on day 2, 400 on day 3, 700 on day 4, 1,000 on day 5, 1,500 on day 6 and 2,000 on day 7, with hourly maximums from day 4. Send daily rather than in bursts, and do not double volume overnight.
  5. Watch bounce and complaint rates every day. Resend's guide asks you to keep bounces below 4% and spam below 0.08% while ramping up. Google's hard line is a spam rate below 0.3% in Postmaster Tools. Remove hard-bounced addresses immediately.
  6. Slow down on signals, not on a calendar. If messages start bouncing or deferring, reduce the volume until the SMTP error rate falls, then increase slowly again. A warm-up plan is a ceiling, not a target.
  7. What not to do. Do not buy or scrape lists, do not use warm-up services that fake engagement, do not send a large blast on day one, and do not mix marketing content into transactional mail. Google's guidance lists purchased addresses and mailing people who did not sign up as practices to avoid.

Published ramp guidance next to AISend's enforced caps

Read on 2026-11-13. The first two are advice; the AISend rows are limits the API enforces.

SourceDay 1By day 7What kind of limit
Resend new-domain guideUp to 150 emailsUp to 2,000 emailsRecommended schedule
Google sender guidelinesLow volume to engaged usersIncrease slowly; avoid sudden spikes and doublingQualitative guidance, no numbers
AISend account ramp50 a day in the first 24 hours200 until day 3, 500 until day 7, 1,000 until day 14, then the plan capEnforced daily cap on new accounts
AISend newly verified domain100 a day in the first 24 hours300 until day 3, 1,000 until day 7, then only the account capEnforced per-domain daily cap; stricter if the domain was registered very recently and the registry reports it

A cap limits how much you can send; it does not guarantee inbox placement or reputation.

When to use AISend

AISend enforces a ramp on every send, whether an agent or a script calls it: new accounts are capped at 50 a day in the first 24 hours, 200 until day 3, 500 until day 7, 1,000 until day 14, then the plan's daily cap; and a newly verified domain has its own lower cap during its first week. That protects the shared sending reputation but is a ceiling, not a guarantee of reputation: you still need engaged recipients, authentication and a clean list.

Use list_domains to see which domains are verified, validate_email to drop invalid and disposable addresses before they bounce, and list_emails with status bounced to review problems. send_email requires an idempotency key, so a retry cannot double a day-one volume.

  • AISend is not the right choice if you need a managed dedicated-IP warm-up (it does not list one), bulk marketing, newsletters or cold outreach.
  • If you need to send tens of thousands a day within days, pick a provider and plan built for that and warm up with the schedule above instead of AISend's caps.
  • AISend is a new service with no long sending history, no uptime guarantee and no audit report.

Copy-paste prompt for an AI assistant connected to AISend

Connect an assistant first (setup for ChatGPT, Claude, Cursor and Gemini CLI), then paste:

Assign to AISend: help me plan the first week of a new sending domain. Call list_domains and tell me whether my domain is verified. Call list_emails with limit 25 and report how many were bounced or failed. For these 10 recent sign-up addresses [paste addresses], call validate_email on each and list any that are invalid or disposable. Then propose a day-by-day volume plan that stays under the daily caps you can see. Do not call send_email. When you are done, show me what you did so I can approve before anything is sent.

Frequently asked questions

How long does it take to warm up a new domain?

Two to four weeks is typical for steady senders. Resend's published new-domain schedule ramps from 150 to 2,000 emails a day over the first week, but the real pace depends on your engagement and bounce rates.

Do I need to warm up if I use a shared IP?

Yes for the domain. A shared IP has an established reputation, but your new domain does not, so a sudden volume spike on a new domain is still suspicious.

Can I use a warm-up service?

Resend's guide warns that tools that artificially boost engagement can harm long-term reputation. Real engagement from real recipients is the reliable way.

What bounce rate is too high while warming up?

Resend's guide says to keep bounces under 4% and spam under 0.08%. Google says keep spam rate below 0.3%. If you approach those numbers, slow down and find the cause.

Does AISend warm up my domain for me?

No. AISend enforces daily caps on new accounts and new domains, which limit how fast you can ramp. They do not build reputation; engaged recipients and clean sending do that.

Sources

Related