Skip to main content

Security report for schule-kuettigen.ch

Schule Küttigen · Education · Switzerland

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

59/100

Risk levelMedium

0–100, higher is better. How it is calculated

Schule Küttigen is a local educational institution in Küttigen, Switzerland, providing comprehensive schooling services including kindergarten, primary and secondary education, special education, music school, and social work. The website serves as an information portal for parents, students, and community members, offering news, events, and access to school services. The institution positions itself as a trusted community education provider with a focus on inclusive and diverse educational offerings. Technically, the website is built on the GOViS eGovernment CMS platform, utilizing modern web technologies such as jQuery and Font Awesome. It demonstrates good mobile optimization, accessibility, and SEO practices. The site employs Matomo analytics configured with privacy considerations and a robust cookie consent mechanism, reflecting a mature digital infrastructure. From a security perspective, the website enforces HTTPS and implements cookie consent with granular user control. However, explicit security headers and published security policies are absent, representing areas for improvement. No vulnerabilities or exposed sensitive data were detected, indicating a solid security posture appropriate for its public service nature. Overall, Schule Küttigen's website is professional, trustworthy, and compliant with privacy regulations. It effectively balances user experience with privacy and security, making it a reliable resource for its community. Strategic enhancements in security transparency and incident response documentation would further strengthen its security maturity.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

5 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048
  4. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

Need hands-on remediation? Email guard@offseq.com

Keep watching schule-kuettigen.ch

This scan found 23 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
42
Security headers
75
Email security
70
DNS health
80
Network security
20
GDPR outside view
68
Average
59

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Schule Küttigen operates as a public education provider within the Swiss canton of Aargau, targeting local families and students. Its competitive advantage lies in offering a broad spectrum of educational and supportive services, including special education and extracurricular activities. The business model is government-funded and community-focused, emphasizing accessibility and inclusivity. The website supports this by providing timely news, event information, and easy access to school resources. Partnerships with local government and technology providers like backslash AG and GOViS CMS indicate a stable operational ecosystem. Growth indicators include active communication channels and regular content updates, although no commercial revenue streams or monetization are evident due to its public service nature.

Security posture

The website exhibits a mature security posture with mandatory HTTPS, privacy-compliant cookie consent, and use of privacy-respecting analytics (Matomo). The absence of explicit security headers such as Content-Security-Policy or X-Frame-Options is a minor gap. No incident response or vulnerability disclosure policies are published, which is common for public sector sites but represents an opportunity for enhanced transparency. No exposed credentials, malware, or phishing indicators were found. The site’s security culture appears aligned with GDPR requirements, supported by comprehensive privacy documentation and user consent mechanisms. Overall, the risk level is low, but formalizing security policies and incident channels would improve readiness.

Recommendations

  1. Implement and publish explicit security headers (Content-Security-Policy, X-Frame-Options, etc.) to enhance protection against common web attacks.
  2. Develop and make publicly available a security policy and incident response plan to improve transparency and preparedness.
  3. Consider adding a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  4. Enhance contact information by providing direct email or phone contacts for administrative and security inquiries.
  5. Regularly review and update cookie and privacy policies to maintain compliance with evolving regulations and best practices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Schule Küttigen
Description
Die Schule Küttigen bietet Bildungsdienstleistungen für Kindergarten, Primarschule, Oberstufe, spezielle Förderung, Musikschule, Schulsozialarbeit und ergänzende Angebote in der Gemeinde Küttigen, Schweiz.
Key services
Kindergarten, Primarschule, Oberstufe, Spezielle Förderung, Musikschule, Schulsozialarbeit, Integrierte heilpädagogische Förderung, Deutsch als Zweitsprache, Logopädie, Aufgabenhilfe
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.7.1, Font Awesome 4.7.0, GOViS CMS, c-consent 3.1.0
Frameworks
GOViS eGovernment CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with granular categories
  • Secure cookie settings in analytics
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Transparency
good

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is focused on local education services with clear navigation and relevant information.
  3. Strong privacy and cookie consent mechanisms are implemented.
  4. No contact emails or phone numbers explicitly found in HTML; contact is via form.
  5. No terms of service or explicit security policy documents found.
  6. Use of Matomo analytics with privacy-respecting configuration.
  7. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on the GOViS eGovernment CMS platform, leveraging jQuery 3.7.1 and Font Awesome 4.7.0 for UI components. It uses a modular cookie consent system (c-consent 3.1.0) with granular category controls. Hosting and development are linked to backslash AG, a Swiss internet agency. Performance is moderate with good mobile responsiveness and accessibility features. SEO is supported by appropriate meta tags and Open Graph properties. The analytics implementation uses Matomo with secure cookie settings and deferred script loading. No deprecated or vulnerable libraries were detected. Opportunities exist to modernize by adding security headers and expanding technical documentation for security and compliance.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with schule-kuettigen.ch. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review schule-kuettigen.ch.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.