Skip to main content

Security report for oensingen.ch

Gemeinde Oensingen · Government · Switzerland

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

Security score

66/100

Risk levelMedium

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

Gemeinde Oensingen operates an official municipal website serving the local community in Switzerland. The site provides comprehensive information about local government, services, politics, events, education, and tourism. It targets residents, local businesses, and visitors, offering online services such as building permits, waste disposal, and job listings. The website positions itself as a central information hub for the Oensingen community with a focus on quality of life and accessibility. Technically, the website uses a modern CMS platform (i-web.ch), employs responsive design, and integrates Matomo analytics for privacy-conscious user tracking. The infrastructure appears stable with good mobile optimization and accessibility features. The site uses HTTPS and includes CSRF protection on login forms, indicating a reasonable security posture. Security-wise, while HTTPS and basic protections are in place, the site lacks explicit security policies, incident response contacts, and vulnerability disclosure mechanisms. No critical vulnerabilities or suspicious content were detected. Privacy compliance is supported by clear privacy and cookie policies with consent mechanisms. Overall, the website is trustworthy, professionally maintained, and suitable for its government service role. Strategic improvements include publishing security policies, adding incident response information, and enhancing security headers to strengthen the security posture further.

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 oensingen.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
42
Security headers
40
Email security
85
DNS health
75
Network security
100
GDPR outside view
53
Average
66

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 reflects a small municipal government entity focused on serving its local population with administrative and community services. Its market position is that of a trusted local authority with a stable user base. The business model is service-oriented, providing digital access to government functions and community information. The site links to multiple partner organizations including local churches, schools, and energy initiatives, indicating a collaborative ecosystem. Growth indicators include active event listings and digital service offerings. Revenue streams are typical for government entities, likely funded by local taxes and public budgets.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and CSRF tokens implemented in forms. No exposed sensitive data or vulnerable libraries were found. However, the absence of a published security policy, incident response contacts, and vulnerability disclosure channels indicates gaps in formal security governance. The use of Matomo analytics respects privacy but tracking is moderate. Security headers are not explicitly detected, suggesting room for improvement. Overall, the site is secure for general public use but could benefit from enhanced transparency and formal security documentation.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and user guidance.
  2. Provide clear incident response contact information such as security@ or abuse@ email addresses.
  3. Implement and publish a security.txt file to facilitate vulnerability reporting.
  4. Add security headers like Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Regularly review and update third-party scripts and dependencies to mitigate vulnerabilities.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Gemeinde Oensingen
Description
Official municipal website providing information about the community of Oensingen, including administration, politics, services, events, and local amenities.
Key services
Online-Schalter (online services), Entsorgung (waste disposal), Baugesuch (building permits), Primarschule (primary school information), Dienstleistungen A-Z (services A-Z), Offene Stellen (job vacancies), Reglemente (regulations), eUmzug (moving services)
Content quality
good
Branding
consistent

Technology

Stack
Matomo Analytics, Bootstrap (implied by classes and modal usage), SVG icons, JavaScript modules, CSS compiled assets
Frameworks
Unknown CMS framework (likely i-web.ch platform)
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of CSRF tokens in login form

Analytics and tracking

Services
Matomo
Tracking level
moderate
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. Official municipal website for Gemeinde Oensingen, Switzerland.
  2. Comprehensive content covering local government, services, events, and community information.
  3. Good use of modern web technologies and responsive design.
  4. Privacy and cookie policies are present with consent mechanisms.
  5. No signs of malicious or suspicious content.
  6. No explicit security policy or incident response information published.
  7. Use of Matomo analytics with anonymized data collection.
  8. Multiple external links to official partner and community sites.
  9. Contact information is clearly provided with email, phone, and physical address.
  10. Login form includes CSRF token for security.
Technical notes

Notes

The website is built on a specialized CMS platform (i-web.ch) tailored for municipal websites, leveraging modern web technologies including JavaScript modules, SVG icons, and responsive CSS. Performance is moderate with optimized images and asynchronous script loading. The site is mobile-friendly and accessible, with clear navigation and semantic HTML structure. SEO is supported by meta tags and structured navigation. Hosting appears to be Swiss-based, enhancing data sovereignty. Technical risks are minimal but could be reduced by adopting additional security headers and continuous monitoring.
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 oensingen.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 oensingen.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.