Review infrastructure, software, protections and findings in one workspace.
Who can do this: Website owners and permitted organisation colleagues.
Before you start: Private evidence requires the existing organisation and exact-asset permissions. Apex and www can have different behavior.
Steps and checks
- Choose the customer and websiteManual check
Select the organisation and exact website above. The URL retains your permitted selection, report source and section.
- Open full investigationManual check
Use this explicit action to include authorised older discoveries and later constituent checks within the displayed host group. Sources retain their own dates; this is not one new scan.
- Read the named sectionsManual check
Use Overview, Infrastructure and platform, Software and versions, Protection and TLS, Findings and actions, and Evidence and reports. Observed server and OS clues remain separate from installed patch verification.
- Review actions or exportManual check
Open finding management for an included hostname. Downloads use the displayed investigation or baseline and its source dates. Deployment inventory is under Evidence and reports.
- Run new work explicitlyManual check
New check opens the public check form. Deeper TLS and recurring collection are optional controls after retained evidence, with their existing permission and consent checks.
Only labelled account facts are verified here. Manual checks and viewing a guide do not prove setup, receipt or access is complete.
Expected result
A dated, source-labelled investigation preserves its host scope across navigation and downloads.
Common questions
Why does the latest check show less evidence?
A later check may cover only one hostname. Open full investigation to include a wider host group when your account is permitted to read it.
Does detecting a WAF prove protection?
No. External observations cannot establish enabled WAF rules, effectiveness or installed patches.
New here?
Take a short tour of checks, evidence, monitoring and account scope.