Website security report.
Evidence you can use.
A useful report explains the observation, its limits and the next step. Explore this illustrative assessment, then start your own.
2 findings need a decision.
1 check is also unverified. Start with the evidence and suggested actions below. Priority order uses the reported severity; your business context still matters.
Public observations · Point-in-time assessmentSuggested first actions
- 01Content Security Policy low reported severity · Website developer
- 02DMARC policy needs review low reported severity · Email administrator / email provider
- 03Provider patch status Establish the missing evidence · Hosting provider
Changes since an earlier assessment
Live reports compare against an earlier saved assessment with matching target, route and coverage. This illustrative report has no assessment history.
What this assessment covers
- Synthetic examples of public web and email configuration checks.
- Shows the structure of a CyberScan report, evidence and recommended actions.
Limits & exclusions
- No requests were made to example.com to produce this example.
- No internal systems, accounts, application business logic or backups were assessed.
Results describe the specified checks at the recorded time. A passing check is not a guarantee of security. Unknown results do not count as passes.
Includes assessment evidence and saved workflow state. API credentials, domain verification tokens and free-text workflow notes are excluded. Workflow state does not change a technical finding.
Inspect the findings
Showing 6 of 6 checks. Full-report and CSV exports include all relevant checks, regardless of filters.
Content Security PolicyWeb security · Direct observation · low severityNeeds attention
Illustrative observation: a Content-Security-Policy header was not present on the inspected response. A policy may exist elsewhere or require application-specific design.
Supporting evidence
EXAMPLE DATA — no CSP header on the inspected responseRecommended next step
Develop a policy for the application, start in report-only mode and test forms, payment flows and third-party integrations.
Read the practical guidanceSuggested owner
Website developer
Copy this finding, its evidence and the requested next step into your support ticket.
DMARC policy needs reviewEmail security · Direct observation · low severityNeeds attention
Illustrative observation: a monitoring-only DMARC policy was found. Legitimate email sources should be reviewed before enforcement changes.
Supporting evidence
EXAMPLE DATA — v=DMARC1; p=noneRecommended next step
Inventory sending services, review alignment and plan a staged enforcement rollout. Avoid switching directly to rejection without testing.
Read the practical guidanceSuggested owner
Email administrator / email provider
Copy this finding, its evidence and the requested next step into your support ticket.
Provider patch statusScanner findings · Not establishedNot verified
Illustrative example of a result that public observations cannot establish. A version string alone does not establish the current patch level.
Supporting evidence
EXAMPLE DATA — no package or provider patch evidence availableRecommended next step
Request the installed package build and the provider advisory confirming any relevant backported fix.
Read the practical guidanceSuggested owner
Hosting provider
Copy this finding, its evidence and the requested next step into your support ticket.
Content-type protectionWeb security · Direct observationObserved pass
Illustrative observation: the response included the nosniff directive.
Supporting evidence
EXAMPLE DATA — X-Content-Type-Options: nosniffRecommended next step
Keep this response header in place and test after application changes.
Read the practical guidanceSuggested owner
Website developer
Copy this finding, its evidence and the requested next step into your support ticket.
HTTPS connectionWeb security · Direct observationObserved pass
Illustrative observation: the HTTPS request completed. This result concerns this connection only.
Supporting evidence
EXAMPLE DATA — HTTPS request completed with HTTP 200Recommended next step
Maintain certificate renewal and monitor the actual domain and all required service names.
Read the practical guidanceSuggested owner
Hosting provider / website administrator
Copy this finding, its evidence and the requested next step into your support ticket.
SPF sender policyEmail security · Direct observationObserved pass
Illustrative observation: one SPF policy record was present. Actual delivery and authorised senders were not tested.
Supporting evidence
EXAMPLE DATA — one SPF policy record observedRecommended next step
Confirm all legitimate sending services are authorised before strengthening enforcement.
Read the practical guidanceSuggested owner
Email administrator
Copy this finding, its evidence and the requested next step into your support ticket.