Skip to main content

Security report for plainecommune.fr

Plaine Commune Grand Paris · Government · France

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

Security score

58/100

Risk levelMedium

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

Plaine Commune Grand Paris is a public territorial establishment serving a large population in the northern Paris region. The website provides comprehensive information about the institution's services, projects, and community engagement. It targets residents, local businesses, and public stakeholders with a focus on urban development, culture, mobility, and environmental initiatives. The digital infrastructure is built on TYPO3 CMS with modern JavaScript libraries, ensuring a responsive and user-friendly experience. Security measures include HTTPS, RSA encryption for login forms, and a GDPR-compliant cookie consent mechanism. However, formal security policies and incident response contacts are not publicly available, representing an area for improvement. Overall, the website demonstrates a strong commitment to transparency, accessibility, and user engagement, positioning it as a trustworthy government portal.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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 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

  4. Network security

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

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • 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

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

Keep watching plainecommune.fr

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
62
Security headers
40
Email security
75
DNS health
80
Network security
20
GDPR outside view
68
Average
58

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 well-established government entity with a clear mandate in urban and community development. Its market position is regional government authority with a large user base. The business model is public service provision funded by government budgets. Key competitive advantages include official status, comprehensive service offerings, and strong digital presence including social media integration. The partnership ecosystem includes related official sites for economic development and media libraries. Growth indicators are visible in ongoing projects and community engagement initiatives. The website supports multiple communication channels including contact forms, phone, and social media, enhancing stakeholder interaction.

Security posture

The website maintains a good security posture with HTTPS enforced and RSA encryption for user authentication. Cookie consent is managed via a robust mechanism allowing granular user control, supporting GDPR compliance. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. However, the absence of published security policies, incident response procedures, and security headers suggests room for maturity improvement. The use of third-party scripts like Facebook Pixel and Matomo Analytics is transparent and consent-based. Overall, the security posture is adequate for a public government website but could benefit from formalized policies and enhanced HTTP security headers.

Recommendations

  1. Publish a formal security policy and incident response plan accessible on the website.
  2. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Provide explicit contact channels for security incidents (e.g., security@ or abuse@ email addresses).
  4. Regularly review and update third-party scripts to mitigate potential vulnerabilities.
  5. Enhance accessibility features to meet higher standards and improve user experience for all audiences.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Plaine Commune Grand Paris
Description
Plaine Commune Grand Paris is a public territorial establishment grouping 8 cities and 1 delegated commune in the northern Paris area, serving approximately 450,000 inhabitants. It focuses on urban development, culture, mobility, environment, and public services.
Key services
Urban planning and development, Public mobility and transport projects, Waste management, Cultural and community services, Economic development support, Public information and communication
Content quality
good
Branding
consistent

Technology

Stack
TYPO3 CMS, jQuery, Bootstrap, Leaflet, Swiper, Fancybox, Matomo Analytics, Tarteaucitron (cookie consent)
Frameworks
TYPO3 CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with granular controls
  • RSA encryption for login form password field
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Facebook Pixel
Marketing tools
Facebook Pixel, Matomo Analytics
Transparency
good

Site quality

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

Key observations

  1. Website is a public government portal for Plaine Commune Grand Paris.
  2. Content is in French and targeted at local residents and businesses.
  3. Uses modern CMS TYPO3 with various JavaScript libraries.
  4. Has a cookie consent mechanism compliant with GDPR.
  5. Includes social media integration with official accounts.
  6. No signs of malicious or suspicious content.
  7. No explicit security policy or incident response info published.
  8. Good contact information and multiple communication channels.
  9. No terms of service page explicitly found.
  10. No vulnerability disclosure or security.txt found.
Technical notes

Notes

The website is built on TYPO3 CMS, a mature and extensible content management system, supported by modern JavaScript libraries including jQuery, Bootstrap, Leaflet for maps, and Swiper for sliders. The site uses Matomo for analytics, ensuring privacy-friendly tracking. Performance is moderate with good mobile optimization and basic accessibility features. The hosting provider is ECRITEL, a reputable French hosting company. The site includes a cookie consent mechanism compliant with GDPR. Technical debt appears low, but opportunities exist to improve security headers and accessibility compliance. Overall, the technical infrastructure supports the business needs effectively with room for modernization in security and accessibility.
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 plainecommune.fr. 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 plainecommune.fr.

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.