Introduction: Deliverability is a Reputation Game, Not a Volume Game

In modern email marketing, especially cold outreach and SaaS outbound, your inbox placement is controlled by one factor: domain reputation engineering. When you treat reputation like an asset, you gain predictable scale and stronger long-term results.

"Deliverability is earned slowly and lost instantly."

To scale safely, control where each mailbox lives, match intent to the right DNS tree, tune sending velocity, and watch engagement signals. Do that well and inbox placement becomes predictable; blur the lines and filtering—or worse, reputational damage—can spread straight to the hostname your customers already trust.

Your root domain and its subdomains are the natural place for internal communication, for customer-facing mail such as support@yourbrand.com, and—when recipients have opted in themselves and keep replying and opening at healthy rates—for newsletters and product updates that can actually strengthen domain reputation instead of eroding it.

The line you do not cross is different: for email marketing at scale and for cold outreach, you should always use related secondary domains and mailboxes on their subdomains. Do not send those programs from yourbrand.com or from *.yourbrand.com—not for a launch, not for a test, not for “just this once.” Never.

That separation is easier to operate than it sounds. On MailAPI, you can provision as many secondary domains and subdomains as your playbook needs and attach mailboxes in minutes, so the right architecture becomes your default, not an exception you postpone.

1. Your Root Domain and Subdomains: Trust, Support, and Engaged Opt-In Mail

Treat yourbrand.com and every hostname beneath it as your public trust layer: the domain on your site, your sign-in flows, and the inboxes customers expect when they need help. Internal mail, support, success, and billing-style addresses belong here by default—they signal that the brand is real, reachable, and stable.

The same tree can also carry newsletters and lifecycle email when people opted in themselves and keep engaging—strong opens, replies, and low complaints. In that narrow lane, sends reinforce reputation instead of gambling it, because the mailbox behaves like a relationship channel, not a megaphone.

What still does not belong on your flagship tree are the high-variance programs ISPs read as acquisition or bulk promotion: cold sequences, purchased lists, spray-and-pray campaigns, or anything you would not happily explain to your support queue. Run those from mailboxes on a related secondary domain and its subdomains—for example outreach@mail.yourbrand-outbound.com—never from *.yourbrand.com. If a sending lane wobbles, you want the pain isolated on infrastructure you can retire or rewarm, not on the address your CEO uses with customers.

Critical insight

Treat “no email marketing or cold outreach from the primary root or its subdomains” as a product decision, not a suggestion. Break that rule once and you teach ISPs—and your own team—to lump your flagship domain in with high-variance sending. Keep that boundary absolute, run campaigns only on related secondary domains and their subdomains, and use MailAPI to grow that secondary fleet without dragging product trust into the experiment.

2. Email Marketing and Cold Outreach: Secondary Domains and Their Subdomains Only

For email marketing at scale and for cold outreach, you should always build on related secondary domains you own—think of a dedicated sending domain that still feels on-brand—and then place mailboxes on subdomains of those secondaries, for example mail.yourbrand-outbound.com under yourbrand-outbound.com. That pattern buys isolation, rotation room, and a hard firewall between promotional volume and the namespace your customers already bookmark.

On MailAPI, you can add as many of those secondary domains and subdomains as you need and attach mailboxes in minutes, so “we need another lane” never becomes an excuse to park acquisition mail back on *.yourbrand.com.

Use the following counts as a practical ramp for each sending subdomain on a secondary domain (not for your primary domain tree).

  • Starter setup: Start with 1-2 mailboxes while you prove list quality and replies on that hostname.
  • Standard cold outreach: Run 2-5 mailboxes for steady day-to-day outbound once baselines look healthy.
  • Scaled systems: Move to 5-8 mailboxes when reply consistency is strong and monitoring is in place.
  • Aggressive infrastructure: Use up to 10 mailboxes only when engagement is strong, segmented, and you can retire a lane without drama.

Subdomains on a secondary domain still share family reputation, so discipline matters—but the key win is that damage stays off your flagship namespace. Good habits compound across your sending fleet; bad habits sting a lane you can quarantine instead of your support inbox.

Need a deeper action plan for this stage? Follow the complete deliverability guide .

3. Safe Email Sending Limits (Per Mailbox, Sending Subdomain, and Fleet Aggregate)

The numbers below apply to campaign and cold-outreach infrastructure on secondary domains and their subdomains. They are not a green light to run bulk acquisition or promotional blasts from your primary root or its subdomains—that traffic belongs on the secondary fleet, period.

Mailbox stage Emails/day Warm-up 5-10/day Early scaling 20-50/day Stable sending 50-100/day High trust accounts 100-150/day Sending-subdomain setup (on a secondary domain) Emails/day Conservative 100-300/day Standard outbound 300-800/day Optimized system 800-1500/day

Use this practical capacity formula for a sending subdomain on a secondary domain: mailboxes × 50-100 emails/day. That keeps your scaling math honest and avoids surprise reputation shocks.

The table below is for combined daily campaign volume you might plan across authenticated secondary domains and their subdomains. It is not permission to ship cold or bulk promotional sends from @yourbrand.com or @anything.yourbrand.com. Your flagship tree stays for internal mail, support-style contact, and engaged opt-in newsletters—not for marketing or cold programs.

Outbound fleet maturity (secondary domains & their subdomains) Emails/day New domain 0-100/day Warming domain 100-500/day Established domain 500-1500/day Strong reputation 1500-3000/day

If you go above 3000 emails/day across your secondary sending fleet, you need strong engagement history, segmented subdomains on those secondaries, and excellent list hygiene. The good result is stable high-volume delivery; the bad result is rapid domain fatigue and inbox degradation.

4. Critical Email Deliverability Health Metrics

You should treat these as non-negotiable KPIs because major ISPs, including Gmail, Outlook, and Yahoo, score your sender quality against them every day. Strong metrics earn trust, while weak metrics trigger filtering and throttling.

Bounce rate

  • You should keep your bounce rate below 1% for optimal mailbox health.
  • You can treat anything below 2% as a safe operating threshold.
  • You should treat anything above 3% as a danger zone that requires immediate cleanup.

Spam complaint rate

  • You should target a complaint rate below 0.1% to maintain strong trust with ISPs.
  • You should treat 0.1%-0.3% as a warning zone and review targeting quickly.
  • You should treat anything above 0.3% as critical and pause scaling until fixed.

Volume spike consistency

Safe pattern: Keep a steady daily increase of 10%-20% so your growth looks natural to ISPs.

Danger pattern: Avoid sudden 5x-10x spikes because they resemble abusive behavior and increase filtering risk.

Engagement metrics

  • Your open rate is usually 20%-35% in cold campaigns, 35%-55% when performance is strong, and 55%+ when targeting is excellent.
  • Your reply rate below 1% is weak, 2%-5% is healthy, and 8%-15% indicates high-performing campaigns.

Replies are your strongest positive sender-reputation signal. If you optimize for real conversations instead of raw sends, you protect inbox placement and scale with much lower risk.

5. Domain Burning Factors (What Breaks Deliverability)

For prevention and recovery tactics for these risks, see this deliverability best-practices guide .

  • If your list hygiene is poor (scraped or outdated contacts), your bounce rate rises and trust drops quickly.
  • If SPF, DKIM, or DMARC is missing, your trust checks fail and inbox placement weakens.
  • If you run email marketing or cold outreach from your primary root or its subdomains, you stack list and reputation risk on the same namespace as support and internal mail—the exact collision this architecture exists to prevent.
  • If your engagement collapses (low opens, low replies, fast deletes), your sender quality score declines.
  • If your copy triggers spam patterns (all caps, fake urgency, repetitive templates), filtering pressure increases.

6. Proven Scaling Architecture (Industry Standard)

  • Keep your primary root domain (and its subdomains) for internal mail, customer-facing inboxes such as support, and—only when engagement stays strong—opt-in newsletters that behave like a relationship channel.
  • Add one or more related secondary domains for email marketing and cold outreach; provision three to five or more sending subdomains under those secondaries as you segment volume.
  • Run roughly two to five mailboxes per sending subdomain for balanced throughput, scaling out with MailAPI on the secondary fleet instead of borrowing your flagship namespace for campaigns.
  • Limit each campaign mailbox to roughly 50-100 emails/day while you watch engagement, then grow with process—not by collapsing everything onto a single hostname.

Your total safe capacity is usually 300-1500/day in the safe zone and 1500-3000/day in optimized systems with disciplined operations.

7. Expert Insight (From Industry Practice)

"Your list quality determines your deliverability, so you should prioritize data quality before you increase volume."
"Your inbox success comes from segmentation and consistency, while brute-force sending usually produces short-term volume and long-term damage."

8. Deliverability Optimization Chart (Real-World Model)

Stage Emails/day Risk level Warm-up 5-10 Very low Early scaling 20-50 Low Stable sending 50-100 Moderate Aggressive scale 100-150 High (if unmanaged) Sending-subdomain capacity (on a secondary domain) 300-1500/day Depends on health Fleet aggregate (secondaries + their subdomains) 500-3000/day Reputation dependent

Final Takeaway: Inbox Placement is Engineering, Not Luck

Deliverability is not about sending more emails. It is about sending structured, behavior-driven traffic that proves your messages are wanted and valuable.

The split is simple to remember: your root domain and its subdomains carry trust—internal mail, support, and engaged opt-in newsletters when the data says people want the mail. Email marketing and cold outreach never live there; they always run on related secondary domains and their subdomains. Scale that secondary fleet horizontally with MailAPI so promotional volume never collides with the identity your customers already believe in.