Skip to main content

Security report for grandreims.fr

Communauté urbaine du Grand Reims · Government · France

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

Security score

67/100

Risk levelMedium

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

The website www.grandreims.fr serves as the official digital presence of the Communauté urbaine du Grand Reims, a large regional government entity in France. It provides comprehensive information and services related to community news, urban planning, environment, business development, and mobility for residents, businesses, and visitors. The site is well-structured, professionally designed, and targets a broad audience within the Grand Reims territory. Technically, it is built on TYPO3 CMS with modern JavaScript libraries and includes GDPR-compliant cookie consent mechanisms. Security posture is strong with HTTPS, security headers, and no visible vulnerabilities. However, WHOIS data is unavailable, which slightly impacts trust but is mitigated by the official nature and content quality of the site.

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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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

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

Keep watching grandreims.fr

This scan found 23 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
15
Email security
80
DNS health
85
Network security
100
GDPR outside view
68
Average
67

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

Grand Reims positions itself as a key government service provider for a large community of 143 communes. Its business model is public service oriented, focusing on delivering information and facilitating access to community services. The website supports local economic development through dedicated business sections and partnerships. The presence on multiple social media platforms enhances community engagement. The lack of WHOIS data is unusual but likely due to privacy or registry update issues rather than malicious intent. The site’s comprehensive content and official branding indicate a mature digital presence with strong community ties.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, multiple security headers, and a cookie consent framework aligned with GDPR. No exposed sensitive data or vulnerable libraries were detected. The absence of a published security policy or incident response contact is a minor gap. No vulnerability disclosure or security.txt file was found, which could improve transparency. Overall, the site is secure for its purpose but could enhance trust by publishing explicit security and incident response information.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and user data protection.
  2. Provide clear incident response contact details to facilitate reporting of security issues.
  3. Implement and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  4. Regularly review and update third-party scripts and libraries to mitigate potential vulnerabilities.
  5. Enhance transparency by detailing data retention policies and cookie usage in the privacy policy.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Communauté urbaine du Grand Reims
Description
Site officiel de la Communauté urbaine du Grand Reims fournissant des informations sur la communauté urbaine et ses 143 communes.
Key services
Community news and events, Public services information, Urban planning and environment, Business development support, Mobility and transport information
Content quality
good
Branding
consistent

Technology

Stack
jQuery, TYPO3 CMS, Photoswipe, Tarteaucitron (cookie consent), Matomo Tag Manager
Frameworks
TYPO3 CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • No exposed sensitive data detected
  • Use of security headers

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
matomo
Marketing tools
Matomo Tag Manager, Tarteaucitron
Transparency
good

Site quality

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

Key observations

  1. Official regional government website for Grand Reims community
  2. Comprehensive content covering community services, environment, business, and mobility
  3. Strong presence on major social media platforms
  4. Uses TYPO3 CMS and modern web technologies
  5. Implements GDPR-compliant cookie consent via Tarteaucitron
  6. No signs of malicious or suspicious content
  7. WHOIS data unavailable, but no negative indicators from website content
Technical notes

Notes

The website uses TYPO3 CMS, a robust and widely used content management system, supported by jQuery and Photoswipe for UI enhancements. It integrates Matomo Tag Manager for analytics and Tarteaucitron for cookie consent management, reflecting compliance with privacy regulations. The site is mobile-optimized with good accessibility features and SEO practices. Performance is moderate, likely due to the extensive content and media. Hosting details are not explicit but the site uses HTTPS with good SSL configuration. The technical stack is modern and appropriate for a government community portal, with opportunities to improve performance and security transparency.
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 grandreims.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 grandreims.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.