Your hosting team can use PD Guard’s Report to prioritise environment and configuration checks. A passing summary is a result for the checks that ran, not proof that the entire installation is secure.

Read a current result

1. Open PD Modules → Guard → Report.
2. Review the report generation time and grouped findings.
3. Read each warning or failure’s value and recommendation before changing anything.
4. Use the report’s refresh control when you need a new measurement rather than a cached result.

The ordinary report can reuse an environment result for about ten minutes. A refresh gathers new facts and may make outbound certificate or exposure checks; it is not merely refreshing the text on screen. It does not automatically apply the recommended repairs.

Check the scope

Read Platform settings checked carefully. Staff-account hygiene, staff two-factor coverage, last system cron, mail transport, update availability and several installation-layout checks are outside this report’s platform coverage. These omissions do not mean those settings are correct.

The headline can be OK while warnings or informational limitations remain. Check the individual rows and scope notes rather than counting green items alone. A configured mail transport is not a successful delivery test, and a configured HTTPS address is not a complete application-security assessment.

Verify a change

Your hosting team should identify the exact check, measurement time, value, recommendation and any unavailable measurements. Use your own platform or hosting administration controls for a change you understand, then request a fresh report and compare that row. For a server-level change outside your team’s access, work with the systems administrator or infrastructure provider responsible for your installation. A warning is not, by itself, a module fault.

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