Skip to main content

Security report for zukunft-wettingen.ch

Gemeinde Wettingen · Government · Switzerland

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

Security score

58/100

Risk levelMedium

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

Zukunft Wettingen is the official municipal website for the community of Wettingen in the canton of Aargau, Switzerland. It serves as a transparent platform to inform residents and stakeholders about ongoing and upcoming community projects aimed at sustainable development and maintaining the quality of life. The site emphasizes proactive communication and engagement with its audience, primarily local residents and interested parties. The business model is centered on providing accessible, clear information about municipal initiatives and fostering community involvement. Technically, the website is built on the TYPO3 CMS platform, a reputable open-source content management system. It integrates modern web technologies including embedded Vimeo videos and Google Analytics via Google Tag Manager for performance and user behavior insights. The site is mobile-optimized, accessible, and SEO-friendly, with a moderate performance profile. Cookie consent is implemented with an opt-in mechanism, reflecting good privacy practices. From a security perspective, the site enforces HTTPS and employs cookie consent mechanisms, but lacks publicly available formal security policies or incident response contacts. No critical vulnerabilities or exposed sensitive data were detected. The WHOIS data aligns well with the municipal identity, confirming legitimacy and trustworthiness. Overall, the site demonstrates a solid security posture with room for improvement in formal security documentation and headers. The overall risk assessment is low, with the site presenting a trustworthy, professional, and privacy-conscious presence. Strategic recommendations include publishing a security policy, adding incident response contacts, enhancing security headers, and continuous monitoring of third-party scripts to maintain security and compliance standards.

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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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

  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 zukunft-wettingen.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. 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
72
Security headers
35
Email security
65
DNS health
85
Network security
20
GDPR outside view
68
Average
58

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

Zukunft Wettingen holds a strong market position as the largest municipality in Aargau, Switzerland, focusing on sustainable community development. Its competitive advantage lies in transparent communication and proactive engagement with residents regarding municipal projects. The business model is informational and service-oriented, targeting local citizens and stakeholders interested in community planning and development. Revenue streams are typical of government entities, funded by municipal budgets rather than commercial sales. The partnership ecosystem includes related local development projects and the official municipal website. Growth indicators include ongoing infrastructure and educational projects. Strategic observations highlight a commitment to sustainability, quality of life, and digital maturity through modern CMS adoption and analytics integration.

Security posture

The website exhibits a mature security posture with mandatory HTTPS encryption and a cookie consent mechanism aligned with GDPR requirements. No exposed sensitive data or vulnerable libraries were identified in the HTML content. However, the absence of explicit security policies, incident response information, and security headers such as Content-Security-Policy or X-Frame-Options indicates areas for enhancement. The use of reputable third-party services like Google Analytics and Vimeo is managed with user consent. Overall, the site maintains a secure environment appropriate for a government informational portal but should formalize security governance and incident handling to improve resilience and trust.

Recommendations

  1. Publish a formal security policy accessible from the website footer or dedicated page.
  2. Provide clear incident response contact information such as security@ or abuse@ email addresses.
  3. Implement and configure security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Regularly audit and update third-party scripts and libraries to mitigate vulnerabilities.
  5. Enhance transparency by detailing data retention policies and cookie usage in the privacy policy.

Contact details published on the site

Addresses
Legal name
Gemeinde Wettingen
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Gemeinde Wettingen
Description
Wettingen ist eine attraktive und lebenswerte Gemeinde im Aargau. Die Gemeinde handelt vorausschauend und nimmt Chancen zur Realisierung wahr, um Leben, Wohnen und Arbeiten attraktiv zu gestalten.
Key services
Information zu Gemeindeprojekten, Transparente Kommunikation, Förderung von Standortqualität
Content quality
good
Branding
consistent

Technology

Stack
TYPO3 CMS, Vimeo (video embedding), Google Tag Manager, Google Analytics
Frameworks
TYPO3 CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with opt-in mechanism
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
basic

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 professionally presented in German language targeting local residents.
  3. Strong focus on transparency and community engagement.
  4. Uses modern CMS TYPO3 and integrates video content and analytics.
  5. Cookie consent mechanism is implemented with opt-in for statistics.
  6. No evidence of security policy or incident response information publicly available.
  7. No terms of service page found.
  8. Contact information is clearly provided with physical address, phone, and email.
  9. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on TYPO3 CMS, a robust and widely used open-source content management system, ensuring a solid technical foundation. It integrates multimedia content via Vimeo and analytics through Google Tag Manager and Google Analytics, indicating a modern digital infrastructure. The site is mobile-responsive and accessible, with good SEO practices evident in meta tags and structured navigation. Performance is moderate, with potential for optimization in asset loading and caching. No critical technical debt or deprecated technologies were detected. Hosting details are not explicitly available, but HTTPS and modern JavaScript usage suggest a contemporary hosting environment. Opportunities exist to improve security headers and formalize technical documentation.
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 zukunft-wettingen.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 zukunft-wettingen.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.