Skip to main content

Security report for bernex.ch

Commune de Bernex · Government · Switzerland

High risk. 8 critical or high findings in Network security, Security headers and 2 other checks.

Security score

49/100

Risk levelHigh

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

The website www.bernex.ch serves as the official online presence for the Commune de Bernex, a local government entity in Switzerland. It provides municipal information and services targeted primarily at residents and visitors of Bernex. The site employs modern web technologies such as Nuxt.js and jQuery, with Google Tag Manager integrated for analytics purposes. The design and content quality are basic but consistent with a small government entity's needs. Security posture is limited, with no visible security headers or published security policies, and privacy compliance is minimal due to the absence of privacy and cookie policies. Overall, the site is accessible and safe, but improvements in security and privacy transparency are recommended.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

8 findings rated critical or high. Fix these first.

  1. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • 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

  2. 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';…

  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

Keep watching bernex.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. The full timeline opens with your unlock code.

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
60
Email security
70
DNS health
75
Network security
0
GDPR outside view
35
Average
52
After the cap
49

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 · found on this site
  • 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

As a municipal government website, the business model is essential and focused on public service delivery. The site targets local residents and stakeholders, providing official information and resources. The market position is that of a local authority with no commercial competition. The use of Google Tag Manager indicates some level of digital maturity in tracking user interactions. However, the lack of detailed privacy and security policies suggests room for growth in compliance and trust-building measures. No partnerships or subsidiaries are evident from the data.

Security posture

The security maturity level is basic. The site uses HTTPS (assumed but not explicitly confirmed in the snippet), but no security headers such as Content-Security-Policy or X-Frame-Options were detected. There is no evidence of a vulnerability disclosure program or incident response contact channels. The absence of privacy and cookie policies indicates compliance gaps with GDPR and related regulations. No exposed sensitive data or vulnerable libraries were identified, but the security posture would benefit from enhancements in headers, policies, and transparency.

Recommendations

  1. Implement comprehensive privacy and cookie policies with clear GDPR compliance statements.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  3. Publish a vulnerability disclosure policy and security.txt file to improve transparency and incident response readiness.
  4. Ensure all forms and data collection points are secured and provide user consent mechanisms.
  5. Regularly audit and update third-party libraries and tracking tools to mitigate vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Commune de Bernex
Description
Commune de Bernex
Key services
Municipal information and services
Content quality
basic
Branding
consistent

Technology

Stack
jQuery, Google Tag Manager
Frameworks
Nuxt.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
30/100

Analytics and tracking

Services
Google Tag Manager
Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
basic

Site quality

Design
basic
User experience
basic
Content relevance
basic
Navigation
basic
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. Website is a municipal government site for Commune de Bernex in Switzerland.
  2. Content is primarily informational with basic design and navigation.
  3. No privacy or cookie policies were found on the homepage HTML content.
  4. No contact emails or phone numbers explicitly found in the provided HTML snippet.
  5. Uses Nuxt.js framework and jQuery library; Google Tag Manager is present for analytics.
  6. No visible security headers or advanced security policies detected.
  7. No vulnerability disclosure or security.txt file found.
  8. No signs of WAF or content blocking; site is accessible.
  9. No adult or questionable content detected; content is safe for general audiences.
Technical notes

Notes

The website is built using Nuxt.js, a modern Vue.js framework, and includes jQuery for legacy support. Google Tag Manager is used for analytics and tracking. The site appears to have moderate performance and good mobile optimization. Accessibility features are basic, and SEO optimization is minimal but present through meta tags. Hosting details and CMS are not explicitly identified. The technical stack is modern but could benefit from enhanced security configurations and performance optimizations.
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 bernex.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 bernex.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.