Introducing DKIM monitoring

Today, we’re launching a new feature called DKIM monitoring, which adds observability capabilities to the dashboard to monitor DKIM records.
DKIM (DomainKeys Identified Mail) is a cryptographic method for email authentication, playing an essential role in electronic mail.
It is one of the cornerstones on which DMARC is based and it’s therefore important to keep it monitored, ensuring that your domain’s DNS configuration properly includes the DKIM verification records.
Until now, it was hard to obtain this kind of visibility.
The new DMARCwise DKIM monitoring feature solves this: it helps you monitor DKIM by continuously scanning and analyzing your domain’s DKIM records. It does so by extracting the DKIM selectors from the DMARC reports of your domain and then fetching the corresponding DNS records.
For example, if your domain is example.com and you use a selector named selector1, DMARCwise helps you keep track of the fact that you’re using this selector and that the DNS record at selector1._domainkey.example.com must be present and valid until you use the selector.
A DNS record is missing? Some records are unused?DMARCwise lets you easily spot these issues.
To try out the new DKIM monitoring feature, head over to the dashboard, choose a domain and switch to the new DKIM tab.
You’ll see two tables:
- Active selectors shows DKIM selectors that were seen in DMARC reports in the last 30 days or are still present in the DNS zone configuration of the domain.
- Inactive selectors shows the rest of the DKIM selectors, i.e. those that haven’t been seen in DMARC reports recently (and therefore likely not used to sign email messages recently) and are not longer present in the DNS zone.
Selectors in each table are grouped by domain name, making it easy to find selectors associated with a specific subdomain.
Note that the DKIM monitoring feature is being introduced in December 2025, so the system won’t be able to tell you if a DNS record existed before that date.
To learn more about the new DKIM monitoring feature and how to interpret the data, visit our dedicated documentation page.
