Skip to main content

Security report for zurzach.ch

Gemeinde Zurzach · Government · Switzerland

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

Security score

65/100

Risk levelMedium

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

The Zurzach website serves as an official municipal and tourism portal for the community of Zurzach, Switzerland. It provides residents and visitors with information about local government services, politics, living conditions, education, social services, and tourism offerings such as thermal baths and wellness. The site is positioned as a trusted local government and tourism information source, targeting residents and tourists alike. The business model is public sector focused, promoting community services and regional tourism. Technically, the site uses a modern JavaScript stack with ES modules, Matomo analytics for privacy-conscious tracking, and a CMS likely provided by i-web. The site is mobile optimized and accessible, with a moderate performance profile. Security posture is adequate with HTTPS usage and no visible vulnerabilities, though security headers and explicit policies could be improved. Privacy compliance is good, with clear privacy and cookie policies and GDPR adherence. Overall, the site is professional, trustworthy, and safe for general audiences.

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

This scan found 25 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
70
DNS health
75
Network security
100
GDPR outside view
53
Average
65

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

Zurzach operates as a small municipal government entity with a complementary tourism promotion function. Its market position is local and regional, focusing on community engagement and visitor attraction. The website supports public administration transparency and tourism marketing, with key services including municipal governance information and wellness tourism. The partnership with badzurzach.info enhances tourism offerings. The business model is non-commercial, funded by public resources, emphasizing service delivery rather than revenue generation. Growth indicators are limited but stable, reflecting municipal service continuity. The partnership ecosystem is modest, centered on local tourism collaboration. Strategic observations suggest opportunities to enhance digital engagement and security transparency.

Security posture

The website demonstrates a moderate security maturity level. HTTPS is enforced, and no sensitive data is exposed in the HTML. The use of Matomo analytics indicates a privacy-conscious approach. However, the absence of visible security headers such as Content Security Policy, HSTS, and X-Frame-Options suggests room for improvement. No vulnerability disclosures or incident response contacts are published, which could hinder timely security issue reporting. Compliance with GDPR is evident through privacy and cookie policies. The security culture appears basic but functional, suitable for a municipal website with low-risk profile. Enhancing security headers and publishing incident response information would strengthen the posture.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to mitigate common web attacks.
  2. Publish a clear security policy and incident response contact information to improve transparency and readiness.
  3. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  4. Regularly audit third-party scripts and libraries to ensure no vulnerabilities are introduced.
  5. Enhance SEO and accessibility features to improve user experience and reach.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Gemeinde Zurzach
Description
The website serves as a portal for the municipality of Zurzach and its tourism sector, providing information about local administration, politics, living, education, social services, and tourism including thermal baths, wellness, dining, and accommodation.
Key services
Municipal administration and political information, Tourism services including wellness and accommodation
Content quality
good
Branding
consistent

Technology

Stack
Matomo Analytics, JavaScript ES Modules, CSS Stylesheets, ReadSpeaker WebReader
Performance
moderate
Mobile
good
Accessibility
good
SEO
basic

Security

Observed score
70/100
Good practices seen
  • HTTPS usage inferred from URL
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries

Analytics and tracking

Services
Matomo
Tracking level
minimal
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 municipal and tourism portal for Zurzach, Switzerland.
  2. Content is in German (de-CH) and well structured.
  3. No forms detected in the HTML content provided.
  4. No direct contact emails or phone numbers found in the HTML content.
  5. Privacy and cookie policies are present and GDPR compliant.
  6. No explicit security or incident response policies published.
  7. Use of Matomo analytics with anonymized data processing in Switzerland.
  8. No advertising or affiliate programs detected.
  9. No social media links found in the provided HTML.
  10. No security headers visible in the HTML; likely configured at server level.
Technical notes

Notes

The website uses a modern front-end technology stack with ES modules and CSS stylesheets, supported by a CMS likely from i-web. Analytics are handled via Matomo, emphasizing privacy and data localization in Switzerland. The site loads scripts asynchronously and uses module preloading for performance optimization. Mobile optimization and accessibility are good, with responsive design and ReadSpeaker integration for accessibility. Performance is moderate, with potential for improvement by optimizing asset delivery and caching. No major technical debt or obsolete technologies detected. The absence of explicit security headers is a technical risk. Overall, the infrastructure is stable and suitable for a municipal portal.
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 zurzach.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 zurzach.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.