Cold email deliverability checklist before you send 250 emails: DNS, warm-up, limits
A pre-flight checklist for your first 250 cold emails: DNS checks with dig, a 9-day ramp, list hygiene and the bounce and complaint limits to stop at.
TL;DR
- Do three things before the first send: publish SPF, DKIM and DMARC for the domain you send from; send from a domain or subdomain you can afford to damage; and screen the list for role mailboxes and dead domains. All three are checkable in a few minutes with
dig. - Do not send 250 on day one. Google says to start low and ramp gradually. GrowFast's code ramps 15, 30, then 50 a day, so 250 emails take 9 sending days (computed from the real functions, below).
- Know your stop limits before you start. Amazon SES reviews accounts at a 5% bounce rate; Gmail's published spam-rate ceiling is 0.30%. In our own October batch, 5 of 251 sends bounced and 95 had no stored delivery result, so we could not compute an exact rate. We now stop a sending account at more than 5% bounced (once 20 results are in) or at a single spam complaint among the first 333 results.
We build GrowFast, a cold-email tool. This mixes public rules (linked), numbers from our 251-email write-up, and limits from GrowFast's code, labelled as ours. It is not legal advice and claims no step raises your reply rate.
Why 250
Our first batch was 251 sends (191 first emails, 60 follow-ups) between 4 and 23 October 2026. Five bounced, no genuine reply was recorded, and 95 sends have no stored delivery result. Daily volume was uneven:
| Day (Oct 2026) | Sends | Delivered | Bounced | No result stored |
|---|---|---|---|---|
| 4 | 63 | 0 | 0 | 63 |
| 16 | 29 | 0 | 0 | 29 |
| 17 | 3 | 0 | 0 | 3 |
| 19 | 18 | 18 | 0 | 0 |
| 20 | 18 | 18 | 0 | 0 |
| 21 | 20 | 18 | 2 | 0 |
| 22 | 37 | 35 | 2 | 0 |
| 23 | 63 | 62 | 1 | 0 |
All five bounces came on 21 to 23 October (days with 20, 37 and 63 sends); the 36 sends on 19 and 20 October all delivered. Five bounces is too few to test, and we did not break the days down by sending domain, so we cannot say volume caused them. We include the table because it is why the ramp below exists.
The checklist
| # | Check | How to verify | Source |
|---|---|---|---|
| 1 | SPF record exists, one record only, 10 DNS lookups or fewer | dig +short TXT yourdomain.com | RFC 7208 |
| 2 | DKIM published and key at least 1024 bits (2048 preferred) | provider's selector: dig +short TXT <selector>._domainkey.yourdomain.com | Google sender guidelines |
| 3 | DMARC record present (p=none is acceptable to start) | dig +short TXT _dmarc.yourdomain.com | Google sender guidelines |
| 4 | Sending domain is separate from your main one | your DNS and sender settings | our design choice, not a vendor rule |
| 5 | Ramp: start low, raise gradually, no bursts | your daily send count | Google sender guidelines |
| 6 | Role and service mailboxes removed; dead domains dropped | list screen, MX lookup | our data and code |
| 7 | Postal address, opt-out and honest subject in every email | read your own footer | FTC CAN-SPAM guide |
| 8 | Stop rules: bounces, complaints, daily ceiling | your tool's limits | AWS SES, Google; our code |
1 to 3: DNS records
Authentication is Google's first requirement. Since 1 February 2024 every sender to personal Gmail accounts needs SPF or DKIM; the stricter set (SPF, DKIM and DMARC, one-click unsubscribe) applies above 5,000 messages a day, and Google still recommends setting up all three for everyone. You will be well below 5,000, so DMARC is not a formal requirement for 250 emails, but it is cheap.
Run these three commands. This is what they return for growfast.sh, which sends through Amazon SES (checked 2026-11-18):
dig +short TXT growfast.sh
# "v=spf1 include:amazonses.com include:_spf.mx.cloudflare.net ~all"
dig +short TXT _dmarc.growfast.sh
# "v=DMARC1; p=none; rua=mailto:dmarc@aisend.app; fo=1"
dig +short MX growfast.sh
What to look for:
- SPF: exactly one
v=spf1record; two are a permanent error and receivers discard both. More than 10 DNS lookups (eachinclude:,a,mx,ptr,exists:andredirect=costs one, and includes nest) also breaks it. Ours uses 2. - DKIM: your sending provider chooses the selector, so take it from their setup page; finding nothing by guessing proves nothing. Gmail requires 1024 bits or longer and recommends 2048.
- DMARC:
p=noneonly asks for reports; forged mail is still delivered. It is our own setting on growfast.sh and fine for a first send. Add anrua=address.
GrowFast's free deliverability audit, SPF checker and DMARC checker run these lookups; point them at the domain you send from. Our checker's provider table marks Google Workspace and Microsoft 365 as accepting any recipient at SMTP time and bouncing afterwards, so no DNS check can tell you whether a prospect's mailbox exists (we did not test this ourselves).
4: a domain you can afford to damage
GrowFast gives each account a managed address on a subdomain we own (reach.growfast.sh), not on growfast.sh itself, so a customer's cold email never shares reputation with our password resets and receipts. We suggest the same for you: a subdomain such as mail.yourdomain.com with its own DNS records. This is our reasoning, not a vendor rule, and we have not tested whether it protects the root domain's inbox placement.
5: the ramp, and what 250 emails really takes
Google says to start with a low volume to engaged users, increase slowly, avoid bursts, and cut volume if mail bounces or is deferred. It names no schedule.
GrowFast enforces one. A new sending domain's cap counts from its first send (ownDomainDailyCap): 15 a day for 3 days, 30 until day 7, 50 until day 14, 100 until day 28, then 200. Managed addresses and mail.* subdomains use 15, 30, then 50 from day 7 (managedDailyCap). The account ceiling is 500 a day across domains, and a campaign larger than today's room is refused, not trimmed.
Here is the 250-email plan that follows, from calling those two functions on 2026-11-18:
| Sending day | Cap | Cumulative |
|---|---|---|
| 1 to 3 | 15 a day | 15, 30, 45 |
| 4 to 7 | 30 a day | 75, 105, 135, 165 |
| 8 and 9 | 50 a day | 215, 250 (day 9 needs only 35) |
Both ramps reach 250 on the ninth sending day. If you send by hand, copy it. We do not claim it maximises inbox placement; it follows Google's guidance.
6: clean the list
Our October batch had 4 bounces in 69 role-mailbox sends with a stored result, against 1 in 87 for named addresses. With five bounces this is only a signal (p = 0.17). GrowFast now acts on it in code:
- Service and role inboxes such as
info@,support@,help@,admin@,noreply@andabuse@are never written to. Shared inboxes (hello@,contact@,team@,sales@) are allowed but rank below named addresses, and the autopilot writes nothing for them without a contact name. - Public-sector and school domains are blocked, since spam traps live there.
- Addresses that unsubscribed, complained or bounced are suppressed for every account, not just yours. Duplicates are skipped.
- Autopilot and CSV import check each domain has a mail server (MX, or an A record per RFC 5321); a timeout keeps the address. The API and MCP send path does not run this lookup.
By hand: dedupe, delete service inboxes, and mail only people you have a specific reason to write to.
7: the footer and the subject
CAN-SPAM has no business-to-business exception. The FTC guide asks for accurate headers, a non-deceptive subject, a valid postal address, and a clear opt-out honoured within 10 business days. Google adds: do not start a subject with Re: or Fwd: unless it is a real reply. GrowFast refuses to send without a saved postal address, refuses a first-email subject starting Re:, Fwd: or Fw:, and adds an unsubscribe link plus List-Unsubscribe and List-Unsubscribe-Post: List-Unsubscribe=One-Click headers (RFC 8058) to every email. Google requires one-click only above 5,000 a day. Paste a draft into the free cold email checker: it runs in your browser and labels each finding as a published rule or our judgement.
8: when to stop
| Signal | Public number | GrowFast's limit (code) |
|---|---|---|
| Bounce rate | Amazon SES: aim below 2%, review at 5%, may pause at 10% | Run halts above 15% once 10 results are in; the account pauses above 5% over 14 days once 20 results are in |
| Spam complaints | Gmail: keep Postmaster spam rate below 0.30%; SES: review at 0.1%, may pause at 0.5% | Account pauses above 0.30% once 10 results are in, so 1 complaint pauses it until 334 results |
| Volume | Google: avoid bursts and sudden spikes | 500 a day per account; ramp per domain |
| Shared reputation | New campaigns refused when the shared sending account has no room under a 1% bounce cap over 14 days |
Two notes. The 15% per-run limit came from one earlier batch (a 5.6% baseline) and is our judgement, not an industry figure. Our October result, 5 bounces in 156 sends with a result (3.2%), would not have tripped the 5% pause, and a limit that counts only stored results is blind to the 95 sends with none. The limits are in src/lib/sender-limits.ts and src/lib/outreach.ts.
FAQ
Do I need to warm up a new domain before cold emailing? Google prescribes no schedule, only a low start, gradual increases and no bursts. The table above is one way to do it.
Do I need DMARC for 250 emails?
Google requires it only for senders above 5,000 messages a day, but recommends SPF, DKIM and DMARC for everyone. p=none is accepted at the start.
What bounce rate should make me stop? Under 2% is Amazon's target and 5% is where it reviews accounts. Treat anything near 5% as a reason to stop and clean the list.
Can I check whether an address exists before sending? Not reliably. Our checker's provider table says Google Workspace and Microsoft 365 accept any address at SMTP time and bounce later (untested by us), so use real addresses you have a reason to write to.
Methodology and data
- Dates: checklist and code read on 2026-11-18 at GrowFast
origin/maincommit6b142ab. Daily-send table from the production query Q4 of the 251-email post (read-only, queried 2026-11-17). - Code results: the ramp, health and breaker figures come from calling
managedDailyCap,ownDomainDailyCap,healthVerdictandBOUNCE_BREAKERdirectly with bun on 2026-11-18; the 9-day schedule assumes a send every day from the first. - DNS:
digand GrowFast's own checker functions on growfast.sh, 2026-11-18. We did not test any other domain. - External rules read on 2026-11-18: Google's email sender guidelines, the FTC CAN-SPAM guide, the AWS SES bounce and complaint FAQ.
- Not tested: inbox placement (we ran no seed or Postmaster Tools test), whether any ramp improves placement, Microsoft's and Yahoo's current requirements, EU or UK law.
- Our repository is private, so readers cannot check file names; the ramp is also stated in the product's refusal message ("A new domain ramps up (15 a day, then 30, 50, 100 and 200 over its first four weeks)").
- Disclosure: we build GrowFast.
From the same team
SEOBolt
Technical SEO and AI search audits with ready-to-apply fix plans.
Try SEOBolt →Bugsly
AI-powered error tracking that explains your bugs.
Try Bugsly →AutoShort
Turn a topic into a faceless short: AI script, voiceover and captions.
Try AutoShort →RemixViral
Paste a long video and get back the moments worth posting, cut vertical and captioned.
Try RemixViral →