Most senders running serious volume in 2026 are paying for some combination of GlockApps, MXToolbox, dmarcian, and Validity Everest, with separate logins, separate billing, and separate alerts that arrive on different channels with different reliability. We bundle the whole stack into one dashboard: DMARC report parsing, Google Postmaster Tools coordination, Microsoft SNDS pulls, Sender Score, blacklist monitoring across 50+ sources, weekly inbox placement testing, all surfaced together with humans on our side reviewing alerts before they reach you. From €49 per domain per month. Same engineering team that has been operating email infrastructure since 2008.
In short
The dashboard pulls from several independent sources — seed accounts, the mailbox providers' own feeds, and blacklist lookups — then correlates and scores them so a single alert tells you what changed and why. You read one signal instead of reconciling six tools by hand. The diagram traces that flow.
A reputation change does not just colour a chart — it fires a contextual alert to your webhook, naming the provider, the direction of the move and the current inbox-placement rate:
POST https://your-app.example/webhooks/osd (deliverability alert)
{
"event": "reputation.drop",
"domain": "mail.yourdomain.com",
"provider": "google_postmaster",
"from": "high",
"to": "medium",
"blacklists": [],
"inbox_placement": 0.91,
"observed_at": "2026-06-09T08:14:22Z"
} The deliverability monitoring market in 2026 is fragmented in a specific way. Each tool covers one piece. GlockApps is excellent at inbox placement testing through seed lists, weak on ongoing reputation tracking. MXToolbox is excellent at blacklist monitoring and DNS diagnostics, weak on placement testing. dmarcian is excellent at DMARC report parsing, scoped only to DMARC. Validity Everest is the closest to a unified product but pricing starts at $525 per month for the Plus tier and most customers under enterprise scale never touch it. The practical result: most teams running serious sending volume end up subscribing to two or three tools and stitching the alerts together manually.
This product is the stitched version, sold as one product, on EU infrastructure. The same dashboard surfaces DMARC aggregate reports parsed from your rua endpoint, Google Postmaster Tools data pulled via the API for every domain you monitor, Microsoft SNDS reputation status for every IP, Sender Score values updated daily, blacklist status across 50+ sources (Spamhaus, SORBS, Barracuda, UCEPROTECT, the major regional lists), and weekly inbox placement testing through a seed list of around 200 mailboxes across the major receivers. When something changes, the alert lands in your email and Slack with context. Instead of a bare "Spamhaus listed your IP", you get "Spamhaus DBL listed example.com today, the typical cause given recent volume patterns is X, suggested first action is Y, escalation contact is Z".
Honest moment about scale. If you are sending under 50,000 emails per month total, you do not need a paid monitoring product. Google Postmaster Tools, Microsoft SNDS, and Sender Score together are free, the dashboards are usable enough, and the alert volume is low enough that manual checking once a week is fine. We will tell you that on the discovery call. Roughly 20 percent of inquiries come from senders at this scale; we redirect them to free tools and they get a thank-you email instead of an invoice. The customers we want are sending 100,000+ per month, where the alert volume is high enough that manual triage breaks down and engineering time spent on monitoring becomes a real cost.
The unique angle is the engineer-level alerting. Most monitoring tools fire raw alerts the moment a metric crosses threshold: "your spam rate exceeded 0.1 percent" or "blacklist X listed your IP". Useful but noisy. Real-world engineering teams get fatigued by alert volume, miss the important ones, and develop alert blindness within months. Our approach: alerts pass through a human review layer before they reach you. A deliverability engineer on our side checks each significant alert, adds context (likely cause, recommended action, urgency level), suppresses obvious noise (Barracuda relisting cycles, transient SNDS yellow that resolves within hours), and only forwards alerts that genuinely warrant attention. The signal-to-noise ratio improves substantially, which is the difference between a monitoring product you actively use and one you eventually mute.
And worth saying upfront: this product is included free for customers of our /smtp-relay, /email-sending-servers, /cold-email-infrastructure, and /managed-dmarc products. The standalone product on this page is for external customers who do not have us operating their sending infrastructure. The cross-product bundling exists because monitoring is the natural complement to sending; charging customers for the same dashboard twice would be silly. If you are evaluating both this and one of the sending products, the bundled pricing makes the decision simpler: pick the sending product, monitoring comes with it.
One last clarification on what this product is not. It is not a sending platform. We do not send email through this product, do not provide SMTP credentials for outbound use, do not route mail of any kind. The product observes your sending and tells you what is happening; it does not produce any sending of its own. It is also not a list verification or list cleaning service. The most common deliverability issues we observe come from list quality (high bounce rate, spam traps, complaint-prone segments), and our dashboard surfaces those issues clearly, but fixing the underlying list quality is your work. We refer customers needing list verification to ZeroBounce, Bouncer, or Prospeo; we do not white-label those services and we do not pretend to. We are deliberately scoped to monitoring and we leave adjacent product categories to vendors who specialize in them.
It tracks six things at once: seed-inbox placement, Google Postmaster Tools, Microsoft SNDS, blacklist status, sender reputation and authentication results. Below are the components our dashboard pulls together. Each is a real product or data source in its own right; the bundling is what makes the workflow tolerable. You do not log into six things and reconcile their alerts manually.
Aggregate reports from receivers (Google, Microsoft, Yahoo, and a long tail) flow into our parsing pipeline through the rua endpoint configured on your DMARC record. We parse the XML, deduplicate sources, identify legitimate senders versus spoofing attempts, and surface the data in a dashboard view that does not require reading XML. Reports are retained for 13 months for trend analysis. Comparable to dmarcian Basic at $24/mo, included here as one component.
Daily pulls from Google Postmaster Tools API for every domain you monitor. Domain reputation, IP reputation, spam rate, authentication breakdown (SPF pass/fail, DKIM pass/fail, DMARC pass/fail), encryption metrics. The API requires domain ownership verification which we walk through during onboarding. Once configured, the pulls happen automatically and the data joins the unified dashboard. Postmaster Tools is free directly from Google but the API integration plus historical retention is what we add.
Smart Network Data Services data pulled daily for every IP you monitor. Green / Yellow / Red status, complaint rate (CFL data when available), traffic volume, trap hit count. SNDS is free directly from Microsoft but the access workflow is awkward (manual approval, JNet keys, occasional auth failures) and the data is XML. We handle the access plumbing and surface the data alongside Postmaster Tools and the rest of the bundle.
Validity Sender Score values pulled daily for every IP. Plus aggregate reputation indicators from secondary sources: Talos reputation, Cisco Sender Base, IBM X-Force categories, Cloudmark scoring where available. None of these is authoritative on its own, but the aggregate view catches reputation drift faster than any single source. Sender Score lookup is free directly from Validity; the aggregation across sources is what we add.
Daily checks against the major blacklists: Spamhaus DBL, ZEN, SBL, XBL, PBL; SORBS aggregate; Barracuda BRBL; UCEPROTECT levels 1, 2, and 3; Invaluement; the major regional lists (Outsight, KISA, NIXSpam, multi-RBL aggregates). Total coverage above 50 sources. Listings get an alert immediately; delistings get a status update. We do not use blacklist monitoring as a fear-driven feature: most listings have minor real-world impact, and we communicate severity honestly so customers do not panic over a UCEPROTECT 3 listing that affects almost no actual receivers.
Seed list of around 200 mailboxes across the major receivers (Gmail, Outlook/Microsoft 365, Yahoo, AOL, Apple, Free.fr, GMX, Strato, ProtonMail, T-Online, web.de, Mail.ru, Yandex, the long tail of regional providers). One placement test per week per monitored domain by default, more frequent on Pro and Enterprise tiers. Results show inbox/spam/missing breakdown per receiver and per domain, with trend lines showing degradation patterns over time. Comparable to GlockApps Essential at $59/mo for the inbox placement testing alone.
Most monitoring products fire raw threshold alerts. Our alerts pass through a human review layer first. The difference matters because alert fatigue is the leading reason teams stop using monitoring products within 6 months of buying them. Below is what the alert pipeline actually looks like.
A metric crosses a configured threshold: spam rate over 0.1 percent for 3 consecutive days, blacklist listing on a major source, Postmaster Tools domain reputation dropping from High to Medium, SNDS IP turning Yellow with sustained traffic. The system flags the event automatically.
The flagged event gets enriched with context: traffic volume during the period, recent campaign sends if known, similar patterns from your own historical data, similar patterns we have seen across other customers in the same vertical. This enrichment is partly automated and partly a deliverability engineer adding judgment. The output is not "spam rate exceeded threshold" but "spam rate exceeded threshold during your Tuesday campaign send to 45,000 recipients, comparable to the pattern we saw three weeks ago which resolved within 5 days, recommended action is to check the list segment used for that campaign".
A deliverability engineer assigns severity: critical (act today), important (review this week), informational (note for the trend, no action). Most monitoring products treat all threshold breaches as the same severity, which is the source of alert fatigue. We classify based on real-world impact, which means a UCEPROTECT 3 listing gets informational while a Spamhaus DBL listing gets critical, even though both are "blacklist listings".
Some alerts are noise that fires regularly: Barracuda relisting cycles that resolve within 24 hours, transient SNDS yellow that returns to green, Sender Score variations within the normal noise range, secondary blacklists with minimal real-world impact. We suppress those before they reach you. Customers can override the suppression if they want maximum alert volume, but the default is filtered.
Alerts that pass through the previous steps land in your configured channels: email, Slack, PagerDuty integration for Pro and Enterprise tiers, custom webhook for any tier. The format includes the event, the context, the severity, the recommended action, and a link to the dashboard for deeper investigation. Most alerts get resolved in under 15 minutes once they reach you because the context is included rather than requiring you to dig for it.
Below is the comparison at typical mid-market use (around 10 domains, monitoring across the full deliverability stack). Pricing reflects published list rates as of early 2026.
| Attribute | OS Domains | GlockApps | MXToolbox | dmarcian | Validity Everest |
|---|---|---|---|---|---|
| Monthly price at 10 domains | €149 (Multi-Domain Pack) | $59 (placement only) + $24+ for DMARC | $129 (Delivery Center, 5-domain limit) | $24 (DMARC only) | $525 (Everest Plus) |
| EU sovereign, no US parent | Yes, Austrian GmbH | No, US company | No, US company | No, US company | No, US company |
| DMARC report parsing | Yes, included | Add-on | Yes, included | Yes, core product | Yes, included |
| Inbox placement testing | Yes, weekly seed tests | Yes, core product | Limited | No | Yes |
| Postmaster Tools + SNDS bundled | Yes, daily pulls | Postmaster only | Limited | No | Yes |
| Blacklist monitoring (major sources) | 50+ sources | Limited | 100+ sources | No | 50+ sources |
| Engineer-reviewed alerts | Yes, default | No | No | No | Limited (Pro tier) |
| Operating since | 2008 (monitoring product since 2018) | 2014 | 2004 | 2014 | 2018 (consolidated brand) |
Most monitoring products throw all the data at you at once. We organize it by cadence so the dashboard matches the pace of real work. Below is what each cadence looks like.
The daily view shows what changed in the last 24 hours: critical alerts (blacklist listings on major sources, Postmaster reputation drops, SNDS turning red), authentication failures, spike-rate anomalies. Roughly 80 percent of customer days show an empty daily view, which is the correct outcome. The other 20 percent show one or two items that warrant a 5-minute look. This view is designed to be checked once per business day in under 5 minutes.
The weekly view aggregates the daily data into trend lines: spam rate over time, complaint rate over time, reputation movement across major receivers, blacklist exposure changes. The weekly inbox placement test results land here with the receiver-by-receiver breakdown. This view is designed for a 15 to 20 minute weekly review, typically Mondays, where the team identifies trends that the daily checks would miss.
The monthly view aggregates everything into strategic indicators: deliverability health score across the full stack, comparison against industry benchmarks for your vertical, list health metrics, authentication compliance trends. This view is designed for the monthly business review where deliverability shows up as a metric in the broader operations report. We auto-generate a monthly summary PDF that fits into existing reporting cadences.
Outside the daily/weekly/monthly cadence, real-time alerts fire for genuine emergencies: Spamhaus DBL listings, Postmaster reputation drops to Bad, sustained high spam rate during an active campaign. These hit your email or Slack within 60 seconds of detection. The volume is low (typically 0 to 3 events per month for healthy senders) because the engineer-review layer suppresses noise. Customers do not get woken up by Barracuda relisting cycles.
Plans start at €49/mo (Single Domain) and €149/mo (Multi-Domain Pack), with Agency and Enterprise tiers above. Pricing is per-organization, not per-user. Domain count is the main scaling axis because most monitoring work scales with domains, not seats. Annual prepay saves 15%. Customers of /smtp-relay, /email-sending-servers, /cold-email-infrastructure, and /managed-dmarc get this product included free at the equivalent tier.
For solo founders, single-product SaaS, small operations.
Live in 60 to 90 minutes after signup
Ideal for
Solo founders running outbound, single-product SaaS at Series A, in-house teams managing one main brand domain.
For in-house teams managing multiple brand domains.
Live in 60 to 90 minutes after signup
Ideal for
In-house outbound at Series B-C, marketing teams running newsletters across multiple brands, small SaaS multi-brand operations.
For agencies managing client portfolios with multi-tenant separation.
Live in 24 hours after signup (brief setup call)
Ideal for
Email marketing agencies, deliverability consultants, MSPs managing 10 to 50 client domains.
For large operations, regulated industries, signed SLAs.
Onboarding 5 to 10 business days
Ideal for
Large SaaS, financial services, healthcare, public sector, anyone past 50 domains or requiring formal contractual structure.
Customers of /smtp-relay, /email-sending-servers, /cold-email-infrastructure, and /managed-dmarc receive this product free at the equivalent tier matching their account size. The standalone product on this page is for external customers running their own infrastructure. Annual prepay saves 15%. Agency tier includes white-labeled reporting at no extra charge; the report shows your branding rather than ours when shared with end clients.
Two reasons. First: the bundling is the product. GlockApps does not pull Postmaster Tools or SNDS in any meaningful way; dmarcian does not do inbox placement testing. To get our coverage with those two tools you would also need MXToolbox Delivery Center ($129) and dmarcian for DMARC ($24), plus you reconcile alerts across three dashboards. Total: ~$212 plus operational overhead. Second: the engineer-review layer. The two-tool stack fires raw alerts that your team has to triage. Our alerts are pre-filtered and contextualized. Whether the difference matters depends on how much your team values reduced operational overhead; for sub-100K/mo senders it usually does not, for 500K+/mo senders it usually does.
Validity Everest Plus is the closest analogue to our product in terms of coverage. The differences: pricing (we are roughly 70 percent less expensive at equivalent tier), jurisdiction (they are US-based, Cloud Act applies; we are Austrian GmbH, EU sub-processors only), engineer-review layer (their alerts are mostly automated; ours have human review), focus (Everest covers more brand-protection and competitive intelligence features; we focus tightly on technical deliverability). For senders who need brand-protection features (deliverability of competitors, share-of-inbox metrics for marketing teams), Validity is the better choice and we will tell you that. For senders who want technical deliverability monitoring without the brand-marketing overlay, we are the better fit at substantially lower price.
A deliverability engineer on our side reviews every alert above the informational severity tier before it gets forwarded to you. The review takes 5 to 15 minutes per alert depending on complexity. The engineer adds context (likely cause, similar past patterns, recommended action), assigns final severity, and decides whether to forward, suppress, or batch with other related alerts. This means alerts arrive with a slight delay (typically 5 to 30 minutes after detection rather than instantaneously), but the alerts that arrive are pre-triaged. For genuine emergencies, automated bypass routes exist: Spamhaus DBL listings, sustained Postmaster Bad reputation, and a few similar patterns fire instantly without the review delay.
You add our rua endpoint to your DMARC record. Two patterns work. Pattern A: change the rua= value to point at our endpoint exclusively (rua=mailto:[email protected]). Pattern B: keep your existing rua endpoints and add ours as additional (rua=mailto:[email protected],mailto:[email protected]). Most customers use Pattern B because it preserves whatever they had before plus adds our parsing. The DNS change is a single record edit; we walk through the syntax during onboarding. From the moment the record propagates (typically 1 to 4 hours), reports start flowing into our parser and surfacing in your dashboard.
DMARC aggregate reports contain IP addresses of senders, which can be PII under GDPR depending on context. Our processing infrastructure runs on EU sub-processors only (matches our broader EU sovereign positioning), we sign a standard DPA with you before onboarding, reports are retained for 13 months for trend analysis and then deleted, customers can request earlier deletion at any time. For customers with stricter requirements (financial services, healthcare, public sector), we offer custom DPA terms with shortened retention and additional confidentiality. The DMARC reports themselves are not personal data of your customers; they are sender data of services attempting to deliver to your customers.
Approximately, with caveats. Seed-based placement testing has known limitations: the seed addresses do not have organic engagement history, the receiver filters treat them slightly differently than real recipients, and the results understate your real placement by 5 to 15 percent typically. We are honest about this in the dashboard; the placement number shown is labeled as "seed-based estimate" not "real placement". For real placement, the gold standard is Google Postmaster Tools data on actual recipients (which we also surface), and the seed-based testing is useful primarily for trend detection (changes over time) rather than absolute placement numbers. Customers who want exact real placement either use Postmaster Tools directly or implement subscriber-side seed lists with their actual customers, which is a different workflow.
SNDS access requires Microsoft to approve your IP and grant a JNet key. The approval is usually fast (1 to 3 business days) but the workflow is awkward. We handle the access plumbing: you provide the IPs you want monitored, we coordinate the SNDS request through our existing Microsoft relationship which usually accelerates approval, we maintain the JNet keys and refresh them when Microsoft rotates. The data flows into your dashboard automatically once access is granted. For customers whose IPs Microsoft refuses to grant SNDS access (rare but happens for IPs with sustained Red status), we work around it with secondary reputation sources, but coverage is degraded versus customers with full SNDS access.
Yes, that is exactly the standalone use case. Most monitoring product customers run their sending infrastructure on someone else (SendGrid, Mailgun, AWS SES, their own PowerMTA on Hetzner, whatever). The monitoring works the same way regardless of what is producing the email. You configure DMARC, Postmaster Tools, and SNDS to point at our endpoints; you pay the subscription; alerts arrive. We do not require you to migrate sending to use the monitoring. The cross-product bundling exists because customers who use both get the monitoring free; standalone customers get the same product for the standalone price.
Critical alerts (Spamhaus DBL, sustained Postmaster Bad, real-time spam rate spikes during active campaigns) fire to your configured channels at 3 AM if they happen at 3 AM. We do not buffer critical alerts to business hours. For non-critical alerts (UCEPROTECT 3 listings, transient SNDS yellow), the alert pipeline batches them to business-hours delivery. Pro and Enterprise tiers include PagerDuty integration that respects your on-call schedule and escalates appropriately. Single Domain and Multi-Domain tiers send to email and Slack with whatever notification preferences your team has configured for those channels. For genuine 24/7 incident support (engineer on the phone within 1 hour at any time), Enterprise tier is the right fit.
Month-to-month for Single Domain, Multi-Domain, and Agency tiers; cancel any time from the dashboard with one click. Annual prepay (15% discount) refunds unused months at the standard monthly rate, so the effective cost lands at the same place but you get the unused balance back. Enterprise tier has a signed annual contract with documented service credits for SLA breaches; cancellation terms are negotiated as part of the contract. We do not run retention games, do not require upgraded tiers to access cancellation, do not charge early termination fees. The dashboard data is exportable via API on every tier; canceling does not lock you out of your historical data during the cancellation period.
For most customers the alert volume is low enough that human review is genuinely scalable: typical customer at Multi-Domain Pack tier sees 5 to 30 alerts per month after suppression, of which 0 to 3 are critical. The review layer handles that easily. For high-volume customers (large agencies running 200+ domains, enterprise senders with significant blacklist exposure), we tier the review: critical and important alerts get human review every time, informational alerts get sample-reviewed and the suppression rules tighten based on patterns we observe. At very high volumes (1000+ alerts per month sustained), Enterprise tier with a dedicated deliverability engineer is the appropriate fit because the workload genuinely requires assigned attention rather than shared review.
Three things during onboarding. First: the domains you want monitored (and the IPs associated with each domain for SNDS pulls). Second: DNS record changes for DMARC reporting (point rua= at our endpoint), which takes one DNS edit per domain. Third: alert delivery preferences (email addresses, Slack channels, PagerDuty integration if applicable). Onboarding for Single Domain and Multi-Domain tiers is fully self-service through the dashboard; you complete the configuration and monitoring starts within 60 to 90 minutes. Agency tier includes a brief setup call (15 to 20 minutes) to configure multi-tenant isolation properly. Enterprise tier is a longer onboarding (5 to 10 business days) because it includes custom alerting rules, signed SLA terms, and possibly custom integrations.
We do not offer them, deliberately. Validity Everest and a few other enterprise tools include features for tracking competitor deliverability, share-of-inbox, and similar competitive intelligence views. The features exist because marketing teams want them, and they are technically interesting. We do not offer them because the data sources required (third-party seed networks reporting cross-customer placement, panel data on consumer email behavior, methodology that assumes you can reasonably extrapolate from sampling) make us uncomfortable from a privacy standpoint. Other vendors can serve that need; we focus on monitoring your own sending without claiming to know what your competitors are doing.
Self-host: no. The dashboard and alert pipeline run on our infrastructure; we do not offer an on-premise version because the operational complexity of supporting customer-side deployments is much higher than the revenue justifies. Import to your own tools: yes, every tier includes API access for exporting current and historical data into your existing observability stack. Common patterns: webhook delivery to PagerDuty or Opsgenie for paging, JSON export to Datadog or Splunk for ingest, scheduled CSV export to BigQuery or Snowflake for data warehouse analytics. The API documentation is available without signing up if you want to evaluate before subscribing.
The default flow has a 5 to 30 minute review delay before alerts forward, which is the right balance for most customers. For genuine emergencies (Spamhaus DBL listings, sustained Postmaster Bad reputation, real-time spam rate spikes during active campaigns), automated bypass routes fire instantly without the review delay. Customers can configure additional bypass conditions if they need certain alert types to skip review entirely; the trade-off is that bypassed alerts come without the contextual enrichment, which usually means more alerts to triage on your side. Most customers leave the defaults in place because the latency cost is low and the alert quality improvement is high.
No. The product is scoped to email reputation specifically. Adjacent reputation signals (social media abuse mentions, Reddit threads complaining about your sending, public spam reports) are interesting but they fall outside email infrastructure work. Customers concerned about broader reputation monitoring usually pair us with a brand-monitoring service (Mention, Brand24, or similar) and the two products serve complementary needs. We considered adding broader reputation features at one point and decided the scope creep would dilute the focus on technical email deliverability, which is the work we do well.
Major receiver events get tracked and surfaced in the dashboard with context. During the Gmail/Yahoo bulk sender enforcement rollout in February 2024, our alerts proactively flagged customers approaching the new thresholds (5,000+ daily sends to Gmail, complaint rate above 0.3 percent) before the enforcement kicked in. Similar pattern during Microsoft outbound IP changes. The dashboard does not replace your need to read the receiver-side announcements, but it does identify which of your sending patterns intersect with the announced changes and which need attention. We document major receiver events in a public changelog accessible from the dashboard, retained as historical context for trend analysis.
Enterprise tier is custom-quoted based on domain count, IP count, alert volume, and contractual requirements. Typical pricing: 100 to 200 domains lands around €800 to €1,500 per month; 200 to 500 domains lands around €1,500 to €3,500 per month; 500+ domains is genuinely custom because the workload involves dedicated engineering attention rather than shared review. Enterprise customers often bundle this product with /managed-dmarc and one of the sending infrastructure products into a single contract; the bundled pricing is typically 20 to 30 percent below standalone pricing for each component because the operational coordination is shared.
Currently English only for alert text and dashboard. Customer support is available in English, Spanish, and German. The alert content (event description, suggested action, severity reasoning) is generated by deliverability engineers writing in English, and translating it would either require professional translation per alert (expensive and slow) or auto-translation that introduces errors in technical content. We considered Spanish localization given customer demand from LATAM, and decided to defer until we have enough Spanish-speaking customers to justify a dedicated reviewer. If Spanish or another language is a strict requirement for your team, the discovery call covers the workaround options, which usually involve your team handling translation on receipt.
The dashboard and alerting layer get incremental improvements continuously; new blacklist sources get added as they emerge, new receiver-side data sources get integrated when they become available, the alert review heuristics evolve based on patterns we observe across the customer base. We do not run major redesigns that require customer re-onboarding; the operational discipline of email infrastructure rewards stability over feature velocity. New customer-facing features (new dashboard views, new integrations, custom alerting rules) ship roughly every 4 to 6 weeks and announce in the changelog. Customers can vote on feature priorities through a feedback portal, and the votes inform the roadmap without dictating it. The pace is deliberate; we are not trying to look like a SaaS competing for hype, we are trying to be the boring reliable product the email infrastructure category needs.
Single Domain, Multi-Domain Pack, and Agency Pack all subscribe through the standard signup flow: configure domains, point DMARC, choose alert channels, monitoring runs within 60 to 90 minutes. Enterprise tier requires a discovery call because the custom alerting and SLA terms benefit from a planning conversation. The discovery call is no charge regardless of whether the engagement closes.