Features
Resources
Feature
DNS changes don't wait for you to check a dashboard. DNS Spy delivers alerts through the channels your team already uses — email, Slack, Discord, or PagerDuty — with full control over what triggers each one.
No credit card required · 7-day trial · Full Enterprise access
The default notification channel. Configure multiple email channels with different recipient lists for different teams or domains.
Push DNS alerts directly into your Slack workspace. Configure per-channel routing so record changes go to #dns-ops and security alerts go to #security.
Deliver DNS alerts to your Discord server via webhook. Same structured formatting and event filtering as other channels.
Route critical DNS events into your PagerDuty escalation policies. Severity, source, and custom details are included so your routing rules work correctly.
Not every alert needs to go everywhere. DNS record changes might belong in your #dns-ops Slack channel. Security Center state changes should hit PagerDuty for your security team. Domain offline events need to page whoever is on-call. WHOIS changes can go to a weekly email digest.
DNS Spy gives you full control. Create as many notification channels as you need. Each one gets its own set of enabled event types. The same event can trigger multiple channels — or just one. You decide the routing, DNS Spy handles the delivery.
Example Routing Configuration
Every DNS Spy feature generates events. You choose which events trigger which channels — per channel, with full granularity.
A DNS record value or TTL changed on any nameserver.
A DNS record was added that wasn't there before.
Authoritative nameservers for the domain changed.
Nameservers are returning different values for the same record.
Previously out-of-sync nameservers are now consistent.
A domain's nameservers came back online after being unreachable.
A domain's nameservers stopped responding.
SOA serial number or fields changed, indicating a zone update.
Domain registration or WHOIS data changed.
Zone transfer availability failed.
Zone transfer recovered after a failure.
Monitoring was disabled for a record.
New look-alike domains discovered or variant status changed.
A Security Center check transitioned from pass to fail or vice versa.
Notifications are built into every DNS Spy feature. Here's what generates the events your channels deliver.
Record changes, new records, nameserver sync, domain online/offline
Security check state changes (pass → fail, fail → pass)
New look-alike domains, status changes, DNS infrastructure changes
Registration data changes, registrar updates
Expiration alerts, security check state changes
Organize domains and manage alerts at the group level
No credit card required · 7-day trial · Full Enterprise access
DNS Spy supports four notification channels: email (all plans), Slack (Enterprise), Discord (Enterprise), and PagerDuty (Enterprise). You can configure multiple channels simultaneously and control exactly which event types each channel receives.
Yes. Each notification channel has its own set of enabled event types. For example, you might send all events to email, DNS record changes and Security Center alerts to Slack, and only domain-offline events to PagerDuty. This gives you full control over alert routing without noise.
There is no limit on the number of notification channels. You can set up multiple email channels with different recipient lists, multiple Slack channels for different teams, and dedicated PagerDuty integrations for critical vs. non-critical alerts.
DNS Spy supports 14 notification event types: DNS Records Changed, New Records Found, Nameserver Changed, Nameservers Out of Sync, Nameservers In Sync, Domain Online, Domain Offline, SOA Record Changed, WHOIS Updated, AXFR Failed, AXFR Working Again, Record Monitoring Disabled, Phishing Variants Detected, and Security Check State Change.
DNS Spy integrates with PagerDuty via Events API using your integration key. Alerts include structured metadata — domain name, event severity, source component, and custom details — so your PagerDuty routing rules and escalation policies work correctly. Critical events like domain-offline or Security Center state changes map naturally to PagerDuty's severity model.
Yes. When configuring a Slack notification channel, you specify both the Slack workspace token and the target channel. You can create multiple Slack channels — for example, #dns-alerts for record changes and #security for Security Center state changes.
Most notifications are sent individually per event to ensure timely delivery. The exception is Phishing Sentinel, which batches all discoveries and changes per domain per scan cycle into a single consolidated notification to avoid alert fatigue.
Email notifications are included on all paid plans. Slack, Discord, and PagerDuty integrations require the Enterprise plan. All channels are available during the 7-day free trial.
Email, Slack, Discord, PagerDuty — pick one or pick all four. Start your free trial and configure your first alert channel in minutes.
Start Free Trial
Features
Resources