Site Sentinel processes a batch of websites per run. Check individual scan times to see whether the sites you care about were included.

Review the controls

1. Open PD Modules → Site Sentinel → Settings.
2. Review Sites to scan per run. Its configured range is 5–500 sites.
3. Without Pro, check Sites included without Pro, which can be set between 1 and 25 and defaults to 10.
4. Check each row’s State, pause setting and Scanned time in Sites.
5. In the PD Modules jobs view, review Website security scan, its enabled state, most recent run and platform cron status.

The scheduled job is registered daily. That is a run interval, not a promise that every site is checked every day or at a particular time. Scan now starts the next general batch; it is not a targeted scan of whichever row you are looking at.

Understand the free-tier selection

Without Pro, the allowance covers a fixed set of the oldest unpaused site rows, not every listed site in rotation. Pausing or resuming an older row can change that set. Rows beyond it are labelled Not scanned (free limit).

The released queue first selects the next batch, then filters it by that allowance. If unscanned rows outside the allowance fill the selected batch, eligible rows can be delayed even when the result says there are no sites to scan. Check allowance labels and unchanged scan times before assuming coverage is complete. Review the batch size, allowance labels and oldest unpaused rows together rather than deleting rows as a repair.

Verify the run

Compare its summary with the relevant rows’ timestamps and reachability. A completed run is not proof that all requests succeeded, all checks were enabled or the whole portfolio was examined. Pro removes the free-tier cap; batch size, scheduling and reachability still matter.

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