Sending at scale

One sending domain vs many

One domain is fine while your volume comfortably fits inside its safe ceiling and your audience is engaged. You add domains when you need redundancy, when you want to separate streams (marketing vs transactional, segments, brands) or when a single campaign needs to reach more contacts than one domain can safely handle in the window.

When one domain is enough

  • Your campaigns fit inside the domain's safe daily ceiling.
  • Your list is engaged and bounce and complaint rates are healthy.
  • You don't need to isolate streams or audiences.

When to add more

  • Single campaigns need to reach more contacts than one domain can safely handle in your send window.
  • You want to isolate transactional from marketing.
  • You run multiple brands, partners or offer categories.
  • You need redundancy so one domain's bad day does not stop you sending.

The trade-offs

  • Every domain needs DNS, SPF, DKIM and DMARC set correctly.
  • Every domain has to be warmed before carrying real volume.
  • Reputation has to be monitored per domain, not just in aggregate.
  • Routing has to know which contact goes through which domain.

How a managed service handles it

Provisioning, authentication, warm-up and monitoring run automatically across the pool, with the campaign routed across the right domains for the right contacts. See /deliverability.

Frequently asked questions

How many domains do I need?

Enough that no single domain carries more than its safe daily ceiling. For million-plus sends, that is dozens.

Do new domains help right away?

No. A fresh domain has no reputation. It has to be warmed before it can carry meaningful volume.

Should I rotate domains constantly?

No. Rotation is not a strategy. Stable, well-warmed domains with clean traffic outperform random rotation.

Keep reading

Stop thinking about the inbox.

We run the sending, protect the reputation and create the campaigns. You approve.