A security lab should be secure itself

Here is how this website protects you, in the open, so you can check it.

How the site is built

  • Mostly static pages. The public pages are pre-built HTML. Only the course accounts and the shop use a small server API and database, and no admin panel is exposed to the internet. Less software running means fewer ways in.
  • HTTPS everywhere, with HTTP Strict Transport Security so browsers never fall back to an unencrypted connection.
  • A strict Content Security Policy. The browser is told to run only the site's own scripts, each one pinned by its cryptographic hash. Injected code would be blocked.
  • No trackers. No advertising networks, no social media widgets, no external fonts. Videos are served from this site. The only outside script is Cloudflare Turnstile, which loads on forms only, once you start filling them in, to check that a person is sending.
  • Private tools. The tools run in your browser and send nothing.

The security headers

HeaderWhat it does
Content-Security-PolicyLimits which scripts, styles, images, and connections the page may use.
Strict-Transport-SecurityForces HTTPS for a year.
X-Content-Type-OptionsStops the browser from guessing file types.
X-Frame-Options and frame-ancestorsPrevents the site from being framed by others (clickjacking).
Referrer-PolicyShares only the site name, not full page addresses, with other sites.
Permissions-PolicyTurns off camera, microphone, location, and payment features the site never needs.

Found a problem?

If you believe you have found a security issue on this site, please report it through the contact page. Contact details are also published in security.txt. Please do not test against other people's data or disrupt the service.