Skip to content
RECURRING · 90% INBOX SLA

Reputation insurance, with honest math.
90% inbox SLA at €129/month — credit if we miss.

Most "deliverability guarantees" in this industry are marketing fiction. Vendors promise 99% inbox without telling you the measurement methodology, the receiver scope, or the scenarios that void the guarantee. We do this differently: specific 90% target across named receivers, continuous measurement via seed-list testing, defined credit policy when we miss, and honest scope on what voids coverage.

What this is: insurance against bad luck. RBL listings outside your control, infrastructure incidents, receiver algorithm changes, third-party complications. What this isn't: protection against bad sending practices. If you send unsolicited mail with high complaint rates, no SLA from anyone makes that work; we won't claim otherwise.

Subscribe on Telegram → SLA mechanics
price €129 / month
SLA target 90% inbox
measurement Continuous seeds
commitment none
why this exists

Insurance vs guarantee. The framing matters.

Real insurance economics: pool risk across many customers, price the premium below expected damage, pay out when insured events occur. The product makes financial sense for customers when their expected damage exceeds the premium. Insurance doesn't make money for customers in any single year; it makes them whole when bad events occur and protects them from outlier damage.

Most deliverability "guarantees" violate insurance principles. They promise outcomes the vendor doesn't control (Gmail's algorithm changes), exclude the things that actually go wrong (your content drift), and credit token amounts that don't offset real damage. The math doesn't work out for customers because the product isn't actually insurance; it's marketing dressed as guarantee.

Our reputation insurance is genuine insurance. The covered events are events outside your direct control: RBL listings where the cause is shared infrastructure or external trigger, receiver algorithm changes that broadly affect placement across senders, infrastructure incidents at our hosting providers. The exclusions are clear: self-inflicted issues (spam content, list quality, sustained high complaint rates) aren't insured because no insurance product can cover those economically. The credit amounts are meaningful relative to the premium (50% for 80-89%, 100% for under 80%) so when we miss, you get materially reimbursed.

The product makes economic sense for senders past 50K daily volume where a single placement incident generates more lost revenue than the annual premium (€1,548). Below that volume, the math typically doesn't work; we recommend cheaper alternatives (standalone monitoring + as-needed remediation) rather than selling you insurance that won't pay back.

how the SLA works

SLA mechanics, step by step.

Click each step to see how measurement, credits, and remediation work. Transparency on mechanics is what differentiates real insurance from marketing-as-guarantee.

→ → → →
step 1 of 5

Continuous seed-list testing

We run inbox placement tests 4 times per week using 60+ seed addresses across Gmail, Outlook, Yahoo, Apple, AOL. Tests use representative content from your typical sending (matched to your campaign patterns rather than synthetic content).

Per-receiver inbox/spam/missing counts captured. Weekly aggregates roll up to monthly SLA scoring. Methodology documented and reproducible; you can verify the data quality independently if you want.

what's insured, what isn't

When SLA pays out, when it doesn't.

Eight common scenarios. Click each to see whether the SLA covers it and why. Honest scope; the exclusions are the things your sending practices control.

covered scenario

Spamhaus DBL listing on shared IP range

Status: Covered by SLA.

When a Spamhaus DBL listing affects your IP because of activity on shared infrastructure (a neighbour trigger, range-level listing, abuse from another tenant), the SLA applies. Placement degradation from the listing counts toward monthly SLA evaluation. Prioritised remediation begins immediately: we investigate the listing, coordinate with Spamhaus and hosting provider, work toward delisting.

Real cases observed: 3 SLA events triggered by Spamhaus DBL across our customer base in 2025. Average remediation time 4-7 days. SLA credits applied for the affected month per policy.

does insurance pay back for you?

Honest insurance economics calculator.

Insurance only makes sense above certain volume thresholds. Adjust the inputs to see your specific case. The calculator honestly tells you when insurance doesn't pay back and recommends alternatives.

100,000 daily

Total daily volume across covered streams. Insurance scope per subscription is one operation; multi-instance ops scale with multi-subscription.

€0.020 per message

Marketing emails: typically €0.005-0.05. Transactional: typically €0.05-0.50 (account notices, receipts, verification). Cold outreach: €0.10-2.00 per delivered.

2 incidents/year

SLA-covered incidents (RBL listings outside your control, infrastructure events, third-party issues). Most ops see 1-3 per year; volatile environments may see more.

cost path

Insurance economics

Annual premium €1,548
Damage per uncovered incident €7,000
Annual expected damage (no insurance) €14,000
Net annual savings (insurance) €5,000+
verdict

Insurance pays back

For your sending profile, reputation insurance is economically positive. Annual premium recovers from expected covered-incident damage. Subscribe.

Subscribe on Telegram →
alternative paths

If insurance doesn't fit

  • Standalone Monitoring (€49/mo): catches incidents but no SLA credit.
  • As-needed remediation: Audit (€299), Blacklist Removal (€149), Recovery (€999) when issues hit.
  • Both combined for active management without premium-style insurance commitment.

For low-volume operations (under 50K daily), the alternative paths typically cost less than insurance over a year while providing similar protection.

Math caveats: damage estimate assumes 5-day duration of incident impact at typical placement degradation. Real incidents vary; some clear in hours, some persist weeks. The simulator uses conservative averages from observed customer incidents. Per-message revenue values are approximate; actual values depend on your business model (transactional senders typically have higher per-message value than marketing senders).

honest fit assessment

Who subscribes, and who shouldn't.

good fit
  • High-volume operations past 50K daily. Single covered incident generates more damage than annual premium; insurance economically positive.
  • Transactional sending with high per-message value. Account notices, signed receipts, security notifications. Damage from placement issues compounds beyond simple revenue impact.
  • Compliance-driven sending needing documented SLA evidence for vendor agreements with end customers (SaaS providers including deliverability commitments to their clients).
  • Operations with complex shared infrastructure (multi-tenant hosting, shared IP ranges) where neighbour-trigger risks elevate.
  • Recently-recovered reputation customers who completed Reputation Recovery and want ongoing premium protection during the sustained-recovery period.
  • Operations preferring predictable-cost over surprise-incident-cost. Some operators value the budget predictability even when insurance economics are marginal; that preference is rational.
poor fit
  • Low-volume sending under 30K daily. Premium typically exceeds expected covered-incident damage. Standalone Monitoring (€49/mo) plus as-needed remediation costs less.
  • Aggressive cold outreach with high complaint rates. Most issues are excluded as self-inflicted; SLA won't pay back. Subdomain Rotation Pool (€99/mo) addresses complaint-rate-driven issues better.
  • You expect insurance to cover content / list issues. No insurance product covers self-inflicted issues. If your business model relies on aggressive sending practices, accept the inherent reputation risk; don't pay for insurance that won't apply.
  • You want 99% inbox guarantee. 99% inbox is unrealistic; vendors who promise it are misleading. We promise 90% because that's what disciplined operations actually achieve. If 90% feels low, your expectations may be misaligned with reality.
  • You can't afford the premium. €129/month is meaningful spend. If the budget pressure is real, prioritise actual deliverability work (Audit, DNS Auth, DKIM Rotation) over insurance.
  • Single-server transactional under 100K daily. Risk profile likely doesn't justify premium. Audit (€299) + Monitoring (€49/mo) typically suffices.
scope of insurance

What's in the €129/month.

01

90% inbox SLA across major receivers

Inbox placement target across Gmail, Outlook/Hotmail, Yahoo, Apple iCloud, AOL. Measured monthly via continuous seed-list testing. SLA threshold is 90% aggregate inbox rate; below that triggers credits per policy.

Why 90% not 99%: 99% is unrealistic. Disciplined sending operations reach 92-96% in healthy months; the natural variability of receiver algorithms creates 4-8% variance even in clean operations. 90% is the threshold we can credibly maintain without manipulating measurement.

02

Continuous seed-list testing

4 inbox placement tests per week (~16 per month). 60+ seed addresses per test across covered receivers. Content matched to your typical campaigns rather than synthetic content; methodology documented for transparency.

Equivalent of standalone Inbox Placement Test (€39 each) executed at 4x weekly cadence. Standalone equivalent would cost ~€2,496/year; bundled into €129/month insurance subscription. Already substantial value before considering SLA mechanics.

03

Credit policy when SLA missed

Two-tier credit. Monthly inbox rate 80-89%: 50% credit (€64.50). Below 80%: 100% credit (€129). Credit applies to next month's subscription. Maximum credit per calendar year: 6 months of full subscription (€774); beyond that we recommend cancelling rather than continuing.

Repeated SLA failures suggest insurance isn't the right product for your situation. We don't keep customers in insurance subscriptions where the math is clearly broken; we'll honestly recommend alternative paths if covered incidents exceed expected frequency.

04

Prioritised remediation

When SLA at risk (placement trending toward 80%, RBL listing detected, infrastructure incident), we move you to top of remediation queue. Investigation begins same hour for high-severity events; standard customers might wait 4-12 hours.

Remediation work itself bills at standard rates (Blacklist Removal €149, Audit €299, Recovery €999). Insurance doesn't include free remediation; it includes free prioritisation. Self-inflicted issues continue to bill normally because remediation cost is real regardless of who caused the issue.

05

Continuous monitoring included

Equivalent of standalone Deliverability Monitoring (€49/mo) bundled into the subscription. Postmaster Tools daily, SNDS hourly, 84 RBLs every 15 minutes, FBL real-time, content classifier estimates weekly. Same coverage as standalone; integrated with SLA evaluation.

06

Documented incident reports

When SLA-relevant events occur, we document: cause, timeline, remediation actions, outcome, prevention recommendations. Reports stored in your customer portal; audit-ready for compliance reviewers, vendor agreements with your end customers, internal incident reviews.

Reports include enough detail to satisfy SOC 2 incident evidence requirements without exposing infrastructure specifics that wouldn't be appropriate for external review. Format refined over multiple compliance audits at customer sites.

07

Annual SLA scope review

What's covered evolves as receiver behaviour, infrastructure, and your operation change. Annual review with you to ensure scope stays aligned: covered receivers, covered event types, exclusion clarifications, premium adjustments if warranted.

Reviews are honest conversations, not upsell calls. If insurance isn't paying back for your case, we'll say so and recommend alternatives. The relationship is more important than retention metrics.

08

What's NOT covered

Self-inflicted issues: spam content, list quality problems, sustained complaint rate above 0.3%, unsolicited bulk sending, DNS modifications without coordination, content classifier flags from your authoring choices.

Excluded receivers: smaller regional providers (Mail.ru, Yandex, GMX, ProtonMail, Zoho). Those are measured as informational signals but don't count toward SLA aggregate. Including them would create gaming opportunities; the 5 covered receivers represent typical commercial sending volume.

questions before you subscribe

Frequently asked.

What does the 90% SLA actually guarantee?

Specific: 90% inbox placement at major receivers (Gmail, Outlook, Yahoo, Apple, AOL) measured monthly via continuous seed-list testing.

Mechanics: 4 tests per week, 60+ seeds each, content matched to your typical campaigns. Monthly aggregation determines SLA evaluation. Below 90% triggers credit policy.

Credits: 80-89% inbox = 50% credit (€64.50). Under 80% = 100% credit (€129). Applied to next month's subscription.

When does the SLA NOT apply?

Self-inflicted issues. The exclusions are deliberate: no insurance product can economically cover problems caused by the insured party's own choices. Specifically excluded:

Spam content: classifier flags from your authoring choices. List quality: sustained complaint rate above 0.3%, scraped lists, unsolicited bulk. Self-inflicted DNS issues: modifying records without coordination breaking authentication. Volume violations: sending bursts that violate receiver throttling patterns. Content drift: templates shifting toward spam-classifier triggers over time.

Honest framing: insurance against bad luck, not against bad practices.

Why 90% and not 99%?

99% inbox is unrealistic. Receiver algorithms have natural variability that creates 4-8% variance even in clean operations. Disciplined sending reaches 92-96% in healthy months; nobody sustainably hits 99%.

Vendors promising 99% are doing one of three things: measuring against a methodology that excludes the receivers you actually care about, defining "delivered" loosely (queue acceptance, not folder placement), or simply misleading customers about realistic outcomes. We promise 90% because that's what serious operations achieve and what we can credibly defend.

How does prioritised remediation differ from regular customers?

Insurance customers go to top of remediation queue. Standard customers might wait 4-12 hours for high-severity issues during operating hours; insurance customers get same-hour response.

Remediation work itself (blacklist removal, audit, recovery) bills at standard rates. Prioritisation accelerates when we get to your case, not the cost of the work itself. For severe events, the time savings can matter substantially (a 12-hour delay during an active incident accumulates damage).

What if I have repeated SLA failures?

Credit cap is 6 months of full subscription per calendar year (€774). If your operation triggers more SLA failures than that, insurance isn't the right product for your situation. We'll honestly recommend alternatives: architectural review, audit + recovery sequence, infrastructure migration.

Repeated SLA failures usually point to root-cause issues insurance doesn't address: shared-infrastructure problems (move to dedicated), content/list issues (excluded from SLA but real), broken sending architecture. Insurance credits don't fix the underlying issue.

How do I know the seed-list testing is honest?

Methodology documented in your customer portal. You can independently verify by running standalone Inbox Placement Tests (€39 each) and comparing to our SLA measurements. If our results consistently differ from your independent tests, the SLA mechanism breaks; we'd lose credibility and customers fast.

Receivers we use, content patterns, sample sizes are all disclosed. Honest measurement is the foundation; without it, the insurance product collapses. We have economic incentive to measure honestly because dishonest measurement creates SLA disputes that cost more than the credits would.

Can I add this to existing subscriptions?

Yes. Common pattern: customers running Monitoring (€49/mo) and Subdomain Rotation Pool (€99/mo) add insurance for additional protection. Insurance bundles Monitoring already; if you have standalone Monitoring, adding insurance refunds prorated remainder of standalone.

For Recovery Pack subscribers (post-recovery customers), we recommend adding insurance during the sustained-recovery period (months 3-12 post-recovery) when reputation is most fragile.

What's the cancellation policy?

Cancel anytime via Telegram. Subscription ends at month boundary. Final-month SLA still applies; if SLA missed during final month, credit applied to refund rather than forward subscription.

We don't have win-back or "are you sure?" sales calls. If insurance isn't fitting your operation, cancellation should be friction-free. Honest service > retention metrics.

How does payment work?

Monthly billing in advance. €129 charged on subscription anniversary. Payable in any of our 11 supported cryptocurrencies via self-hosted BTCPay. SLA credits applied as service credit on subsequent invoices; we don't refund credits as cash.

also relevant

Related services and references.

recurring

Deliverability Monitoring

Standalone monitoring without SLA. €49/mo. Bundled into insurance subscription.

→ per-test

Inbox Placement Test

Single tests for measurement validation. €39 each. Bundled at 4x weekly into insurance.

→ one-time

Deliverability Audit

Diagnostic when SLA-covered incidents need root-cause investigation. €299.

→ one-time

Blacklist Removal

RBL listing remediation. Prioritised for insurance subscribers. €149 standard fee.

→ project

Reputation Recovery

Severe-damage recovery sequence. Insurance valuable during post-recovery period.

→ per hour

Consulting

For repeated SLA failure cases or architectural review.

→

What reputation insurance actually covers and what it does not

Reputation insurance is positioned as a service that protects sending operations against reputation incidents that affect deliverability. The framing produces both legitimate value and substantial customer confusion about what is and is not covered.

What the service actually covers: incident response when reputation events occur, expedited remediation through our existing operational infrastructure, evidence preparation for blocklist appeals and receiver communications, coordination of recovery operations across the multi-system reputation landscape. The coverage produces faster recovery times than customers would achieve through ad-hoc engagement.

What the service does not cover: prevention of reputation incidents that customer-side behaviors cause directly (list quality issues, content that triggers receiver-side classification, sending pattern violations of AUP), guaranteed deliverability levels regardless of customer behavior, financial compensation for revenue impact during reputation incidents, replacement of operational discipline that customers need to maintain regardless.

The structural framing that matches the actual service: incident response service with pre-positioned operational resources, not insurance in the financial sense that produces payouts. The naming reflects industry convention rather than precise financial-services terminology; customers should understand the actual operational model rather than treating the name as descriptive of the structure.

Incident response patterns and typical resolution timelines

Reputation incidents fall into several categories with different response patterns and resolution timelines. The patterns below capture what we have observed across customer incidents.

Spamhaus listings: response within 4 hours of customer notification, evidence preparation within 24-48 hours, submission to Spamhaus within 72 hours, typical clearance within 7-14 days depending on case complexity. The pattern produces faster outcomes than ad-hoc engagement because we have institutional context and pre-positioned operational resources.

Postmaster Tools Pass-to-Fail transitions: response within 2 hours of automated alert detection, root cause analysis within 12-24 hours, remediation deployment within 24-72 hours depending on what the root cause requires, transition back to Pass status typically within 7-14 days as receivers update their classification based on the changed conditions.

Sudden blocklist listings across multiple blocklists: response within 2 hours, cascade analysis to identify root cause, evidence preparation for each affected blocklist, sequential submissions following the priority order documented in the rbl-dnsbl wiki entry. Recovery timelines extend with the cascade scope; comprehensive recovery typically runs 14-30 days.

Receiver-specific reputation events (degraded placement at specific receivers without blocklist or Postmaster Tools events): response within 24 hours, diagnostic investigation across the specific receiver behaviors, remediation deployment, monitoring across 30-60 days for sustained recovery. These incidents are typically less acute but more time-consuming because the diagnostic work is harder.

Pricing tiers and operational coverage

Reputation insurance pricing reflects the operational scale and incident-response sophistication each tier provides. The standard tier at EUR 149 monthly covers single-domain operations with response during business hours and standard incident resolution.

Professional tier at EUR 399 monthly covers multi-domain operations with priority response (within 1-2 hours business hours, within 4-8 hours outside business hours), expanded incident handling including blocklist removal at no additional charge, quarterly reputation reviews identifying preventive interventions.

Enterprise tier at EUR 999 monthly covers operations sending above 10M monthly or running ESP-style infrastructure. Includes 24/7 incident response, dedicated technical contact for incident handling, expanded scope including upstream coordination with infrastructure providers when needed, monthly business reviews covering operational and strategic reputation considerations.

All tiers operate with the same fundamental coverage scope; the differences are response time commitments and operational sophistication for the included incident handling. Operators should choose tier based on their operational requirements (response time needs, incident frequency expectations, operational complexity) rather than aspirational positioning.

Limitations of reputation incident response service

Reputation incident response can address incidents that have occurred but cannot prevent incidents that customer-side behaviors will produce. The limitation matters because customers sometimes expect the service to overcome operational practices that produce reputation incidents regardless of provider intervention.

Sustained list quality decay produces reputation incidents that resolve only when the underlying list quality improves. Our incident response can handle individual events; the underlying decay continues until customer operational changes address it. Customers expecting incident response to overcome list quality decay are operating under a structural misunderstanding of what the service can deliver.

Content that triggers receiver-side classification produces reputation incidents that resolve only when content patterns evolve to avoid the triggers. Our incident response can address the immediate event; preventing recurrence requires customer-side content adjustments that we can advise on but cannot execute.

Sending pattern violations of receiver expectations (sudden volume changes, audience compositions that look like spam-pattern, content distribution at times suggesting automated bulk sending) produce reputation incidents resolving only through customer operational changes. The incident response handles the event; sustained improvement requires customer commitment to operational practices that prevent recurrence.

Ready to insure against bad luck?

Telegram subscription takes 15 minutes. Onboarding completes within 48 hours (registering monitoring sources, calibrating seed-list testing). First SLA measurement period begins on next calendar month boundary. Cancel anytime, no commitment.

Subscribe on Telegram → Submit ticket

# Median Telegram response: 12 minutes during operating hours