Skip to main content

Security report for kuettigen.ch

Gemeinde Küttigen · Government · Switzerland

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

Security score

57/100

Risk levelMedium

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

Gemeinde Küttigen operates as the official municipal government website for the community of Küttigen in Switzerland. It provides residents and visitors with access to administrative services, local news, event information, and various public resources. The website is positioned as a trusted local government portal, leveraging the GOViS eGovernment CMS platform to deliver content in German tailored to its regional audience. Key services include an online service counter, news updates, event calendars, and a customer portal, supporting efficient citizen engagement and municipal transparency. From a technical perspective, the site employs modern web technologies such as jQuery and Font Awesome, with a focus on accessibility and mobile responsiveness. The use of Matomo analytics configured with privacy considerations demonstrates a commitment to user data protection. The website is hosted securely over HTTPS, although explicit security headers are not evident in the HTML source, representing an area for improvement. Security posture is solid with no visible vulnerabilities or exposed sensitive data. The site implements a comprehensive cookie consent mechanism aligned with GDPR requirements, enhancing privacy compliance. However, the absence of explicit security policies, incident response contacts, and vulnerability disclosure mechanisms suggests room for maturity in security governance. Overall, the website reflects a professional, trustworthy municipal government presence with good content quality and technical implementation. Strategic recommendations include enhancing security headers, publishing security policies, and establishing formal vulnerability disclosure processes to further strengthen the security and compliance posture.

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 kuettigen.ch

This scan found 24 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. The full timeline opens with your unlock code.

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
55
DNS health
80
Network security
20
GDPR outside view
68
Average
57

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

The website serves as the digital face of the Gemeinde Küttigen, a small municipal government entity in Switzerland's Aargau canton. Its market position is that of a local government authority providing essential public services and information to residents. The business model is non-commercial, focused on public administration and community engagement. Revenue streams are typical of municipal budgets rather than commercial sales. The target customer segment is local residents, businesses, and visitors seeking municipal services and information. The partnership ecosystem includes regional government bodies, local schools, and service providers such as the GOViS CMS and local agencies. Growth indicators are aligned with community development initiatives like 'Küttigen 2040'. The website's operations emphasize transparency, accessibility, and digital service delivery consistent with Swiss eGovernment standards.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and privacy-respecting analytics via Matomo. The cookie consent mechanism is comprehensive and user-friendly, supporting GDPR compliance. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. However, the lack of explicit security headers such as Content-Security-Policy or X-Frame-Options is a notable gap. There is no published security policy or incident response contact information, which limits transparency in security governance. The absence of a vulnerability disclosure or security.txt file reduces opportunities for coordinated vulnerability reporting. Overall, the site is secure for its purpose but could benefit from formalizing security policies and enhancing technical security controls.

Recommendations

  1. Implement and configure security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  2. Publish a dedicated security policy page outlining security practices and incident response procedures.
  3. Establish a vulnerability disclosure program or publish a security.txt file to facilitate responsible reporting.
  4. Enhance contact information availability, including security and general contact emails and phone numbers.
  5. Regularly audit third-party scripts and libraries to ensure no vulnerabilities are introduced.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Gemeinde Küttigen
Description
Die Gemeinde Küttigen bietet Online-Dienstleistungen, Informationen zu Verwaltung, Politik, Wirtschaft, Kultur, Gesundheit und Freizeit für die Einwohner und Interessenten der Gemeinde Küttigen im Kanton Aargau, Schweiz.
Key services
Online-Schalter für Verwaltungsdienstleistungen, Informationen zu Politik, Verwaltung, Soziales, Gesundheit, Freizeit, Kultur, Wirtschaft, Veranstaltungsankündigungen, Newsletter, Kundenportal
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.7.1, Font Awesome 4.7.0, GOViS CMS, c-consent cookie consent library
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
  • No exposed sensitive data in HTML
  • Use of secure cookies in analytics

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 a municipal government portal for Gemeinde Küttigen, Switzerland.
  2. Content is in German targeting local residents and stakeholders.
  3. Comprehensive cookie consent and privacy policy implemented.
  4. No contact emails or phone numbers explicitly found in HTML content.
  5. No terms of service or security policy pages detected.
  6. Use of Matomo analytics with privacy-respecting configuration.
  7. No signs of suspicious or malicious content.
  8. Good technical implementation with modern libraries and CMS.
  9. No explicit security headers detected in HTML source.
  10. No vulnerability disclosure or security.txt found.
Technical notes

Notes

The website is built on the GOViS eGovernment CMS platform, utilizing jQuery 3.7.1 and Font Awesome 4.7.0 for UI components and icons. The cookie consent is managed by the c-consent library version 3.1.0, providing granular user control over cookie categories. The site is served over HTTPS with secure cookie settings for analytics. Performance is moderate with no evident blocking scripts or heavy resources. The site is mobile optimized and accessible, with semantic HTML and ARIA roles used appropriately. SEO is supported by meta keywords, descriptions, canonical links, and Open Graph tags. Hosting provider details are not explicitly disclosed. There is no evidence of deprecated or vulnerable libraries. Overall, the technical infrastructure is modern and well-maintained, supporting a reliable user experience.
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 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 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.