A SiteLock report is useful when each finding becomes a specific action with an owner and a verification step. Read the scan type, scope and completion time before deciding that a warning means infection or that a green result proves the entire application is safe.
01 Review and assign findings
- Open the correct website's Security Report. Confirm the domain and expand the feature that needs attention.
- Open its details and inspect the latest completed result. A configuration problem or unfinished scan is different from a completed scan with no findings.
- Separate detected malicious content from suspicious items awaiting review and software vulnerabilities that require an update. Record affected paths or URLs and the reported severity.
- Assign a next action. The developer can assess application updates; the hosting administrator can investigate access failures; an eligible cleanup service can address covered malware. Confirm the purchased scope before expecting automatic repair.
- Export or download the relevant report for the incident record. Restrict access because paths and vulnerability details can reveal useful information about your application.
- After the action, obtain a fresh result for the affected scan and test the website function that was changed.
Common questions
Does a vulnerability finding mean the site has been hacked?
It identifies exposure that needs assessment. Evidence of vulnerable software and evidence of a successful compromise are different. Patch or replace affected software and investigate related activity without dismissing the warning.
Why does the report list features I have not configured?
The dashboard can show setup tasks and upgrade options. Check your subscription before treating every displayed component as an active, included service.
Can I give the full report to a customer?
Share an appropriate summary of impact and corrective action. Give technical evidence to authorised people who need it, and remove personal data, access details and unrelated findings.