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:
- Email - Immediate alerts to qualifying users and the customer alert email.
- In-App Notifications - Appear in the notification bell in the dashboard header.
- Webhooks - HTTP POST to your configured endpoint (Standard plan and above).
- 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
| Column | Description |
|---|---|
| Type | Badge showing the channel - Email, Webhook, or Teams |
| Domain | The domain that triggered the alert |
| Changes | Number of DNS changes in this alert (e.g., "3 change(s)") |
| Sent At | When the alert was dispatched |
| Actions | View 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:
| Setting | Default | Description |
|---|---|---|
| Email Notifications | On | Receive email alerts for DNS changes |
| Critical Alerts Only | Off | Only receive high and critical severity notifications |
| Daily Digest | Off | Get 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
| When It's Sent | |
|---|---|
| DNS Change Alert | Immediately when drift is detected |
| DNS Recovery | When all drift for a domain is resolved |
| Monitoring Error | When a DNS check fails |
| Daily Digest | Once 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
- Go to Settings → Webhooks.
- Click Add Webhook.
- Configure:
| Field | Required | Description |
|---|---|---|
| Name | Yes | A friendly identifier (max 100 characters) |
| URL | Yes | Must be HTTPS. Max 2,048 characters. |
| Secret | No | HMAC-SHA256 signing key for verifying payloads |
| Send on Change | Yes (default: on) | Fire when DNS drift is detected |
| Send on Recovery | Yes (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
| Header | Description |
|---|---|
Content-Type | application/json |
X-Webhook-Event | Event type (e.g., dns.change) |
X-Webhook-Timestamp | ISO 8601 timestamp |
X-Webhook-Signature | sha256=<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
| Plan | Max Webhooks |
|---|---|
| Free | - |
| Standard | 3 |
| Professional | 10 |
| MSP | 40 |
Microsoft Teams Integration
Requires Professional or MSP plan.
Send rich Adaptive Card notifications directly to your Microsoft Teams channels.
Setting Up Teams Integration
- In Microsoft Teams, create an Incoming Webhook connector for your target channel.
- Copy the webhook URL.
- In DriftSensor, go to Settings → Teams Integration.
- Click Add Integration and configure:
| Field | Required | Description |
|---|---|---|
| Name | Yes | Friendly identifier (max 100 characters) |
| Webhook URL | Yes | The Teams/Office 365 incoming webhook URL |
| Channel Name | No | Display name for reference |
| Alert Types | Yes | Which events to receive: Drift, Recovery, Security, SSL, Domain Added, Domain Removed |
| Min Severity | Yes | Minimum 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.

