How to Warm Up a New Email Domain for Free (With Your Own Inboxes)

Warming up a new email domain for free means sending a small, slowly growing volume of real email — to inboxes you own or to people who'll actually reply — before you ever send cold outreach from it, so Gmail and Yahoo build up a history that your domain is a real sender and not a fresh throwaway. Neither Google nor Yahoo publishes an exact day-by-day schedule, but their own guidelines agree on the shape of it: start low, grow slowly, never spike, and get SPF, DKIM and DMARC right before volume matters at all. Here's the free version, step by step, including the parts that need real conversations rather than just sent mail.

What does "warming up" a domain actually mean?

A brand-new domain, or an old one that's never sent email, has no sending reputation yet. Mailbox providers like Gmail and Yahoo decide whether to inbox, filter, or reject your mail partly based on what they already know about your sending domain: how much you send, how consistently, and how recipients react (opens, replies, deletes, spam reports). A domain with no history gets treated cautiously by default.

Warm-up is the process of building that history on purpose, before you need it for anything that matters: a handful of emails a day at first, to people likely to open and reply, gradually increasing, so your domain earns a track record of being read rather than reported.

How do you warm up a new domain for free, step by step?

1. Set up SPF, DKIM and DMARC first. Google's sender guidelines require at minimum SPF or DKIM from every sender, and recommend a DKIM key of 2048 bits where your provider supports it; Yahoo's sender best practices say the same at a 1024-bit minimum. A DMARC record set to p=none is enough to start — it lets you monitor authentication without rejecting your own mail while you're still testing. Do this before you send anything from the new domain, not after.
2. Start with real conversations, not a list. Email a handful of people who you know will open, reply, and not mark you as spam — former colleagues, friends, your own other inboxes, or your team. The goal is replies and opens registering against your domain, which is what builds reputation; a sent email nobody opens does less for you than one that gets a reply.
3. Send a small, consistent volume daily rather than bursts. Google's guidelines explicitly warn against "sudden volume spikes," giving doubling your previous volume as an example of what to avoid, and recommend sending "at a consistent rate" instead. A handful of emails a day, every day, beats fifty one day and none the next.
4. Increase gradually over a few weeks. Neither Google nor Yahoo publishes a specific number of emails per day or a fixed number of weeks — their own pages stop at "start low, grow slowly, watch your metrics" — so there's no official schedule to follow blindly. Use your own sending history as the pace-setter: keep growing only as long as replies and opens stay healthy and bounces stay low.
5. Watch for bounces and deferrals, and back off if you see them. Google's guidance is explicit here too: if you start seeing bounces or temporary deferrals, reduce volume until the error rate drops, then resume increasing slowly. A sudden drop in acceptance is a signal to pull back, not push through.
6. Keep your spam complaint rate low the entire time. Google's page states the requirement as below 0.3% and the actual target as below 0.10% in Postmaster Tools; Yahoo states the same 0.3% ceiling. This matters during warm-up as much as afterward — a handful of early complaints on a new domain does more damage than the same complaints on an established one.

Is there an official warm-up schedule from Google or Yahoo?

No — and that's worth knowing before you trust a vendor's precise-looking chart as gospel. Google's own sender guidelines describe the principle (start low, avoid spikes, scale more slowly if you're a large sender, back off on bounces) without giving a day-by-day volume table. Yahoo's sender best practices page doesn't address warm-up or volume ramping at all; it only covers authentication, spam-rate and unsubscribe requirements. Any specific "day 1: 20 emails, day 7: 50 emails" schedule you see online is a vendor's own practice, not something either provider has published, so treat those numbers as a reasonable starting point rather than a rule.

What do you need authenticated before volume even matters?

Both providers converge on the same baseline, and it has to be right before warm-up volume helps you at all — a well-paced sending schedule on a domain with broken authentication still won't land in the inbox:

Gmail defines "bulk" as more than 5,000 messages a day to Gmail addresses specifically — well above what a solo founder's personal cold outreach should ever hit — but setting up all three (SPF, DKIM, and a p=none DMARC record) from day one costs nothing and means you're never caught out if your sending grows. See cold email deliverability best practices for the full authentication checklist beyond just warm-up.

How do you warm up a domain using inboxes you already own?

The manual version of warm-up — sending real emails back and forth between inboxes you control, watching where they land, and repeating daily — works, but doing it by hand across multiple seed inboxes gets tedious fast: writing a different-sounding email for each one, checking four separate inboxes for where it landed, and remembering to send again tomorrow.

Mail Mantis, a free, open-source, self-hosted tool from the team behind Larvabot, is built specifically for this. You connect your domain's sender and the inboxes you own (Gmail, Outlook, Yahoo, iCloud, or any IMAP inbox, or ones friends lend you — never a shared pool of strangers' inboxes), and it drafts a different, ordinary-looking email for each one based on a brief it reads from your own website. You send manually or hand it to autopilot, which sends a few new emails a day (you set the number, from 1 to 10) and advances each conversation by one reply. For each send, it checks the seed inbox and reports whether the message landed in Primary, Promotions, Focused, Other, or Spam, so you're not guessing at placement. It's MIT-licensed and runs with docker compose up -d, or free on Vercel with a Neon database — see the self-hosting guide or the source on GitHub. It's explicit that it can't guarantee inbox placement — no tool can — and that proper SPF/DKIM/DMARC and real engagement matter more than any warm-up tool; it automates the busywork of warming up with your own inboxes, not a substitute for getting the authentication right first.

The two tools don't connect to each other, but they fit the same workflow: Mail Mantis builds a new domain's reputation through real back-and-forth with inboxes you own, and once you're sending actual outreach from that warmed-up domain, Larvabot paces those personal emails in small daily batches through your own connected sending account (how it sends through your domain) rather than front-loading a list all at once — the same "don't spike volume" principle warm-up runs on, just applied to the outreach itself.

How long does domain warm-up take?

Long enough that you shouldn't plan to send real cold outreach from a domain the same week you registered it. Vendors who sell warm-up tools commonly describe three to four weeks for a brand-new domain with no sending history, growing from a handful of emails a day up into the dozens by the end of that period — but since this figure comes from vendors, not Google or Yahoo directly, treat it as a reasonable planning estimate, not a guarantee. The actual answer is "as long as it takes for your bounce rate and spam complaints to stay low while you increase volume" — if either climbs, you slow down and extend the timeline rather than hit a date on a calendar.

If you're warming up a domain specifically to send personal cold outreach afterward, see cold email for SaaS for templates built around the small, individually written volume a newly warmed domain should actually be sending — and is cold emailing legal for the authentication and opt-out rules that apply once you start.

Frequently asked questions

Do I need to warm up a domain if I'm only sending a few emails a day?

Yes, if the domain has never sent email before. Reputation is about consistency and history, not just volume — a domain that goes from zero sends to any outbound cold email overnight looks the same to a filter whether that's 5 emails or 500. Start with real conversations to inboxes you own for a week or two before sending to people who don't know you.

Can I warm up a domain without any paid tools?

Yes. SPF, DKIM and DMARC setup is free through your domain registrar or DNS host, and sending real emails back and forth between inboxes you own costs nothing beyond your own time. A free, self-hosted tool can automate that back-and-forth if doing it by hand across several inboxes gets tedious (see the warm-up tool above).

What happens if I skip warm-up and send cold email from a brand-new domain?

You risk higher spam-folder placement and bounce rates from the start, since the domain has no history for Gmail or Yahoo to trust yet. A few early spam complaints or bounces on an unwarmed domain can damage its reputation faster than the same signals would on an established one, making it harder to recover even after you slow down.

How many emails a day is safe during warm-up?

Neither Google nor Yahoo gives an exact number — their guidance is to start low with engaged recipients and grow slowly without sudden spikes. A handful of emails a day at the very start, increasing gradually over a few weeks while watching your bounce and complaint rates, is the general shape vendors recommend; let those metrics set your pace rather than following a fixed number.

Does warming up a domain guarantee my emails will reach the inbox?

No tool can promise that, and the warm-up tool above says so directly about itself: proper SPF, DKIM and DMARC authentication and genuine recipient engagement matter more than any warm-up process. Warm-up builds a track record; it doesn't override a misconfigured domain or content that looks like spam.