Skip to content
RECURRING · CANCEL ANYTIME

Extra dedicated IPv4 addresses.
€8/month each. Configured in 24 hours.

One IP works fine for most senders. Past about 20K daily, past multi-stream architectures, past multi-brand operations, extra IPs start to matter. Throttling at major receivers scales per-IP; reputation accumulates per-IP; isolation between sending streams happens at the IP level.

Extra IPs come from clean ranges with no historical RBL issues. Custom rDNS configured per IP, FCrDNS verified, HELO aligned. PowerMTA VMTA mapping or Postfix transport configuration handled. €8/month per IP, cancel any IP individually anytime, no commitment.

Order on Telegram → When extra IPs help
price €8 / IP / month
delivery 24 hours
rDNS Custom + FCrDNS
commitment none
when single IP stops being enough

Three reasons to add IPs.

The first reason is throttling. Major receivers (Gmail, Outlook, Yahoo) throttle inbound mail per-IP based on observed sending rates and reputation. A single IP sending 50K daily often hits per-IP per-hour throttling at peak times; messages defer rather than deliver, queue depth climbs, customers wait. Splitting that volume across 2-3 IPs spreads throttling pressure and keeps deliveries flowing smoothly. The breakpoint where throttling starts to matter varies by receiver and by your reputation profile, but typically appears between 20-50K daily on a single IP.

The second reason is stream isolation. Mixing transactional mail (account notices, password resets, receipts) with marketing campaigns on the same IP means complaint rate from marketing damages transactional placement. Customers expecting their password reset in 30 seconds shouldn't wait because your campaign list quality is poor. Separate IPs per stream isolate reputation; transactional gets clean-IP placement while marketing handles its own reputation pressure on a dedicated IP.

The third reason is multi-brand operations. Lead-gen agencies running outreach for multiple clients, SaaS providers handling sending for multiple customers, multi-tenant email infrastructure all benefit from per-brand IP isolation. One brand's bad day doesn't drag down the others. Multi-domain Warmup (€599) addresses domain-level isolation; extra IPs address IP-level isolation. Both layers matter for serious multi-brand operations.

The honest counter-argument: most senders don't need extra IPs. Operations under 20K daily on a single brand work fine on one IP. Adding IPs for the sake of it adds complexity (warming overhead, monitoring, configuration) without proportional benefit. The calculator below helps think through whether extra IPs make sense for your specific case. For low-volume or single-stream operations, the answer is often no.

do extra IPs help your case?

Capacity calculator.

Adjust volume and stream count. The calculator estimates whether extra IPs help your operation and how many IPs fit. Single-stream low-volume operations rarely need extra IPs; multi-stream or high-volume often do.

50,000 daily

Total daily volume across all streams. Throttling matters past 20-30K per IP at major receivers.

Distinct sending streams that benefit from reputation isolation. Mixing streams on one IP causes cross-contamination.

Profile affects per-IP capacity. Aggressive cold burns IPs faster, requiring more IPs for same sustained volume.

recommendation

2 IPs recommended

Recommended IP count 2 IPs
Per-IP daily volume target 25,000
Monthly cost (extra IPs) €8/mo (1 extra)

For your volume and stream count, 2 IPs balance throttling pressure and stream isolation. Adding more IPs creates overhead without proportional benefit.

suggested allocation

Per-IP assignment

IP #1 (existing) Transactional · 25K/day
IP #2 (new) Marketing · 25K/day

Allocation isolates streams so complaint pressure on marketing doesn't damage transactional placement. Specific volumes can shift; allocation is operational guidance, not strict cap.

alternatives to consider

Other paths

  • Subdomain Rotation Pool (€99/mo): if multi-stream is cold outreach, rotation pool may fit better than per-stream IPs.
  • Multi-domain Warmup (€599): for multi-brand isolation at domain level rather than IP level.
  • Stick with single IP: if you can consolidate streams or accept some cross-contamination.

Calculator simplifies real allocation logic. Some operations benefit from more IPs than this baseline (very high volume, unusual receiver mix, specific compliance requirements); some benefit from fewer (consolidated streams, low volume). Use as starting point; for specific allocation review, book consulting hour (€199).

how to assign IPs to streams

IP allocation strategy.

Click each strategy to see how IPs map to sending streams. The right allocation depends on your operation profile; these are common patterns we deploy.

strategy detail

Single IP, single stream

Most common pattern for small to mid-size operations. One IP handles everything: transactional, marketing, any other streams. Reputation accumulates on the single IP; complaint pressure from any stream affects all delivery.

Works fine when daily volume stays under 20K and complaint rates are low (under 0.1%). Past those thresholds, throttling and reputation pressure start causing problems that extra IPs would mitigate.

dedicated vs shared

When dedicated IPs matter, when shared works.

Toggle the criteria. Dedicated IPs aren't always better; shared IPs are sometimes the right architecture. The honest tradeoffs depend on volume and reputation strategy.

  us
Dedicated IPv4		 Shared IPv4
(typical hosting)		 SaaS ESP IPs
(Mailgun, AWS SES)
Per-IP cost (monthly) €8 Free (included with hosting) $0 individual / $$ for dedicated
Setup cost €0 (24h delivery) €0 (immediate) $0 / $79+ for dedicated
Year 1 cost (3 IPs) €288 (€96 × 3) €0 directly (shared with neighbours) $948+ for dedicated
Reputation control Full (your sending only) Shared with hosting neighbours Vendor-managed
RBL listing risk from neighbours None (dedicated) Real (range listings can affect you) Vendor's responsibility
Per-IP reputation building Yes (your control) Difficult (shared signals) Vendor's IP, vendor's reputation
FCrDNS / rDNS control Custom per IP Provider-default (often generic) Vendor-set
Per-IP daily volume capacity ~50K (typical commercial) Variable (depends on shared activity) Vendor-throttled
Throttling control Per-IP per-receiver tuned (PowerMTA) Provider-default Vendor-imposed
Burst capacity High (PowerMTA can sustain) Limited by shared infrastructure Vendor-imposed
Neighbour-trigger RBL risk None Real (range listings) None (vendor IP)
Cold start (new IP) handling Warming required (we handle) Shared reputation may help or hurt Vendor handles
Best for Volume + control + isolation Low volume + cost-sensitive Hands-off + vendor-trust

Shared IPs are genuinely fine for low-volume opt-in transactional sending. The reputation isolation benefits of dedicated IPs only matter past certain volume thresholds. SaaS ESP IPs (Mailgun, AWS SES) are the right fit when operational hands-off matters more than control. Dedicated IPs are right when self-hosted control + volume + reputation isolation align as priorities.

honest fit assessment

Who needs extra IPs, who doesn't.

good fit
  • Operations past 20K daily on single IP. Per-IP throttling at major receivers starts to matter at this volume; spreading across 2-3 IPs maintains delivery flow.
  • Multi-stream operations (transactional + marketing + cold) where stream isolation prevents cross-contamination of reputation.
  • Multi-brand or multi-tenant sending where per-brand IP isolation is operational requirement (lead-gen agencies, SaaS with deliverability commitments).
  • Recovery customers who completed Reputation Recovery and want fresh IPs to maintain clean reputation post-recovery.
  • Cold outreach scaling where IP pool spreads complaint pressure. Subdomain Rotation Pool addresses this differently; IP pool is complementary at higher volumes.
  • Compliance-driven sending needing documented IP-level isolation between regulated and unregulated streams.
poor fit
  • Single-stream sending under 20K daily. Single IP works fine. Adding IPs adds complexity (warming, monitoring, configuration) without proportional benefit at this scale.
  • You expect IP rotation to fix bad sending practices. Adding IPs doesn't fix complaint-rate issues, content problems, or list quality. Those need to be addressed at the source. Audit (€299) starts that work.
  • You need many IPs but no warming budget. Each new IP requires 30-day warming. If you need 10 IPs immediately at full capacity, that's 10 separate 30-day warming projects. Multi-domain Warmup (€599) bundles managed warming if needed.
  • You're using shared hosting and unwilling to migrate. Extra IPs from us require either (a) hosting them on your infrastructure or (b) using our infrastructure. Not compatible with cPanel-style shared hosting.
  • You don't need PowerMTA-level control. If your sending volume doesn't justify dedicated MTA software, dedicated IPs probably also don't apply. Mailgun or similar SaaS ESP fits.
  • Snowshoe-pattern intent. Cycling many IPs through unwarmed sending of unsolicited mail. Receivers detect snowshoe patterns regardless of IP architecture; we don't operate that pattern.
scope of allocation

What's in the €8/month.

01

Dedicated IPv4 from clean range

IPs come from ranges with no historical RBL listings, no shared-tenant baggage, no abuse history. Pre-checked against 84 RBLs before allocation. If pre-allocation check shows any listing, IP gets swapped before delivery to you.

IPv4 only. We don't allocate IPv6 separately because most major receivers (Gmail, Outlook, Yahoo) treat IPv6 reputation differently from IPv4, and dedicated IPv6 for commercial sending has limited adoption. IPv6 sending available via your existing infrastructure if needed.

02

Custom rDNS configured

Per-IP PTR record matching your sending domain pattern. Examples: mta1.brand.com for brand-themed, send01.brand.com for numbered, your custom convention if you have one.

rDNS configured on the IP allocation side (provider PTR record); forward DNS configured on your domain side (matching A record pointing back to the IP). FCrDNS verification confirms forward and reverse match.

03

FCrDNS verified, HELO aligned

Forward-confirmed reverse DNS validated: PTR record points to hostname, hostname resolves to original IP. HELO/EHLO in MTA configured to match the rDNS hostname; alignment keeps receivers from flagging mismatched HELO.

FCrDNS misconfiguration is one of the most common silent problems in self-hosted sending. We verify FCrDNS at allocation and again after MTA configuration; ongoing FCrDNS monitoring catches drift.

04

MTA configuration support

PowerMTA: VMTA mapping for the new IP, throttling rules template, DKIM signing block update. Postfix: transport map entries, smtp_bind_address4 configuration, sender- dependent transport routing. We configure based on your existing MTA stack.

Configuration support for the IP allocation only. Broader MTA configuration (reorganisation, performance tuning, architecture changes) bills at consulting rates (€199/h) or via PowerMTA + MailWizz Setup (€299) if scope is full setup.

05

Initial warming included

Each new IP starts with zero reputation. We warm to ~1,500 daily over 30 days as part of allocation. Day 1: ~50 to seed addresses. Day 7: ~300. Day 14: ~700. Day 21: ~1,200. Day 30: ~1,500 sustained.

For higher final capacity (3K+ daily) or accelerated warming, bundle Multi-domain Warmup project (€599) which handles managed warming through to higher volume targets. Standard warming covers most operations; high-capacity warming applies to specific cases.

06

RBL monitoring included

Each IP polled across 84 RBLs every 15 minutes. Alerts via Telegram immediately when any listing detected. Same coverage as standalone Deliverability Monitoring (€49/mo) applied per-IP at no additional cost.

For full reputation monitoring (Postmaster Tools, SNDS, content classifier estimates, FBL), subscribe to Deliverability Monitoring separately. Per-IP RBL coverage is included free; broader monitoring is the standalone product.

07

Per-IP cancellation flexibility

Cancel individual IPs anytime. Subscription ends at month boundary for that specific IP. Other IPs in your allocation remain unchanged. No fleet cancellation required.

On cancellation, IP returns to available pool after 30 days (gives time for any in-flight traffic to clear, prevents immediate reuse by other customers that could create confusion).

08

Flat pricing

All IPs at €8/IP/month. No bulk tiers, no minimum commitments, no fleet-wide cancellation required. Each IP billed independently; cancel any individual IP anytime with prorating on next cycle.

Most operations need 2-4 extra IPs. Past 10 IPs typically indicates a different architectural need (subdomain pool, multi-domain, fleet operations) where consulting on architecture (€199/h) helps before scaling IPs alone.

questions before you order

Frequently asked.

When do I need extra IPs vs sticking with one?

Extra IPs make sense when: daily volume exceeds 20-30K on a single IP and throttling becomes an issue, you run multiple sending streams that benefit from reputation isolation, you operate multiple brands needing cross-contamination prevention.

Single IP works fine for: under 20K daily on a single stream, single-brand operations, opt-in transactional sending where complaint rates stay low. Don't add IPs for the sake of it; the warming and monitoring overhead doesn't pay back without operational justification.

Do I need to warm extra IPs separately?

Yes. Each new IP starts with zero reputation; receivers see it as new sender regardless of your existing IP's reputation. Standard warming (included in subscription): ~1,500 daily over 30 days. For higher final capacity, Multi-domain Warmup (€599) handles managed warming to higher targets.

Skipping warming is the most common mistake we see in self-managed IP allocation. Sending high volume from a day-1 IP triggers receiver throttling immediately and damages the new IP's reputation before it's established. The 30-day warming discipline matters.

Why €8/month per IP? Other providers charge less.

Some providers charge less for shared-tenant IPs without custom rDNS, FCrDNS verification, or RBL pre-checking. Cheaper IPs typically come with shared reputation risk (neighbour-trigger RBL listings affecting you) and generic rDNS (provider default like mta-12-34-56-78.providerXYZ.com) that signals shared infrastructure to receivers.

Our €8/month covers: dedicated allocation, RBL pre-check against 84 lists, custom rDNS configured, FCrDNS verified, ongoing 15-minute RBL polling, MTA configuration support, initial 30-day warming. Most cheaper alternatives cover one or two of those items, not all.

Can I bring my own IP and have you configure rDNS?

Yes, separate service. rDNS configuration on customer-owned IP: €29 one-time per IP. Includes: PTR record configuration with your hosting provider, FCrDNS verification, HELO alignment, MTA configuration support. Doesn't include RBL monitoring or ongoing maintenance.

For ongoing per-IP RBL monitoring on customer-owned IPs, subscribe to Deliverability Monitoring (€49/mo) which covers any IPs you register. The €8/mo price includes monitoring; standalone monitoring at €49/mo covers multiple IPs.

What jurisdiction are the IPs in?

Standard locations: Bulgaria, Romania, Moldova, Panama, Hong Kong, Singapore, Ukraine. Specific country selectable at allocation time. EU jurisdictions typical for cold outreach (regulatory + sender reputation reasons); other locations available for specific use cases.

For specific jurisdiction requirements (data residency compliance, sanctions considerations, sender-recipient geographic alignment), mention at allocation. Some jurisdictions have allocation lead time (10-14 days vs standard 24 hours).

What if an IP gets RBL-listed?

We monitor all IPs continuously; alerts within 15 minutes of listing detection. For listings caused by your sending (high complaint rate, content issues, list problems), Blacklist Removal (€149) is the remediation product. For listings outside your control (range listings, shared-infrastructure issues, false positives), we handle delisting at no charge.

Distinguishing self-inflicted from external causes is standard part of investigation. Reputation Insurance (€129/mo) covers SLA-tier protection against external- cause listings; standalone IP allocation doesn't have SLA component.

How do I cancel a specific IP?

Telegram message specifying which IP to cancel. Subscription for that IP ends at month boundary. Other IPs in your allocation continue unchanged. No fleet-cancellation requirement; per-IP granularity throughout.

On cancellation, IP returns to pool after 30-day cool-down. Your existing IPs and infrastructure unaffected. If you want to re-add the same IP later, we'll allocate a different clean IP rather than reusing the cancelled one.

Can I get IPs from specific RBL-clean ranges?

Yes for special cases. Specific range requirements (avoiding certain ASNs, requiring specific geographic ranges, avoiding historical-issue ranges) can be accommodated. Some requirements have lead time (10-14 days vs standard 24 hours) and may have premium pricing.

Most operations don't need this. Our standard pool is actively maintained; ranges are clean, RBL-checked, low- risk. For senders with specific compliance requirements (financial services, healthcare with specific routing requirements), let us know at allocation; we work within your constraints.

How does payment work?

Monthly billing in advance. €8 per IP charged on subscription anniversary. Flat pricing applies regardless of fleet size. Payable in any of our 11 supported cryptocurrencies via self-hosted BTCPay. Pre-paid 6-month subscription: 5% discount. Pre-paid 12-month: 10% discount.

also relevant

Related services and references.

project

Multi-domain Warmup

For multi-brand operations needing both IP and domain isolation. €599.

→ recurring

Subdomain Rotation Pool

Alternative to multi-IP for cold outreach scaling. €99/mo.

→ one-time

Custom rDNS

For configuring rDNS on customer-owned IPs. €19 per IP.

→ one-time

Blacklist Removal

RBL listing remediation when listings appear. €149.

→ recurring

Deliverability Monitoring

Per-IP RBL monitoring included; standalone for full reputation tracking. €49/mo.

→ per hour

Consulting

For IP allocation strategy review or architectural decisions.

→

IPv4 allocation realities in 2026 and what additional IPs actually provide

IPv4 address scarcity has been a structural constraint since approximately 2015 when the major regional internet registries depleted their primary allocation pools. Through 2020-2026 the constraint has tightened progressively; market prices for IPv4 addresses have risen from USD 12-18 per address in 2018 to USD 40-65 per address in 2026 depending on block size and seller.

What additional IPv4 addresses actually provide for sending operations: reputation isolation across sending categories (transactional separated from marketing, opt-in separated from cold outreach), capacity expansion when single-IP volume approaches receiver-side rate limits, geographic distribution when sending operations span multiple regions with different receiver expectations, redundancy for incident response when reputation events affect specific IPs.

What additional IPv4 addresses do not provide: automatic deliverability improvement (additional IPs without reputation are worse than fewer IPs with established reputation), permanent reputation protection (any IP can develop reputation issues regardless of how many other IPs the operator has), independence from underlying network reputation (multiple IPs in the same /24 share network-level reputation factors), bypass of operational discipline requirements (more IPs do not substitute for proper authentication, list hygiene, content quality).

For operators evaluating whether they need additional IPs, the structural question is whether their current IP configuration limits their operational requirements. Operations sending in a single category at moderate volume rarely need additional IPs. Operations with diversified sending across multiple categories or substantial volume that approaches per-IP rate limits benefit from additional allocation.

IPv4 allocation tiers and pricing

Our IPv4 allocation tiers reflect the underlying market pricing plus operational support overhead. The pricing structure is transparent: customers see the marginal cost of each additional IP rather than complex bundled pricing that obscures the real allocation cost.

Single additional IP: EUR 8 monthly. Covers the underlying address rental cost plus rDNS configuration, abuse contact management, monitoring integration. Suitable for operators expanding from baseline allocation by one or two IPs.

Block allocations (4 IPs, 8 IPs, 16 IPs): EUR 28, EUR 54, EUR 96 monthly respectively. The block pricing reflects volume efficiencies in our underlying allocation; customers receive better per-IP pricing for larger blocks. Suitable for operators with diversified sending requiring multiple IPs per category.

Larger allocations (32 IPs, 64 IPs, 128 IPs and above): EUR 180, EUR 320, EUR 580 monthly respectively. Suitable for ESP-style operations or large senders with substantial diversification requirements. Custom pricing for allocations above 128 IPs based on specific operational requirements.

All tiers include rDNS configuration, abuse contact management, network reputation monitoring at the /24 level, integration with our broader monitoring infrastructure. The pricing is fully inclusive without surprise charges for typical operational requirements.

Operational considerations for multi-IP sending architecture

Adding IPs to a sending operation involves more than provisioning the addresses. The operational considerations below capture what production operators settle on after experiencing the consequences of less-developed approaches.

Warmup planning: new IPs need reputation warmup before they can sustain production volume. Skipping warmup produces predictable delivery problems during the first 30-45 days as receivers develop classification for the unfamiliar IPs. Our standard onboarding includes warmup pacing recommendations matched to customer existing reputation patterns.

Pool segmentation: multi-IP operations benefit from explicit pool segmentation rather than treating all IPs as interchangeable. Common segmentation patterns: transactional pool with strictest reputation requirements, marketing pool with moderate requirements, cold outreach pool with looser requirements but isolated from other categories. The segmentation supports per-pool optimization and prevents cross-category reputation contamination.

Rotation patterns within pools: some operations rotate sending across IPs within a pool to distribute volume and avoid concentrated per-IP usage. Other operations dedicate specific IPs to specific campaigns for clearer reputation attribution. Both patterns work; the choice depends on operational preferences and the specific analytics requirements.

Monitoring per IP: each IP needs independent reputation monitoring because pool-level monitoring obscures per-IP variations. Our monitoring infrastructure tracks per-IP reputation across the major signal sources, with alerting on per-IP anomalies that aggregate pool monitoring might miss until problems compound.

Ready to add capacity?

Telegram order takes 5 minutes. IP delivered with rDNS configured within 24 hours. Initial warming begins immediately; full capacity by day 30. Cancel any IP anytime, no contract.

Order on Telegram → Submit ticket

# Median Telegram response: 12 minutes during operating hours