How does SenderSignal detect blacklist listings?

Checks run immediately when you add an asset, on your plan schedule, and whenever you rescan. When a listing is newly detected, alerts can reach your team through the channels you configure.

Which blacklists does SenderSignal monitor?

SenderSignal monitors 44 or more blacklist vendors, including major DNSBL and URIBL feeds. The vendors available to you depend on your subscription plan.

Where do alerts get delivered?

Email, Slack, and HTTPS webhooks. Webhooks work well for PagerDuty, Microsoft Teams adapters, and custom automation. You can subscribe each channel to the event types that matter to your team.

Alerts

Rules & routing

Optional filters that decide which alerts reach which channels without turning off monitoring.

Rules vs channels (quick recap)

Channel = where notifications go (email list, Slack, webhook)
Rule = optional filter + routing logic on top

Flow: Event occurs → alert created → each active rule evaluated → matching channels notified (if channel also subscribes to that event type).

When you need rules

Route listed on production domains to PagerDuty, listings on dev domains to email only
Suppress noisy score_rise alerts for sandbox assets
Require minimum severity before Slack ping
Match asset tags (e.g. tag client-acme → dedicated webhook)

Small teams often skip rules and rely on channel event subscriptions alone.

Rule conditions

Rules can combine conditions such as:

Alert types: whitelist specific type codes
Severity: critical, warning, info
Asset tags: match monitor tags you assign to domains/IPs
Domain pattern: limit to suffix or substring (advanced)

Empty conditions typically mean “match all alerts of subscribed types” for that routing path.

Routing actions

A rule links to one or more channels. When the rule matches, those channels receive the notification (subject to their event type subscriptions).

Alert settings (org-level toggles)

Under Alerts → Settings, workspace admins enable or disable generation of entire alert families:

Blacklist listed / delisted
Score rise / drop with configurable delta thresholds
Postmaster reputation, compliance, and spam rate changes
Deliverability-specific signals (when available on your plan)

Disabling a family stops new alerts of that type: existing history remains.

Delivery logs

Each notification attempt is logged with channel name, timestamp, success/failure, and error message. Use logs to debug Slack URL typos, expired webhooks, or mailbox full errors.

Best practices

Start with one email channel + all critical events
Add Slack for real-time listed/delisted
Introduce rules when asset count grows beyond a single team inbox
Test with Send test on each channel after changes

← Alert channels · Blacklist events →