Dedicated IP planning

Size dedicated SMTP IP count before committing to infrastructure.

Work backwards from monthly send load to a defensible dedicated IP count using conservative per-IP daily caps.

Calculator

Model the send load.

Per-IP caps here are planning ceilings, not targets. New IPs still ramp through warmup, blacklist monitoring, and launch gates before carrying prospect traffic. Microsoft and Google mailbox packages carry no SMTP IP share in this model.

Reset defaults

Capacity recommendation

Dedicated SMTP infrastructure

Dedicated server/IP planning for customers that need stronger infrastructure isolation.

Estimated monthly cost

$630

Planning estimate only.

Monthly emails

15,000

5,000 prospects x 3 touches.

Daily send requirement

693

Spread across 5 send days/week.

Recommended inboxes

28

25 emails/inbox/day cap.

Recommended domains

10

3 inboxes/domain by default.

Infrastructure caps

SMTP IP capacity
2
Domain daily cap
100
IP daily cap
3,000
Warmup assumption
30 days

Per-IP utilization should stay below 80 percent before adding traffic. Scale horizontally with more IPs or domains before raising inbox caps.

Cost assumptions

Dedicated SMTP infrastructure platform planning baseline$249
28 inboxes$168
10 managed domains$15
2 SMTP IP capacity units$198

Domain registration, taxes, discounts, support tiers, and real Microsoft/Google reseller SKUs can change the final quote.

Readiness notes

  • Treat this as a planning estimate, not a quote or deliverability guarantee.
  • Readiness gates, seed-placement evidence, and fresh SMTP/IMAP smoke tests still decide exportability.
  • Dedicated SMTP IP capacity should be reserved before raising inbox caps.

Common questions

How many emails per day can one dedicated IP send?

This calculator defaults to a conservative 3,000 emails per IP per day. Higher-risk profiles model up to 5,000, but higher throughput concentrates reputation risk on fewer IPs.

Is one dedicated IP enough to start?

Often yes for the modeled volume, but a single IP is also a single point of reputation failure. The result should be read alongside blacklist monitoring and replacement planning, not as a launch approval.