ILLUSTRATIVE EXAMPLE · NOT A LIVE SCAN

A report your developer
can act on.

PHP patch status: unable to verify

No reliable runtime or vendor-package evidence was available in this example. This does not establish whether PHP is present, affected or patched.

Action: Ask the host to identify the PHP runtime serving this domain, confirm the applicable PHP2Shell patches and follow PHP's current session-upload-progress guidance. A command-line PHP version can differ from the web runtime.

Verify: Obtain the hosting package advisory and confirm serving workers were restarted where required.

Example finding: browser security policy absent

Observation: A Content-Security-Policy header was absent from the sampled HTML response. This is a hardening opportunity, not evidence that cross-site scripting is exploitable.

Action: Inventory the scripts, styles and third-party resources the site needs. Test a tailored policy in report-only mode before enforcement; avoid copying a restrictive policy blindly.

Verify: Check representative pages and user flows, review browser console violations, then confirm the intended header on fresh responses.

Completed checks and boundaries

Your purchased report lists the actual URLs and times assessed, the checks completed, unavailable checks, evidence, confidence, priorities, remediation and verification steps. Private application logic and source code remain outside scope.