Skip to main content

Security report for muenchenstein.ch

Einwohnergemeinde Münchenstein · Government · Switzerland

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

Security score

64/100

Risk levelMedium

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

The website www.muenchenstein.ch serves as the official online presence of the Einwohnergemeinde Münchenstein, the municipal government of Münchenstein, Switzerland. It provides comprehensive information and services for residents, families, seniors, foreign residents, and local businesses. The site offers access to administrative services, community news, event announcements, waste disposal information, and local project updates, positioning itself as a key resource for the local population. The business model is that of a governmental service provider focused on community engagement and service delivery. Technically, the website employs modern web technologies including Bootstrap for responsive design, Matomo for analytics, and ES modules for JavaScript. The site is mobile optimized and accessible, with good SEO practices and a clear navigation structure. The CMS used appears to be i-web, a specialized platform for municipal websites. Performance is moderate, with asynchronous loading of analytics scripts and modular JavaScript enhancing user experience. From a security perspective, the site enforces HTTPS and includes a cookie consent mechanism compliant with GDPR. However, it lacks explicit security policy documentation, incident response contacts, and vulnerability disclosure mechanisms such as security.txt. No critical vulnerabilities or exposed sensitive data were detected. The WHOIS data confirms the domain's legitimacy and consistency with the municipal identity. Overall, the website is a trustworthy, well-maintained municipal portal with good content quality and technical implementation. Strategic improvements include publishing a security policy, adding incident response contacts, and enhancing security headers to further strengthen the security posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  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 384-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

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

Keep watching muenchenstein.ch

This scan found 26 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
52
Security headers
40
Email security
65
DNS health
75
Network security
100
GDPR outside view
53
Average
64

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

Münchenstein's municipal website is positioned as an essential local government portal serving a medium-sized community in Switzerland. Its competitive advantage lies in providing a centralized, accessible platform for residents to access services and information. The business model is non-commercial, focused on public service delivery. Revenue streams are typical of municipal funding rather than direct monetization. The target customer segments include residents of all ages, families, seniors, and foreign residents, reflecting a broad community focus. Growth indicators include ongoing projects and digital service expansions such as the online counter (Online-Schalter). The partnership ecosystem includes local schools and project-specific websites, indicating collaboration within the community. Operationally, the site demonstrates a stable and consistent approach to content and service delivery, supporting community engagement and transparency.

Security posture

The website demonstrates a mature security posture with mandatory HTTPS and a cookie consent mechanism aligned with GDPR requirements. No critical security headers were detected in the provided data, suggesting room for improvement in HTTP security configurations. The absence of a published security policy or incident response contact limits transparency and readiness for security incidents. No vulnerability disclosure or security.txt file was found, which is a common best practice for public-facing government sites. The use of Matomo analytics indicates a preference for privacy-respecting tracking. Overall, the site shows good baseline security but would benefit from enhanced documentation and security header implementation to improve resilience and trust.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Implement and publicize an incident response contact email or form to handle security issues.
  3. Add a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  4. Enhance HTTP security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Regularly review and audit third-party scripts and dependencies to mitigate potential vulnerabilities.

Contact details published on the site

Addresses
Legal name
Einwohnergemeinde Münchenstein
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Einwohnergemeinde Münchenstein
Description
Official website of the municipality of Münchenstein providing information about the community, services, politics, events, and local administration.
Key services
Online services (Online-Schalter), Community information, Event announcements, Administrative services, Waste disposal information, Local projects and planning, Contact and support
Content quality
good
Branding
consistent

Technology

Stack
Matomo Analytics, JavaScript ES Modules, CSS3, HTML5
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

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

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Transparency
basic

Site quality

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

Key observations

  1. Website is a well-structured municipal government portal for Münchenstein, Switzerland.
  2. Content is comprehensive for residents and local stakeholders.
  3. Good use of modern web technologies and accessibility features.
  4. Privacy and cookie policies are present and GDPR compliant.
  5. No visible security policy or incident response information.
  6. No terms of service page found.
  7. No vulnerability disclosure or security.txt present.
  8. No suspicious or malicious content detected.
  9. Social media presence limited to Instagram link.
  10. WHOIS data confirms legitimacy and consistency.
Technical notes

Notes

The website is built on a modern tech stack featuring Bootstrap for responsive design and Matomo for analytics, indicating a focus on usability and privacy. The use of ES modules and import maps reflects up-to-date JavaScript practices. The CMS appears to be i-web, specialized for municipal websites, which supports structured content management and modular design. Performance is moderate with asynchronous script loading, though no explicit performance metrics were provided. The site is mobile optimized and includes accessibility features such as ARIA labels and keyboard navigation support. SEO is supported by meta tags and structured navigation. Technical risks are minimal but include the lack of advanced security headers and absence of a documented security framework.
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 muenchenstein.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 muenchenstein.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.