Skip to content
RECURRING · 15 SUBDOMAINS

Subdomain rotation pool, managed.
Single root, fifteen warmed sending streams.

Cold outreach at scale needs sending diversity to spread complaint pressure. Multi-domain warmup uses separate root domains; subdomain rotation uses one root with multiple warmed subdomains. The choice depends on whether your brand is one identity (subdomains fit) or multiple identities (multi-domain fits). Both are legitimate when done correctly.

We maintain a pool of 15 warmed subdomains under your root domain. Automated rotation logic distributes sending across the pool. When a subdomain accumulates damage (high complaint rate, RBL listing, postmaster downgrade), it gets rotated out and replaced. Continuous reputation monitoring across all subdomains plus the root. €99/month, cancel anytime.

Subscribe on Telegram → See architecture
price €99 / month
subdomains 15 warmed
rotation Automated
commitment none
subdomain rotation vs alternatives

When subdomains fit, when they don't.

Subdomain rotation makes sense when your brand identity is singular but your sending streams are multiple. A SaaS company sending account notices, marketing campaigns, and cold outreach from one brand can route those streams through different subdomains under the same root: billing.acme.com, marketing.acme.com, outreach.acme.com. The brand stays consistent; the reputation per stream isolates. Each subdomain accumulates its own reputation profile at receivers, separate from the others.

Multi-domain warmup makes sense when brand identity is plural. Lead-gen agencies running outreach for multiple clients use separate root domains per client. Each client's reputation stays isolated from the others; cross-contamination doesn't happen because the domains are unrelated. Subdomain rotation can't do this; subdomains under one root share reputation correlation through the root.

The honest tradeoff: subdomains are cheaper to maintain (one DNS root, one SSL certificate strategy, one brand) but carry shared reputation risk through the root. Multi-domain is more expensive (separate DNS per domain, separate authentication setup) but provides stronger isolation. For single-brand cold outreach at scale, subdomain rotation is the right architecture; for multi-brand or multi-tenant cold outreach, multi-domain warmup is the right architecture.

Receivers see both patterns regularly and have learned to distinguish legitimate subdomain operations from snowshoe patterns. Subdomain rotation done legitimately uses warmed subdomains, proper authentication, content patterns consistent with the brand, sending volume per subdomain that matches the warming history. Subdomain rotation done as snowshoe (cycling through unwarmed subdomains, no authentication, generic content) gets penalised. The architecture is shared; intent and execution differ. Our rotation runs the legitimate version because that's the only version that sustains.

how the pool operates

Pool architecture, layer by layer.

Click any layer to see what gets configured at that level. The full stack is what differentiates managed subdomain rotation from manually maintaining 15 subdomains yourself.

vs multi-domain warmup

Subdomain pool vs multi-domain pool.

Both architectures distribute sending across multiple identities. The differences matter for cost, reputation isolation, and operational complexity. Toggle the criteria to see what fits your case.

  us
Subdomain Rotation Pool		 Multi-domain Warmup
(separate roots)		 Single-domain
(no rotation)
Setup cost €0 (included in subscription) €599 (10 domains, 30-day warmup) €0 (you already have one)
Ongoing cost (monthly) €99/mo ~€100-200/mo (monitoring + maintenance) €0 (or €49/mo monitoring)
Domain registration cost €8-15/year (1 domain) €80-150/year (10 domains) €8-15/year (1 domain)
Year 1 total cost ~€1,200 ~€2,000-3,000 ~€20
Reputation isolation Subdomain-level (correlated through root) Domain-level (independent) None (single reputation)
Damage to one subdomain Affects pool partially through root Doesn't affect other domains Affects all sending
Cross-contamination risk Low if warmed properly, real if neglected Very low N/A (one identity)
Maximum sustainable volume ~15K-20K daily across pool ~15K daily across 10 domains ~3K-5K daily before issues
DNS records to maintain 15 subdomain sets (under 1 root) 10 separate root domains 1 root domain
Authentication coordination Per-subdomain DKIM, shared SPF strategy Per-domain everything Single setup
Pool maintenance complexity Medium (rotation + burn recovery) High (10 separate operations) Low (one identity)
Brand consistency High (all under one root) Variable (10 different domains) Highest (single identity)
Recipient visibility of pattern Subtle (subdomain hint only) Visible (multiple domains) None
Best for Single-brand cold outreach scaling Multi-client agencies, multi-brand operations Low-volume opt-in or transactional

The architectures aren't mutually exclusive. Some operators use both: subdomain rotation for primary brand outreach, multi-domain warmup for high-risk segments or A/B campaign comparison. Our Recovery Pack bundles addons that cover both approaches when the operation justifies it. For most senders, one architecture fits the operation cleanly; using both adds complexity without proportional benefit.

when subdomains burn out

Burn-recovery simulator.

Set your daily volume and complaint rate. The simulator estimates how often subdomains get burned out and how the pool recovers. Cold outreach has higher burn rates than opt-in marketing; the math differs sharply.

10,000 daily

Total daily sending across all 15 subdomains. Recommended max around 15-20K daily across the pool.

Complaint rate determines burn frequency. Higher rates burn subdomains faster; pool must replenish faster.

Content quality affects how quickly receivers' content classifiers flag subdomains. Generic templated content burns faster.

burn rate

Expected subdomain burns

Burns per month ~2 subdomains
Burns per quarter ~6 subdomains
Average subdomain lifespan ~4 months

Based on observed burn patterns across our customers' pools. Actual burn rate varies with content quality, list quality, and seasonal factors.

pool stability

Pool composition

Active subdomains needed 15 always
Replacement subdomains warming 2-3 always
Pool rotation completeness ~12 months

Your full subdomain pool turns over completely on this cycle. Newer subdomains carry less reputation history; warming buffer keeps the active 15 from being all-fresh simultaneously.

our recommendation

Strong fit

For your volume and complaint profile, subdomain rotation is well-matched. The burn rate is sustainable; pool maintenance keeps you ahead of damage. Subscribe.

Subscribe on Telegram →

Math caveats: burn rate scales non-linearly with complaint rate; doubling complaints more than doubles burns because receiver reputation systems compound damage. The simulator uses observed burn coefficients across our customer pools. Senders running aggressive outreach (high complaint rate + high volume + low content quality) experience burn rates that exceed pool replenishment capacity; in those cases we recommend either reducing volume, improving content, or switching to multi-domain architecture.

honest fit assessment

Who subscribes, and who shouldn't.

good fit
  • Single-brand cold outreach at scale needing 5K-15K daily volume distributed across multiple sending streams. Subdomain pool keeps brand consistent while diversifying reputation pressure.
  • SaaS companies with multiple sending streams (transactional, marketing, outreach, account notices) who want isolation per stream without separate root domains.
  • Operations with established root reputation that they want to extend rather than replace. Subdomain rotation extends the root; multi-domain replaces it.
  • Long-term cold outreach operations running 6+ months. Burn-recovery management amortises across months; short campaigns don't justify the maintenance overhead.
  • Recent multi-domain warmup customers who want a complementary subdomain pool for additional sending capacity within the same brand.
  • Compliance-driven sending needing isolation between regulated and unregulated streams (regulated industries often require separation between marketing and transactional sending).
poor fit
  • Multi-brand or multi-tenant operations. Subdomain pool ties all sending to one root; cross-brand contamination risk. Use multi-domain warmup instead.
  • Daily volume under 3K. Pool maintenance overhead doesn't pay back at this scale. Single-domain with proper authentication is sufficient.
  • Short-term campaigns under 3 months. Pool warming takes 4-6 weeks; you've only got partial warming completed before the campaign ends. Use Multi-domain Warmup project (€599) for batch operations instead.
  • You don't yet have an established root domain. Subdomain rotation extends existing root reputation. Brand-new root (under 30 days registered) doesn't have reputation to extend; warming takes much longer.
  • Aggressive snowshoe-pattern intent. If your goal is high-volume unsolicited mail with complaint-rate masking, this product won't work; the architecture assumes legitimate sending discipline. Receivers will detect snowshoe patterns regardless of architecture.
  • Internal team that already manages subdomains. If you have engineering capacity to maintain 15 subdomains' authentication, monitoring, rotation logic, and burn recovery, paying us duplicates work. Most teams don't have that capacity.
scope of operation

What's in the €99/month.

01

Subdomain naming + DNS publication

We publish 15 subdomains under your root with naming convention agreed at intake. Common patterns: descriptive (send, mail, outreach, connect, reach), product-themed (team, app, platform), or numbered (send01, send02...). Descriptive patterns work best for brand consistency; numbered patterns are more obvious to recipients but simpler operationally.

We avoid suspicious patterns (random-looking subdomains, brand-misspellings, known-spam patterns). Each subdomain gets standard A/MX records pointing to sending infrastructure.

02

Per-subdomain authentication

Each subdomain in the pool gets its own SPF record authorising the sending IPs, DKIM 2048-bit RSA key with year-quarter selector, DMARC policy at p=none with rua= reporting active, MTA-STS in testing mode, TLS-RPT companion record. Same standard as our standalone DNS Authentication Setup (€99) executed across the 15-pool.

Quarterly DKIM rotation across all subdomains included. Compliance documentation generated per rotation cycle. For multi-domain DKIM rotation needs beyond the pool, the standalone DKIM Rotation product applies.

03

Initial pool warming (4-6 weeks)

Each subdomain warmed to ~1,000 daily volume before entering active rotation. Warming follows logarithmic ramp (similar to our Multi-domain Warmup) but compressed to 4-6 weeks because subdomains inherit some root domain reputation rather than starting from zero.

During warming weeks, partial volume can be sent through already-warmed subdomains while others continue ramping. Most operators start producing meaningful campaign volume by week 5; full pool capacity ~week 7.

04

Sending IP pool with rDNS

Dedicated IPs allocated to the pool, with custom rDNS configured per IP, FCrDNS verified, HELO aligned. Number of IPs typically 4-8 depending on volume; subdomains don't get unique IPs (unnecessary infrastructure cost) but IP-to-subdomain mapping is consistent so receivers see stable identity per subdomain.

Server jurisdiction your choice from our standard set (BG, RO, MD, PA, HK, SG, UA). EU jurisdictions typical for cold outreach.

05

Rotation logic

Automated distribution across the 15 active subdomains based on per-subdomain capacity (newer subdomains lower, mature subdomains higher), per-receiver throttling patterns, and time-of-day distribution. Rotation isn't random; it's driven by per-subdomain reputation health.

Operator visibility: dashboard shows current per-subdomain volume allocation, capacity, and reputation snapshot. You don't manually pick subdomains for campaigns; the rotation handles it. Manual override available for specific cases (intentional A/B testing, segment isolation).

06

Per-subdomain monitoring

Postmaster Tools data daily per subdomain. SNDS data hourly per IP. RBL polling every 15 minutes. FBL data ingested in real-time. Authentication monitoring hourly. Same coverage as our Deliverability Monitoring (€49/mo standalone) extended across the 15-subdomain pool.

Daily Telegram digest: per-subdomain summary, anomalies, burn-recovery actions taken (or queued). Weekly detailed report: pool composition, replacement subdomain status, ongoing actions.

07

Burn-recovery management

When a subdomain accumulates damage (Postmaster red, multiple RBL listings, complaint rate sustained over threshold, or content classifier severely flagging), we rotate it out of active sending. New replacement subdomain from warming buffer enters rotation. Damaged subdomain either rehabilitated (if salvageable) or retired (if not).

Pool stays at 15 active throughout. Replacement buffer (typically 2-3 subdomains) maintained continuously to handle expected burn rate without triggering reputation crisis when one burns. Burns are normal; pool design assumes them.

08

Quarterly pool review

Detailed assessment every 90 days. Pool composition vs current sending patterns, underperformer identification, naming convention review, retirement schedule for specific subdomains.

Recommendations delivered: subdomains to retire even if still functional (preventive rotation), naming pattern adjustments based on observed receiver behaviour, volume rebalancing across pool. You approve, we execute.

questions before you subscribe

Frequently asked.

Is this just snowshoe spam?

No. Snowshoe spam uses many disposable domains across many IPs to evade reputation tracking on bulk unsolicited mail. Subdomain rotation under a single root domain inherits the root's reputation, uses warmed subdomains rather than burner domains, and routes through stable infrastructure with proper authentication. The architecture and intent differ; receivers can tell the difference.

That said, subdomain rotation can be misused as snowshoe (cycling unwarmed subdomains for unsolicited bulk mail). We don't operate that way; it's not a sustainable architecture, and our customers running legitimate cold outreach get penalised when they share rotation infrastructure with snowshoe operators. Our operating model assumes legitimate sending intent.

Do receivers detect subdomain rotation?

Receivers see subdomain sending and infer reputation across the root. Done legitimately with proper warming and authentication, the pattern looks like normal multi-stream operations from a single brand. Done sloppily (no warming, missing authentication, content patterns matching unsolicited mail), it looks like snowshoe and gets penalised.

We've operated subdomain pools across 50+ customer roots for 18+ months. No customer pool has been categorically penalised by Gmail, Microsoft, Yahoo, Apple, or AOL when our rotation hygiene is followed. Individual subdomains burn out (expected); the pool architecture absorbs that damage by rotating to fresh subdomains. Pool itself sustains.

What if my root domain gets damaged?

Root damage affects the entire pool. If complaint rate climbs across multiple subdomains simultaneously, root reputation degrades and individual subdomain reputation doesn't fully isolate. We monitor for this pattern and alert before it becomes catastrophic.

Root damage usually has a fixable cause: content drift across all streams, list quality degradation, infrastructure misconfiguration. Identification + remediation typically takes 2-4 weeks. For severe root damage, the honest answer is sometimes to retire the root and migrate to fresh infrastructure. We surface that conversation when evidence supports it.

How often do subdomains burn out?

Depends on volume and complaint rate. The simulator on this page estimates for your specific profile. Typical ranges:

  • Opt-in marketing (0.05% complaint): ~1 burn per quarter
  • Typical cold outreach (0.15% complaint): ~2 burns per month
  • Aggressive cold outreach (0.30% complaint): ~3-4 burns per month
  • High-friction segments (0.5%+): pool replenishment can't keep up; reduce volume or improve content

Average subdomain lifespan in our customer pools: 3-6 months for cold outreach, 8-12 months for typical commercial sending.

Can I add more than 15 subdomains?

Yes, custom pool sizes available. 20 subdomains: €129/mo. 25 subdomains: €159/mo. 30+ subdomains: custom quote. Additional pool capacity makes sense for very-high-volume operations (15K+ daily) or high-burn cases (aggressive cold outreach with 0.4%+ complaint rate).

Most operators don't need more than 15. Larger pools increase operational complexity without proportional benefit beyond a certain volume. If your need exceeds 15, we suggest discussing whether multi-domain warmup or architecture review (consulting hour) might be more appropriate.

What happens if I cancel?

Cancel anytime via Telegram. No notice period. Last-month handover delivered: pool composition, per-subdomain reputation snapshot, recommended next steps for self-management or retirement.

Subdomains remain in your DNS after cancellation (you own the root). Without ongoing rotation management, burn-recovery becomes your responsibility; without it, individual subdomains accumulate damage over time and the pool degrades. Some customers continue with manual rotation; some retire the pool entirely. Both work.

Can I bring my own warmed subdomains?

Yes, but coordination required. Existing subdomains with history get integrated into the rotation; we audit them for current reputation, document baseline metrics, and include in pool. Subdomains with damage need rehabilitation before entering active rotation.

Most operators don't have pre-existing warmed subdomains because the maintenance overhead of warming subdomains manually is what motivated them to subscribe. But if you do have them, we don't waste them.

How does this interact with my existing email setup?

Subdomain rotation is sending-side infrastructure. It doesn't affect your inbound mail (MX records on the root are unchanged). Your transactional sending from the root continues unaffected; subdomain pool handles the sending streams that benefit from distribution.

For complete isolation between transactional (root) and outreach (subdomain pool), we recommend separate infrastructure paths. Our PowerMTA + MailWizz Setup covers that architecture if you don't have it.

How does payment work?

Monthly billing in advance. Initial month covers warming phase (subdomains entering rotation as they complete warming). First full-pool month is typically month 2. 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 or multi-client operations. Separate roots, stronger isolation. €599.

→ one-time

DNS Authentication Setup

Per-subdomain DNS records included in subscription; this is the standalone equivalent.

→ recurring

DKIM Key Rotation

Quarterly rotation across pool included; standalone for non-pool domains.

→ recurring

Deliverability Monitoring

Per-subdomain monitoring included; standalone for non-pool domains.

→ bundle

Cold Outreach Bundle

Subdomain rotation + VPS + multi-domain warmup + ongoing addons bundled.

→ per hour

Consulting

If unsure between subdomain pool, multi-domain, or other architecture.

→

Subdomain rotation architecture for production sending

Subdomain rotation distributes sending across multiple subdomains under a primary domain to support specific operational requirements. The pattern emerged through 2018-2024 as receiver-side enforcement increased and senders found that single-subdomain operations produced limitations that multi-subdomain operations did not.

The mechanical implementation: primary brand domain (example.com) hosts the customer-facing identity, operational subdomains (mail.example.com, news.example.com, send.example.com, etc.) host the actual sending activity. Each operational subdomain has independent SPF, DKIM, DMARC configuration; receivers evaluate each subdomain reputation independently rather than aggregating into a single domain-level reputation.

The structural benefits: reputation isolation across sending categories (transactional from marketing, opt-in from cold outreach), incident containment (reputation events on one subdomain do not automatically affect others), capacity expansion (per-subdomain volume can scale independently within per-subdomain rate limits), brand protection (primary brand domain protected from operational reputation events).

The structural limitations: organizational domain reputation still affects subdomain reputation at some receivers; the isolation is partial rather than complete. Some receivers explicitly correlate subdomain behaviors back to the organizational domain. The implementation complexity increases with the number of subdomains; operational discipline must be maintained across all subdomains rather than concentrated in one place.

Common subdomain rotation patterns and when each applies

Several specific subdomain rotation patterns serve different operational requirements. The pattern choice should match the senders specific situation.

Pattern 1: category-based separation. Subdomains correspond to sending categories: transactional.example.com, marketing.example.com, prospecting.example.com. The pattern provides clear reputation attribution per category and supports per-category operational tuning. Suitable for operations with distinct sending categories and clear category boundaries.

Pattern 2: temporal rotation. Subdomains rotate based on time periods (weekly, monthly): send-2026w08.example.com, send-2026w09.example.com. The pattern produces fresh subdomain identity for each rotation period; older subdomains can be retired or repurposed. Suitable for cold outreach where receiver-side classification benefits from rotating sender identity.

Pattern 3: campaign-based isolation. Subdomains correspond to specific campaign types or sources: launches.example.com, newsletter.example.com, alerts.example.com. The pattern provides granular reputation attribution and supports campaign-specific authentication policies. Suitable for operations with many distinct campaign types each warranting independent reputation tracking.

Pattern 4: customer-based separation (for ESP-style operations). Each customer gets their own subdomain under operator-controlled apex: customer-acme.example-esp.com, customer-globex.example-esp.com. The pattern produces customer-level isolation while operating from shared infrastructure. Suitable for ESP operations balancing infrastructure economics with reputation isolation.

Hybrid patterns combining elements of the above are common in practice. Most production operations use 2-3 patterns simultaneously: category separation for the broad structure, temporal rotation for cold outreach within the prospecting category, customer separation for any ESP-style components. The combination produces the operational outcomes that single-pattern approaches do not.

Pricing structure and operational coverage

Subdomain rotation managed service handles the operational complexity of multi-subdomain sending. The standard tier at EUR 99 monthly covers operations with up to 10 active subdomains under a single organizational domain.

Professional tier at EUR 249 monthly covers operations with up to 30 active subdomains, multi-domain coordination, advanced rotation patterns including temporal rotation. Suitable for cold outreach operations or campaign-heavy operations requiring granular reputation attribution.

Enterprise tier at EUR 599 monthly covers ESP-style operations with subdomain management across substantial customer bases. Includes custom rotation patterns, integration with customer-facing management interfaces, dedicated support for subdomain-related operations.

All tiers include DNS management for the subdomains, authentication configuration across all subdomains, reputation monitoring per subdomain, coordination of rotation events when applicable. The pricing is fully inclusive without surprise charges for typical subdomain operations within the tier scope.

Ready to scale single-brand cold outreach?

Telegram subscription takes 15 minutes. Initial warming begins within 48 hours. Partial pool capacity available by week 4; full pool capacity by week 7. Cancel anytime, no contract. Most subscribers run the pool for 6-18 months as their primary cold outreach infrastructure.

Subscribe on Telegram → Submit ticket

# Median Telegram response: 12 minutes during operating hours