Site Sentinel emails new serious findings rather than every advisory. Check the scan and finding lifecycle as well as the destination address when an expected notification is missing.

Set the recipients

1. Open PD Modules → Site Sentinel → Settings.
2. Set Who to alert about serious findings to the intended comma-separated addresses.
3. Save and review the platform’s ordinary mail delivery configuration.
4. Check the next relevant scan, finding and Activity evidence.

Valid configured addresses are used. If no valid recipient remains, the module tries the platform’s system sender address. Check the saved addresses carefully rather than assuming an invalid list simply disables alerts.

Check which findings qualify

The email path selects fresh serious findings. Warnings and advisories, including ordinary page-change warnings, do not qualify. A finding returning after resolution can be fresh again; the original Since date can still remain unchanged.

Both Scan now and scheduled scans can send notifications. Do not use a live scan as a harmless email-preview action. Existing unaltered findings are not an automatic repeated reminder or mail retry queue.

Interpret the delivery evidence

The finding can be stored before sending is attempted. If email fails, another scan of the same still-open issue may not try again because it is no longer fresh. Alert sent indicates the mail helper reported success, not confirmed inbox delivery. Activity shows the latest 60 events and recording is best effort.

Email can include detailed finding descriptions and affected addresses. Keep recipients appropriate for that information. For a missing alert, collect the redacted scan time, finding state, recipient configuration and mail error rather than sending exposed credentials or repeatedly forcing scans.

See the PD Site Sentinel WHMCS guide for related tasks, or explore PD Site Sentinel.