Use Needs attention to prioritise the findings from completed outside-in scans. An empty list has several possible explanations, so verify coverage before calling a site clean.

Read the current findings

1. Open PD Modules → Site Sentinel → Needs attention.
2. Review the Serious, Fix and Advisory findings, beginning with the site and client association.
3. Use Serious only, Worth fixing or Advisory to narrow the list.
4. Read What it means and Since. Check Show accepted if an expected finding is hidden.
5. Compare the site’s current State and Scanned time on Sites.

The table loads up to 500 open findings. Since reflects the original first detection, including a finding that later reappears; it is not necessarily the latest incident start. Site summary counts and accepted-filtered lists can differ.

Check whether the absence is meaningful

Confirm that the site was actually scanned, was reachable and was within the allowance. Check enabled checks, Pro-only features and the chosen severity/accepted filters. The report’s latest scan time is the newest across the portfolio, not proof that every row was checked then.

An unreachable home page stops the remaining checks. Findings absent from a later result can be marked resolved even when the relevant check was disabled, failed or no longer ran. A disappearing finding alone does not prove that the underlying website was repaired.

Verify the website directly

Check the website through your normal authorised administration process and compare a fresh, relevant result. Keep exposed credentials and private file contents out of screenshots. Site Sentinel is an outside-in check of selected responses, not a server-file malware scan or a complete site audit.

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