Skip to main content

Security report for granges-paccot.ch

Commune Granges-Paccot · 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 website www.granges-paccot.ch serves as the official digital portal for the municipality of Granges-Paccot in Switzerland. It provides residents and visitors with comprehensive information about local government administration, community services, education, environment, transport, and events. The site supports eGovernment initiatives with online services such as a virtual counter for administrative procedures and access to municipal documents. The target audience primarily includes local residents and stakeholders interested in municipal affairs. Technically, the website is built on the i-web.ch CMS platform, utilizing modern web technologies including JavaScript modules and responsive CSS. The site is mobile-optimized and accessible, with a clear navigation structure and good SEO practices. Performance is moderate, with no critical technical issues detected. The site employs HTTPS and anonymized web statistics hosted in Switzerland, reflecting a commitment to privacy. From a security perspective, the website demonstrates a solid baseline with HTTPS encryption and secure form handling. However, it lacks explicit security policies, incident response contacts, and vulnerability disclosure mechanisms. No security headers were detected in the provided data, suggesting room for improvement in hardening the site against common web threats. No vulnerabilities or suspicious activities were identified. Overall, the website is a trustworthy and professional municipal portal with good content quality and user experience. The domain registration aligns with the municipal entity, reinforcing legitimacy. Strategic recommendations include enhancing security posture by adding security headers, publishing a security policy, and establishing incident response contacts to improve transparency and resilience.

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 granges-paccot.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. 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
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

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 granges-paccot.ch, from OffSeq Breach.

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

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 granges-paccot.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

Granges-Paccot's municipal website positions itself as a key information and service hub for local governance and community engagement. Its competitive advantage lies in providing integrated eGovernment services, including online administrative procedures and digital access to municipal resources. The business model is non-commercial, focused on public service delivery. Revenue streams are not applicable as it is a government entity. The target customer segments are local residents, businesses, and visitors seeking municipal information and services. Growth indicators include digital service adoption and community event promotion. The partnership ecosystem includes social media platforms and the i-web.ch CMS provider. Strategic observations highlight the municipality's commitment to digital transformation and community outreach through modern web presence.

Security posture

The website exhibits a moderate security maturity level with HTTPS enforced and anonymized analytics respecting privacy. The absence of advanced security headers and lack of published security policies or incident response information indicate gaps in formal security governance. No exposed sensitive data or vulnerable libraries were detected, which is positive. Compliance with GDPR is suggested by the presence of privacy and cookie policies with consent mechanisms. The site would benefit from establishing a vulnerability disclosure program and publishing a security.txt file to enhance transparency and readiness. Overall, the security posture is adequate for a municipal website but could be improved to meet higher standards and regulatory requirements.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Establish and publicize incident response contact channels (e.g., security@ or abuse@ email).
  4. Implement a vulnerability disclosure program and provide a security.txt file at the root domain.
  5. Regularly audit 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
Commune Granges-Paccot
Description
Official municipal website providing information and services related to the local government, community life, education, environment, finances, and events for the municipality of Granges-Paccot, Switzerland.
Key services
Online municipal services (virtual counter), Information on local administration, Community news and events, Education resources, Transport subsidies and parking permits, Waste management information, Energy programs
Content quality
good
Branding
consistent

Technology

Stack
JavaScript modules, CSS, SVG icons, i-web.ch 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
  • Use of secure forms with autocomplete off

Analytics and tracking

Services
stats.i-web.ch
Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a well-structured official municipal site for Granges-Paccot, Switzerland.
  2. Content is primarily in French with some German navigation elements.
  3. No signs of phishing, malware, or suspicious activity.
  4. Social media presence supports legitimacy and community engagement.
  5. No explicit privacy or security policy pages beyond basic privacy and cookie notices.
  6. No visible terms of service or incident response information.
Technical notes

Notes

The website is built on the i-web.ch CMS platform, leveraging modern JavaScript modules and responsive CSS for mobile optimization. The HTML structure is valid and includes meta tags for SEO and accessibility features such as ARIA labels and skip links. Performance is moderate, with no critical errors or broken elements detected. The site uses SVG icons and optimized images for visual quality. However, no advanced frameworks or hosting provider details were identified. The technical stack is sufficient for the site's purpose but could be enhanced with performance optimizations and security hardening measures.
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 granges-paccot.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 granges-paccot.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.