Glarion · sample reportBack to Glarion
example.com · prepared by Northstar Studio · 6 September 2026
Use Print or Ctrl/Cmd+P, then choose “Save as PDF”. Turn off browser headers and footers.

Fictional example · all findings and data are invented for this sample.

Prepared by Northstar Studio

Website security review

example.com — prepared for Example Client

Scanned 6 September 2026

2 issues need attention.

A snapshot of the website's public surface. Use the findings below to plan fixes and review decisions.

Need attention
2
Worth a decision
1
For reference
2

Start with these actions

Review these priorities with the team responsible for the website. Each item links to its evidence and recommended fix.

  1. HighRenew the TLS certificate
  2. MediumAdd a Content Security Policy

Needs attention

Findings with a concrete fix, most important first.

Action 01 High

Renew the TLS certificate

Why it matters

If this certificate expires, browsers may warn visitors or block access to the website.

What to do

Ask the hosting provider to confirm automatic renewal. Once renewed, check that the replacement certificate is being served.

Observed evidence

Fictional observation: the certificate for example.com:443 expires in 18 days.
Action 02 Medium

Add a Content Security Policy

Why it matters

The browser has no declared policy limiting which scripts and resources this page may load. A policy can reduce the impact of injected content.

What to do

Ask the development team to deploy a report-only policy first. Review required sources and violations before enforcing it.

Observed evidence

Fictional observation: the homepage response did not include a Content-Security-Policy header.

Worth a decision

Whether these matter depends on how the site is used.

Decision 01 Low

Publish a security contact

Why it matters

Researchers may have difficulty finding the right person to report a security issue to. The right contact depends on your support process.

What to do

Choose a monitored contact address and decide whether to publish it in a security.txt file. Keep its expiry date current.

Observed evidence

Fictional observation: /.well-known/security.txt was not found.

For reference

Observations kept for context, not classified as actions or decisions. These are not a count of passed security tests.