Submit a ticket My Tickets
Welcome
Login  Sign up

How to Configure DNS Takeover Alerts

DNS Takeover Alerts in PowerDMARC enable you to continuously monitor your domains for misconfigured DNS records that attackers can exploit to hijack your subdomains even when DMARC is fully enforced. Leveraging the enhanced PowerAlerts system, you can configure alerts that automatically scan your domain infrastructure, detect dangling DNS records, and notify your team the moment a risk is identified.

This article provides a step-by-step guide to configuring DNS Takeover Alerts and explains each configuration option to help you set up effective, proactive monitoring for your domains.

Step 1: Select Monitoring Entities

  1. Navigate to PowerAlerts > Configuration >Add Alert Configuration.

  1. Click Add Alert Configuration.

  2. Under Monitoring Entities, select one or more domains, or a domain group to monitor multiple domains together.

  3. Once selected, click Next.

Monitoring entities define which domains the DNS Takeover alert will apply to. Only explicitly added (paid) domains can be selected as monitoring entities. Auto-discovered subdomains cannot be selected directly.

Step 2: Select Alert Type

  1. In the Alert Type section, choose DNS Takeover from the dropdown.

  2. Click Next to continue.

DNS Takeover alerts monitor your domain's DNS records for configurations that are vulnerable to subdomain takeover attacks such as nameserver delegations, CNAME records, SPF includes, and MX records that point to hostnames or domains that no longer exist.

Step 3: Configure Alert Conditions

This is the core step where you define which DNS takeover checks should trigger an alert.

Event Type

Event Type determines which class of DNS misconfiguration you want to monitor. Select one or more of the following:


Event Type

What It Monitors

Severity

Dangling NS

Nameserver records pointing to a nameserver that no longer exists. An attacker can register the expired nameserver and gain full DNS control of the subdomain.

Critical

SPF Subdomain Takeover

SPF records containing include:, redirect=, a:, mx:, or exists directives that reference a domain which has expired or is no longer registered.

Critical

Dangling CNAME

CNAME records pointing to a hostname that no longer resolves 

Critical

Dangling MX

MX records pointing to a mail server hostname that no longer resolves. An attacker could intercept email destined for your domain.

Critical

Dangling A/AAAA

A or AAAA records pointing to an IP address that may no longer be under your control and is potentially reclaimable by a third party.

Warning


Event Trigger

Event Trigger is automatically populated based on the Event Type selected and represents the specific detection signal that will generate the alert:

Event Type

Event Trigger

Dangling NS

Nameserver Record Unresolvable

SPF Subdomain Takeover

SPF Include Domain Unresolvable

Dangling CNAME

CNAME Target Unresolvable

Dangling MX

MX Record Unresolvable

Dangling A/AAAA

A/AAAA Record Unresolvable


Severity

Severity is system-assigned based on the risk level of each check type and is displayed as a read-only field. It cannot be manually adjusted for DNS Takeover alerts.

Adding Multiple Conditions

You can monitor more than one check type within the same alert configuration:

  • Click + Add New DNS Takeover Event to add individual conditions one at a time.

  • All five check types can be active within a single configuration.

Once all conditions are set, click Next.

Step 4: Configure Notification Groups

Notification Groups define who receives alert notifications and how they are delivered. You can either select an existing notification group or create a new one.

Option 1: Create a New Notification Group

If no suitable notification group exists, you can create one directly from the alert configuration flow.

  1. Click Create Notification Group.

  2. In the Create Notification Group panel, provide the following details:

  • Name: Enter a name to identify the notification group. This name will appear when selecting notification groups for alerts.

  • Emails: Add one or more email addresses to receive alert notifications. Multiple email addresses can be added as recipients.

  • Webhooks (Optional):Use Add Webhook to configure webhook-based notifications for third-party services such as Slack or Discord.

  1. Click Save to create the notification group.

Once created, the new notification group is available for selection and can be reused across multiple alert configurations.

Option 2: Select an Existing Notification Group

  1. In the Notification Groups section, click the dropdown.

  2. Select one or more existing notification groups from the list.

  3. Proceed to create the alert configuration.

Step 5: Create Alert Configuration

  1. Review the selected domains, alert type, conditions, and notification settings.

  2. Click Create Configuration to save the alert.


Your DNS Takeover Alert will now begin monitoring immediately. An initial scan runs as soon as the configuration is saved, followed by continuous scheduled scans.

How DNS Takeover Detection Works

Once a DNS Takeover alert configuration is active, PowerDMARC's detection engine runs the following process:

  • Scheduled scans: Re-run every 24 hours per monitored domain. An initial scan triggers immediately on configuration save; subsequent scans confirm new risks or resolution of existing findings.

  • Subdomain scope: The engine checks all subdomains known to the platform for the monitored domain, including subdomains observed across the platform's existing domain data. Only explicitly added domains can be configured as monitoring entities; auto-discovered subdomains are scanned automatically under their parent domain.

  • DNS validation: Each DNS query is retried exactly 3 times before a record is classified as unresolvable (NXDOMAIN). 

  • Reoccurrence: If a previously resolved finding reoccurs in a later scan, a new alert is created with a new First Triggered Date. The historical resolved finding is retained for audit and reporting purposes.

A finding is only created when a DNS object is confirmed as unresolvable (NXDOMAIN) after multiple validation attempts, to prevent false positives from transient DNS failures.

Viewing DNS Takeover Alerts

Once triggered, DNS Takeover alerts appear in PowerAlerts > Alert Logs under the DNS Takeover Alerts tab.

Each alert entry displays:

Column

Description

First Triggered Date

The date and time the issue was first detected.

Monitoring Entity

The domain or subdomain where the issue was found.

Event Type

The type of DNS misconfiguration detected (e.g. Dangling CNAME).

Severity

Critical, High, or Warning.

Status

In Alarm (active issue) or Resolved (issue no longer detected).

Remediation

A plain-language description of what to fix.

Remediation Guidance

Each DNS Takeover alert includes an inline remediation message explaining what was detected and what action to take:

Event Type

Remediation

Dangling NS

Your subdomain's nameserver record points to a server that no longer exists. Remove or update the NS record in your DNS provider to prevent an attacker from registering the nameserver and gaining full control of this subdomain.

SPF Subdomain Takeover

Your SPF record includes a domain that has expired or is no longer under your control. Remove the expired directive from your SPF record to prevent attackers from sending email that passes authentication on your behalf.

Dangling CNAME

Your subdomain's CNAME record points to a hostname that no longer resolves. Remove or update the CNAME record in your DNS provider to prevent an attacker from claiming that hostname and taking over this subdomain.

Dangling MX

Your domain's MX record points to a mail server hostname that no longer resolves. Remove or update the MX record in your DNS provider to prevent an attacker from intercepting or impersonating inbound email for this domain.

Dangling A/AAAA

Your subdomain's A or AAAA record points to an IP address that may no longer be under your control. Verify ownership of this IP with your hosting provider and update or remove the record if it is no longer assigned to you.

Alert Status

Status

Description

In Alarm

An active DNS takeover risk has been detected and has not yet been resolved.

Resolved

The previously detected issue is no longer present. The alert resolves only when all affected records for the same domain and event type are confirmed clean.


Disabling or Deleting a DNS Takeover Alert

From the Alert Configurations list, you can manage any DNS Takeover alert using the action controls on each row:

  • Edit (pencil icon) — Modify the conditions, monitoring entities, or notification group.

  • Toggle (power icon) — Enable or disable the configuration without deleting it. Disabling pauses monitoring and stops notifications for that configuration.

  • Delete (bin icon) — Permanently remove the configuration. Associated alert log entries are retained in Alert Logs.

For further assistance, visit support.powerdmarc.com or contact your PowerDMARC account manager.

P
PowerDMARC is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.