Scheduled jobs

Slack delivery

Connect a Slack incoming webhook so scheduled scan results post to your channel.

Send DNSSEC scan summaries to Slack when a scheduled scan completes or fails. dnsec uses a Slack incoming webhook — you choose the channel when you create the webhook in Slack.

Before you start

  • A Slack workspace where you can create or manage apps
  • Access to dashboard Schedule in dnsec
  • A channel where scan alerts should appear (for example #security or #dns-alerts)

1. Create a Slack app

  1. Open Slack API — Your Apps and sign in to your workspace.
  2. Click Create New App.
  3. Choose From scratch, name the app (for example dnsec), and select the workspace that should receive alerts.

2. Enable incoming webhooks

  1. In the left sidebar of your app settings, open Features → Incoming Webhooks.
  2. Turn Activate Incoming Webhooks On.

3. Create a webhook URL

  1. On the same Incoming Webhooks page, click Add New Webhook to Workspace.
  2. Select the channel where dnsec should post (for example #security-alerts).
  3. Click Allow.
  4. Copy the Webhook URL — it starts with https://hooks.slack.com/services/…

Keep this URL secret. Anyone with the URL can post messages to that channel.

4. Connect dnsec

  1. In dnsec, go to Dashboard → Schedule.
  2. Scroll to Notification settings → Delivery.
  3. In the Slack card, turn the toggle on.
  4. Paste the webhook URL into Incoming webhook URL.
  5. Click Save Slack delivery.
  6. Click Test connection to confirm a test message arrives in Slack.

What gets posted

When a scheduled scan finishes, dnsec posts a summary with:

  • Grade, score, risk, and DNSSEC status
  • Chain of trust, site lookalikes, and resolver consistency signals
  • A link to the full report in dnsec

Manual scans from the dashboard (without a schedule) do not use this delivery path. Use Run now on a schedule row or wait for the recurring schedule to fire.

Troubleshooting

IssueWhat to try
No messages after a scanConfirm Slack is enabled, webhook saved, and Send report is on under Alerting.
Test works but scans do not notifyThe job must be linked to a schedule (scheduled_scan_id). Use Run now or a cron-driven schedule, not a one-off dashboard lookup.
invalid_auth or 404 from SlackRecreate the webhook in Slack and paste the new URL in dnsec.
Wrong channelIncoming webhooks are tied to one channel. Create a new webhook for a different channel.

Previous

Getting started

Next

Chain of trust

On this page