Accept an expected finding to keep the default attention list focused. Acceptance records your review; it does not fix the domain or stop future scans.

Accept an expected result

1. Open PD Modules → Domain Radar → Needs attention.
2. Review the domain, finding, severity, detail and checked time.
3. Confirm why the condition is expected before choosing Accept.
4. Check that it leaves the default unaccepted list.

For example, a customer may deliberately use external nameservers. Accepting that note is different from changing the DNS service or claiming that the delegation matches your own.

Bring it back to attention

Choose Show accepted and locate the finding, then use Un-accept. This returns it to the attention list without changing the registry or platform domain settings. Severity filters still apply, so review them when looking for a missing row.

Understand later changes

A changed condition can clear acceptance, such as a severity change or changed nameserver details. A changing day count alone is deliberately treated differently for expiry-related findings. Do not assume that every small wording update becomes a new digest item.

The list shows open findings, optionally including accepted ones; it is not a full resolved-history browser. Its row limit can also differ from the summary counts. A finding that vanishes may have been resolved by the latest rule output, accepted or hidden by filtering.

Before treating disappearance as proof of a real-world fix, review lookup success and the actual domain state. An unsuccessful lookup can replace earlier open problems with Could not be checked, so check the evidence rather than relying only on an empty list.

See the PD Domain Radar Blesta guide for related tasks, or explore PD Domain Radar.