Skip to main content

Security report for mooj.fr

Mooj ! Le réseau Mobilités de Mauges Communauté · Transportation · France

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

Security score

51/100

Risk levelMedium

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

Mooj ! Le réseau Mobilités de Mauges Communauté is a regional public transportation service operated by the local community of Mauges Communauté in France. The website serves as an information portal for residents and commuters, offering details on regular bus lines, school transport, transport on demand, train connections, carpooling, and electric bike rental and purchase aid. The service is positioned as a key regional mobility provider, supporting sustainable and accessible transportation options for the community. Technically, the website is built on WordPress using the Divi theme, enhanced with plugins such as Yoast SEO, Matomo Analytics, and MailPoet for marketing. The site demonstrates good digital maturity with responsive design, accessibility features, and SEO optimization. Performance is moderate, with common libraries like jQuery and Slick Carousel used for UI components. From a security perspective, the site enforces HTTPS, implements standard security headers, and includes a cookie consent mechanism compliant with GDPR. No critical vulnerabilities or exposed sensitive data were detected. However, the site lacks a dedicated security policy page, vulnerability disclosure, and incident response contact information, which are recommended for enhanced trust and compliance. Overall, the website is professional, trustworthy, and well-aligned with its public service mission. The absence of WHOIS data due to privacy protection is not unusual for such entities and does not detract from the site's legitimacy. Strategic recommendations include publishing security policies and improving transparency around incident response to further strengthen security posture and user trust.

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

10 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

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

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

Keep watching mooj.fr

This scan found 29 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
52
Security headers
15
Email security
70
DNS health
45
Network security
100
GDPR outside view
25
Average
51

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

Mooj operates within the transportation sector as a public service entity under Mauges Communauté. Its competitive advantage lies in providing integrated mobility solutions tailored to the regional community, including diverse transport modes and support for sustainable alternatives like electric bikes and carpooling. The business model is community-funded and service-oriented, targeting residents, students, and commuters. The website reflects a medium-sized operation with a clear partnership ecosystem involving related community and regional sites. Growth indicators include active communication of service updates and integration with external route planning services. The partnership network enhances service reach and community engagement.

Security posture

The current security maturity level is good, with HTTPS enforced and multiple security headers implemented. The presence of a cookie consent mechanism and GDPR-compliant privacy policy indicates awareness of privacy regulations. No immediate vulnerabilities or security misconfigurations were found in the analyzed content. However, the absence of a published security policy, vulnerability disclosure program, and incident response contacts suggests room for improvement in transparency and preparedness. Compliance with GDPR is evident, but additional documentation and proactive communication would enhance security culture and incident readiness.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Implement a vulnerability disclosure program or security.txt file to facilitate responsible reporting.
  3. Provide clear incident response contact information to improve transparency and user confidence.
  4. Regularly audit and update third-party scripts and plugins to mitigate potential vulnerabilities.
  5. Enhance data retention and privacy documentation to align with evolving compliance requirements.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Mooj ! Le réseau Mobilités de Mauges Communauté
Description
Un service de de Mauges Communauté
Key services
Regular bus lines, School transport, Transport on demand (TAD), Train connections, Carpooling, Electric bike rental and purchase aid
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Divi Theme, jQuery, Slick Carousel, Matomo Analytics, MailPoet
Frameworks
Yoast SEO
Platforms
WordPress 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 in HTML
  • Use of security headers

Analytics and tracking

Services
Matomo, Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Marketing tools
MailPoet
Transparency
basic

Site quality

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

Key observations

  1. Website is a public transportation service portal for Mauges Communauté in France.
  2. Content is in French and well-structured with clear navigation.
  3. Uses WordPress CMS with Divi theme and common plugins.
  4. Includes cookie consent and privacy policy compliant with GDPR.
  5. Contact information is clearly provided including phone, email, and physical address.
  6. No WHOIS data available, likely due to privacy protection or registry restrictions.
  7. No signs of WAF or content blocking detected.
  8. No adult or explicit content detected; content is safe for general audiences.
  9. Social media presence on Facebook, Instagram, LinkedIn, and YouTube.
  10. Uses Matomo and Google Analytics for user tracking with moderate tracking level.
Technical notes

Notes

The website leverages a mature WordPress infrastructure with the Divi theme, supported by widely used JavaScript libraries such as jQuery and Slick Carousel for interactive elements. SEO is enhanced via Yoast SEO plugin, and analytics are managed through Matomo and Google Analytics, balancing user insights with privacy compliance. The site demonstrates good accessibility features and responsive design, ensuring usability across devices. Performance is moderate, with potential optimization opportunities in script loading and caching. Hosting details are not explicitly identified, but the presence of CDN resources suggests a distributed content delivery approach. Overall, the technical stack is stable and appropriate for the site's public service function.
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 mooj.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 mooj.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.