Skip to main content

Security report for lemans.org

Automobile Club de l'Ouest (ACO) · Transportation · France

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

Security score

72/100

Risk levelMedium

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

The Automobile Club de l'Ouest (ACO) is a well-established French motorsport organization founded in 1906, best known for creating and organizing the prestigious 24 Hours of Le Mans endurance race. The website serves as the official portal for the ACO, providing information about the club, its history, membership benefits, and event details. The site targets motorsport enthusiasts, club members, and the general public interested in endurance racing. The business model revolves around event organization, membership services, and motorsport promotion. Technically, the website is built on modern frameworks such as Next.js and React, hosted likely on Google Cloud Platform, and integrates consent management via Didomi, reflecting a mature digital infrastructure. Security posture is good with HTTPS and consent mechanisms, though explicit security headers and policies are not evident. The absence of WHOIS data limits domain trust analysis, but the website content and branding strongly indicate legitimacy. Overall, the site is professional, GDPR-aware, and serves its audience effectively.

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

6 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 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, LinkedIn, Cloudflare, Google APIs

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching lemans.org

This scan found 21 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
80
DNS health
85
Network security
100
GDPR outside view
35
Average
72

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

ACO holds a leading position in the endurance motorsport sector, leveraging its century-long heritage and large membership base. Its competitive advantage lies in organizing one of the world's most famous motorsport events and offering exclusive member benefits. Revenue streams likely include event ticket sales, memberships, merchandising, and corporate partnerships. The target customer segments include motorsport fans, automotive enthusiasts, and corporate clients for events and driving schools. The partnership ecosystem includes related domains like club.lemans.org for membership management. Growth indicators include ongoing innovation programs like MissionH24 for hydrogen racing. Strategic observations highlight the importance of digital modernization and enhanced security transparency to maintain trust and compliance.

Security posture

The website demonstrates a moderate to good security maturity level with enforced HTTPS and a robust consent management platform (Didomi) for GDPR compliance. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. However, the lack of explicit security headers (CSP, HSTS, etc.) and absence of published security policies or incident response contacts indicate areas for improvement. There is no evidence of a vulnerability disclosure program or security.txt file, which could enhance transparency and incident handling readiness. Compliance with GDPR is supported by consent mechanisms but lacks visible privacy policy documentation in the provided content. Overall, the security posture is adequate but could benefit from formalized policies and enhanced header configurations.

Recommendations

  1. Implement and publish comprehensive privacy and security policies accessible from the website footer.
  2. Add standard security headers such as Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options to improve security posture.
  3. Establish a vulnerability disclosure program and publish a security.txt file to facilitate responsible reporting.
  4. Enhance accessibility and navigation clarity to improve user experience, especially for mobile users.
  5. Regularly audit third-party scripts and tracking tools to ensure compliance and minimize privacy risks.

Contact details published on the site

Addresses
Legal name
Automobile Club de l'Ouest
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Automobile Club de l'Ouest (ACO)
Description
Site officiel de l'Automobile Club de l'Ouest (A.C.O), créateur et organisateur des 24 Heures du Mans. L’ACO est un club de plus de 40 000 membres passionnés auto-moto, organisateur d’épreuves automobiles majeures, notamment les 24 Heures du Mans.
Key services
Organization of 24 Hours of Le Mans and other motorsport events, Membership club with exclusive benefits, Motorsport heritage and museum, Driving schools and corporate events
Content quality
good
Branding
consistent

Technology

Stack
Next.js, React, Google Tag Manager, Didomi Consent Management, Typekit Fonts, Cloud Storage (Google Cloud Storage)
Frameworks
Next.js
Platforms
Google Cloud Platform
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Consent management implemented (Didomi)
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Didomi Consent SDK
Marketing tools
Didomi Consent Management
Transparency
good

Site quality

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

Key observations

  1. Website shows an application error message but main content and consent banner are present.
  2. No WHOIS data available, limiting domain trust analysis.
  3. Consent management is implemented with Didomi, indicating GDPR awareness.
  4. No explicit privacy policy or terms of service pages detected in provided content.
  5. Contact information is available via structured data with phone and email.
  6. Website uses modern web technologies and cloud hosting.
  7. No security.txt or vulnerability disclosure found.
  8. No signs of WAF or blocking mechanisms.
  9. Content is safe and appropriate for general audiences.
Technical notes

Notes

The website uses a modern React-based framework (Next.js) with server-side rendering capabilities, hosted on Google Cloud infrastructure. It integrates third-party services including Google Tag Manager for analytics and Didomi for consent management, indicating a focus on privacy compliance. Fonts are served via Adobe Typekit. The site loads multiple CSS and JS assets asynchronously to optimize performance, though some client-side errors are indicated by the 'Application error' message in the HTML, which may affect user experience. Mobile optimization is good, but accessibility features are basic and could be improved. SEO is supported by proper meta tags and structured data (JSON-LD) describing the organization and contact details. Overall, the technical infrastructure is solid but requires attention to error handling and accessibility enhancements.
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 lemans.org. 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 lemans.org.

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.