Skip to main content

Security report for suhr.ch

Gemeinde Suhr · Government · Switzerland

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

Security score

68/100

Risk levelMedium

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

The website www.suhr.ch serves as the official digital presence of the municipality of Suhr in Switzerland. It provides comprehensive information about the community, local government, services, events, and digital offerings such as an online service portal. The site targets residents and visitors seeking municipal information and services. The business model is that of a government service portal, focusing on transparency, accessibility, and community engagement. The website is well-branded, consistent, and trustworthy, reflecting its official status. Technically, the site is built on a modern stack including HTML5, CSS3, JavaScript, and a proprietary CMS platform (i-web.ch). It uses Matomo for analytics, indicating a privacy-conscious approach. The site is mobile-optimized, accessible, and SEO-friendly, with good performance characteristics. The presence of accessibility features and a dedicated accessibility mode enhances inclusivity. From a security perspective, the site enforces HTTPS and employs secure login forms with password reset capabilities. However, it lacks explicit security headers and does not publish a security policy or vulnerability disclosure information. No vulnerabilities or exposed sensitive data were detected. Overall, the security posture is solid but could be improved with additional headers and transparency. The overall risk assessment is low, with no critical issues detected. Strategic recommendations include implementing security headers, publishing a security policy, and adding vulnerability disclosure mechanisms to enhance trust and security culture. The site is suitable for its purpose as a municipal information portal and demonstrates good digital maturity.

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 suhr.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
52
Security headers
40
Email security
80
DNS health
85
Network security
100
GDPR outside view
53
Average
68

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention suhr.ch, from OffSeq Breach.

Total records
1
Employees
0
Customers
1
Third parties
0
Weak passwords
0%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for suhr.ch.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

The municipality of Suhr operates this website as a key communication and service channel for its residents and stakeholders. Its market position is that of a local government authority, providing essential public services and information. The business model is non-commercial, focusing on public administration and community engagement. Revenue streams are not applicable. The target customer segments are local residents, businesses, and visitors. Growth indicators include digital service adoption such as the online service portal and event management. Partnerships with cantonal and federal entities are evident through linked domains. The website reflects a stable and professional operation with a focus on transparency and accessibility.

Security posture

The website demonstrates a moderate to good security maturity level. HTTPS is enforced, and no sensitive data is exposed in the HTML content. The login form includes password reset functionality, indicating user account management security. However, the absence of security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces the overall security hardening. There is no published incident response or security contact information, which limits readiness for security events. GDPR compliance is indicated through privacy policy and cookie consent mechanisms. No vulnerabilities or outdated libraries were detected. The security culture appears cautious but could benefit from enhanced transparency and technical controls.

Recommendations

  1. Implement standard security headers including CSP, HSTS, X-Frame-Options, and X-Content-Type-Options to improve security posture.
  2. Publish a dedicated security policy page outlining security practices and incident response procedures.
  3. Add a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  4. Enhance transparency by providing contact channels specifically for security incidents (e.g., security@ or abuse@ email addresses).
  5. Regularly audit and update third-party libraries and CMS components to mitigate potential vulnerabilities.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Gemeinde Suhr
Description
Official website of the municipality of Suhr providing information about the community, local government, services, events, and digital offerings.
Key services
Online services (Online-Schalter), Community news and events, Contact and administrative information, Room reservations, Information on local politics and administration
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Matomo Analytics
Frameworks
i-web.ch CMS (custom or proprietary CMS)
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Secure login form with password reset link

Analytics and tracking

Services
Matomo
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Matomo
Marketing tools
Matomo Analytics
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 primarily in German (Swiss German locale).
  3. Site uses HTTPS with valid SSL certificates.
  4. Contact information is prominently displayed and consistent.
  5. Site includes accessibility features and an accessibility mode toggle.
  6. No social media links detected.
  7. Multiple modals for contact, login, and search enhance UX.
  8. No explicit privacy or security policy pages beyond basic privacy and imprint pages.
  9. No visible security.txt or vulnerability disclosure information.
Technical notes

Notes

The website is built on a modern and maintainable technology stack, leveraging HTML5, CSS3, JavaScript, and a proprietary CMS platform (i-web.ch). It uses Matomo analytics for privacy-respecting user tracking. The site is mobile-responsive and includes accessibility features, enhancing user experience across devices and user groups. Performance is moderate, with no major bottlenecks detected. The site uses asynchronous loading for analytics scripts, improving load times. There is room for improvement in security headers and explicit hosting provider identification. Overall, the technical infrastructure supports the business needs effectively with opportunities for incremental modernization.
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 suhr.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 suhr.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.