Site Sentinel checks a small set of common website exposure locations. A finding gives you a reason to investigate access to that specific resource.

Locate the evidence safely

1. Open PD Modules → Site Sentinel → Needs attention.
2. Find A file is readable that should not be or A directory can be browsed.
3. Confirm the site, finding subject, last scan time and What it means.
4. Keep any exposed credentials, download links and private contents out of screenshots and ordinary support attachments.

The exposed-file check uses a successful response plus a body pattern, rather than treating every HTTP success as exposure. Directory-listing detection also uses page patterns. Those patterns reduce common false positives; they are not a full content classification or a complete list of all possible backup names.

Fix access through the site’s own controls

Review the affected resource through your authorised website or hosting administration process. Remove unintended public access as appropriate and review any credentials that may have been exposed. Site Sentinel does not remove the resource, change access rules or rotate those credentials for you.

Verify the specific outcome

Check that unauthenticated visitors can no longer retrieve the sensitive resource through the affected address. Then arrange a scan of the relevant site and confirm its timestamp advances.

The module examines selected locations beneath the final home-page address. Failed probes, redirected resources, response limits or disabled checks can leave gaps. A finding disappearing from Needs attention does not alone establish that the resource was repaired or that other copies are inaccessible.

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