Skip to main content

Security report for cls.fr

CLS (Collecte Localisation Satellites) · Energy · France

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

Security score

67/100

Risk levelMedium

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

CLS (Collecte Localisation Satellites) is a large multinational company founded in 1986, specializing in satellite data collection and Earth observation services. The company operates globally with 35 sites and focuses on environmental monitoring, maritime security, sustainable fisheries, mobility, and energy infrastructure. CLS leverages advanced technologies such as data science, AI, and machine learning to provide actionable insights to governments, environmental agencies, and industry sectors. The website reflects a mature digital presence with professional design, comprehensive content, and multilingual support. Technically, the website is built on WordPress using the Divi theme and incorporates modern JavaScript libraries like Swiper.js and GSAP. It employs HTTPS with good SSL configuration and uses hCaptcha for form security. The site includes detailed privacy and cookie policies with consent mechanisms, indicating good privacy compliance. Analytics are implemented via Google Tag Manager with moderate user tracking. From a security perspective, the site shows good practices such as HTTPS enforcement and CAPTCHA usage but lacks explicit security headers like Content-Security-Policy and X-Frame-Options. No vulnerabilities or exposed sensitive data were detected in the HTML content. The absence of WHOIS data limits domain legitimacy verification, but the professional web presence and certifications support trustworthiness. Overall, CLS presents a strong business and technical profile with good security posture and privacy compliance. The main risk is the lack of publicly available WHOIS data, which should be further investigated to confirm domain registration legitimacy.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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. GDPR outside view

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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 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, Twitter, LinkedIn, YouTube, Google APIs

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

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

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

Keep watching cls.fr

This scan found 22 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
77
Security headers
65
Email security
65
DNS health
70
Network security
100
GDPR outside view
25
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

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 cls.fr, from OffSeq Breach.

Total records
1,284
Employees
2
Customers
1,267
Third parties
15
Weak passwords
24%

Latest record dated 2025-10-17 · 74 subdomains affected

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 cls.fr.

Select it in the checkout above.

Masked preview

  • –jira-projects.cls.fr2025-10-17
  • –owa.cls.fr2025-10-17

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

CLS holds a strong market position as a pioneer in satellite-based Earth observation and environmental monitoring. Its business model is B2B, serving governmental and industrial clients with satellite data and digital platforms. The company benefits from its parentage by CNES and CNP, enhancing credibility and access to space technologies. CLS's growth is supported by acquisitions (e.g., Ground Control) and a broad portfolio of solutions addressing climate, maritime security, and energy sectors. The company’s global footprint and certifications indicate operational maturity and compliance. Partnerships with specialized platforms further extend its service ecosystem.

Security posture

The website demonstrates a mature security posture with HTTPS, CAPTCHA protection on forms, and no visible sensitive data leaks. However, it lacks some recommended HTTP security headers, which could improve defense against clickjacking and MIME sniffing attacks. No public incident response or security policy pages were found, which could be enhanced to improve transparency and readiness. The use of third-party plugins and scripts appears controlled, but ongoing vulnerability management is advised. Privacy policies and cookie consent mechanisms align well with GDPR requirements, indicating good compliance culture.

Recommendations

  1. Implement and enforce Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options HTTP headers to strengthen security.
  2. Publish a dedicated security policy and incident response page to improve transparency and preparedness.
  3. Regularly audit and update third-party plugins and scripts to mitigate potential vulnerabilities.
  4. Enhance accessibility features to improve compliance and user experience for all users.
  5. Investigate and verify domain WHOIS information to confirm registration legitimacy and reduce trust concerns.

Contact details published on the site

Addresses
Legal name
CLS (Collecte Localisation Satellites)
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
CLS (Collecte Localisation Satellites)
Description
CLS est une société multinationale innovante qui oeuvre pour la Terre depuis l'espace, fournissant des solutions spatiales pour étudier, protéger la Planète et gérer durablement ses ressources.
Key services
Satellite data collection and processing, Environmental and climate monitoring, Sustainable fisheries management, Maritime security, Mobility and connectivity solutions, Energy and infrastructure monitoring, Digital platform services
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, Divi Theme, jQuery, Swiper.js, Tippy.js, GSAP, Popup Maker, Contact Form 7, hCaptcha
Frameworks
WordPress CMS
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of hCaptcha for forms
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
Axeptio (consent management)
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and multimedia
  2. Professional and consistent branding throughout
  3. Strong focus on environmental and satellite data services
  4. Multiple language support (French and English)
  5. Use of modern web technologies and CMS
  6. Presence of detailed privacy, cookie, and terms policies
  7. Contact information clearly provided with physical address and phone
  8. No signs of adult or questionable content
  9. No visible security policy or incident response page
  10. WHOIS data unavailable, limiting domain trust verification
Technical notes

Notes

The website is built on WordPress with the Divi theme, leveraging modern JavaScript libraries such as Swiper.js for sliders, GSAP for animations, and Tippy.js for tooltips. It uses hCaptcha for bot protection and Google Tag Manager for analytics and marketing tags. The site is mobile-optimized with responsive design and good SEO practices including meta tags and structured data (JSON-LD). Performance is moderate, with potential improvements in caching and resource optimization. Accessibility is basic but could be enhanced. The technical stack is standard for corporate websites, providing a balance of functionality and maintainability.
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 cls.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 cls.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.