DriftSensor Docs

Alerts & Notifications

Configure how and when DriftSensor notifies you about DNS changes - email, webhooks, Microsoft Teams, and in-app notifications.

How Alerts Work

When DriftSensor detects DNS drift, it triggers notifications through multiple channels simultaneously:

  1. Email - Immediate alerts to qualifying users and the customer alert email.
  2. In-App Notifications - Appear in the notification bell in the dashboard header.
  3. Webhooks - HTTP POST to your configured endpoint (Standard plan and above).
  4. Microsoft Teams - Adaptive Card messages to your Teams channels (Professional and MSP plans).

Recovery notifications are sent when all drift for a domain is resolved.


Alerts Page

Navigate to Alerts in the sidebar to view all dispatched notifications.

Table Columns

ColumnDescription
TypeBadge showing the channel - Email, Webhook, or Teams
DomainThe domain that triggered the alert
ChangesNumber of DNS changes in this alert (e.g., "3 change(s)")
Sent AtWhen the alert was dispatched
ActionsView details

Filters

  • Type - Filter by Email, Webhook, or Teams.
  • Date Range - Set start and end dates to narrow results.

Alert Detail

Click the eye icon to view full alert details:

  • Subject (for email alerts)
  • Domain Info - Domain name and send timestamp
  • DNS Changes Detected - Each change shows the record type, expected vs. current value, and detection timestamp. Missing values are highlighted in red.

Email Notifications

User-Level Settings

Each user can configure their notification preferences in Settings → Notifications:

SettingDefaultDescription
Email NotificationsOnReceive email alerts for DNS changes
Critical Alerts OnlyOffOnly receive high and critical severity notifications
Daily DigestOffGet a daily summary instead of immediate emails

Customer Alert Email

Tenant admins can set a dedicated Notification Email Address in Settings (e.g., alerts@yourcompany.com). This email always receives alerts regardless of individual user preferences - useful for shared inboxes or ops teams.

Email Types

EmailWhen It's Sent
DNS Change AlertImmediately when drift is detected
DNS RecoveryWhen all drift for a domain is resolved
Monitoring ErrorWhen a DNS check fails
Daily DigestOnce daily, summarizing all changes grouped by domain

In-App Notifications

The notification bell in the dashboard header shows a red badge with your unread count. Click it to see recent notifications.

Each notification shows:

  • Type Icon - DNS Change (blue), Monitoring Error (amber), Security (red), or System (gray)
  • Title and Message
  • Priority Badge - Low, Medium, High, or Critical
  • Timestamp

Hover to mark as read or delete. Click a notification to navigate directly to the affected domain.

Use Mark All Read to clear your unread count, or visit the full notifications page via View All Notifications.

Notifications poll every 30 seconds so you'll see new alerts quickly.


Webhooks

Requires Standard plan or higher.

Webhooks send HTTP POST requests to your endpoint when DNS changes are detected.

Setting Up a Webhook

  1. Go to Settings → Webhooks.
  2. Click Add Webhook.
  3. Configure:
FieldRequiredDescription
NameYesA friendly identifier (max 100 characters)
URLYesMust be HTTPS. Max 2,048 characters.
SecretNoHMAC-SHA256 signing key for verifying payloads
Send on ChangeYes (default: on)Fire when DNS drift is detected
Send on RecoveryYes (default: on)Fire when drift is resolved

Webhook Payload

{
  "event": "dns.change",
  "timestamp": "2026-02-24T12:00:00Z",
  "data": {
    "domain": "example.com",
    "domain_id": "uuid",
    "changes": [
      {
        "type": "A",
        "old": "1.2.3.4",
        "new": "5.6.7.8",
        "detected_at": "2026-02-24T12:00:00Z"
      }
    ]
  }
}

Event types: dns.change, dns.recovery, test.

Webhook Headers

HeaderDescription
Content-Typeapplication/json
X-Webhook-EventEvent type (e.g., dns.change)
X-Webhook-TimestampISO 8601 timestamp
X-Webhook-Signaturesha256=<hmac> (only if a secret is configured)

Verifying Webhook Signatures

If you set a secret, DriftSensor signs the payload using HMAC-SHA256. Verify by computing HMAC-SHA256(secret, request_body) and comparing it to the signature in the X-Webhook-Signature header.

Testing

Click Test on any webhook to send a test payload. You'll see the HTTP status code, response time, and any errors.

Auto-Disable

If a webhook fails 10 consecutive times, it's automatically disabled to prevent repeated failures. The failure count resets on any successful delivery.

Plan Limits

PlanMax Webhooks
Free-
Standard3
Professional10
MSP40

Microsoft Teams Integration

Requires Professional or MSP plan.

Send rich Adaptive Card notifications directly to your Microsoft Teams channels.

Setting Up Teams Integration

  1. In Microsoft Teams, create an Incoming Webhook connector for your target channel.
  2. Copy the webhook URL.
  3. In DriftSensor, go to Settings → Teams Integration.
  4. Click Add Integration and configure:
FieldRequiredDescription
NameYesFriendly identifier (max 100 characters)
Webhook URLYesThe Teams/Office 365 incoming webhook URL
Channel NameNoDisplay name for reference
Alert TypesYesWhich events to receive: Drift, Recovery, Security, SSL, Domain Added, Domain Removed
Min SeverityYesMinimum severity threshold: Info, Warning, or Critical

Notification Cards

DriftSensor sends visually rich Adaptive Cards to Teams:

  • DNS Drift Alert - Red/amber card showing domain, severity, number of changes, and a table of affected records with expected vs. actual values. Includes a button to open DriftSensor.
  • Recovery Alert - Green card confirming drift has been resolved.
  • Security Alert - Shows identified security issues with severity levels.
  • SSL Expiry Alert - Warns about upcoming SSL certificate expiration.

Testing

Click Test to send a test card to your channel. A green confirmation card will appear in Teams with the message "Your Microsoft Teams integration is working correctly!"

Limits

Maximum 10 Teams integrations per customer. Auto-disables after 10 consecutive delivery failures.