Skip to main content

Security report for ilevia.fr

ilévia · Transportation · France

Medium risk. 7 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

ilévia operates as the primary public transportation provider for the Métropole Européenne de Lille, offering comprehensive bus, metro, tram, and bike-sharing services. The website serves residents and visitors with route planning, schedules, ticketing, and news about local events, positioning ilévia as a key mobility facilitator in the region. The digital presence is modern, leveraging Next.js and React frameworks, ensuring a responsive and accessible user experience. Security posture is strong with HTTPS, security headers, and script nonce usage, though the absence of WHOIS data and explicit security policies slightly reduce transparency. Overall, ilévia's website reflects a professional, trustworthy, and user-centric platform supporting urban mobility.

Scanned

NIS2 and GDPR posture

GDPR outside view
10/ 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

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

  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

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

Keep watching ilevia.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. 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
82
Security headers
75
Email security
70
DNS health
65
Network security
100
GDPR outside view
10
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

ilévia holds a significant market position as the main transit operator in Lille, supported by a large infrastructure including metro, tram, bus, and bike-sharing networks. The business model focuses on public service transportation with revenue streams from ticket sales, subscriptions, and partnerships. The company targets a broad audience including daily commuters, tourists, and event attendees. The website integrates with partner domains and social media to enhance engagement. Growth indicators include service expansions and event promotions. Strategic partnerships with local authorities and cultural institutions strengthen its ecosystem.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, comprehensive security headers, and modern web development practices. No exposed sensitive data or vulnerable libraries were detected. However, the lack of a public security policy, incident response contact, or vulnerability disclosure mechanism indicates room for improvement in transparency and incident readiness. The missing WHOIS data is a concern for domain legitimacy verification but does not directly impact website security. Overall, the security measures are robust but could benefit from enhanced communication and formal policies.

Recommendations

  1. Publish a clear security policy and incident response contact information on the website.
  2. Implement and publicize a security.txt file to facilitate vulnerability reporting.
  3. Monitor and update third-party libraries regularly to mitigate potential vulnerabilities.
  4. Enhance transparency by ensuring WHOIS data is publicly available or justified by privacy policies.
  5. Maintain and improve accessibility and privacy compliance to meet evolving regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
ilévia
Description
Retrouvez tous les services bus, métro, tram et V'Lille de la Métropole Européenne de Lille : itinéraires conseillés, horaires aux arrêts ainsi que de nombreuses actualités.
Key services
Bus services, Metro services, Tram services, V'Lille bike sharing, Ticketing and subscriptions, Transport on reservation, Park and Ride facilities
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, Google Tag Manager, Normalize.css, Web fonts (TTF), Image optimization via Next.js, JavaScript ES6+
Frameworks
Next.js, React
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of nonce attributes in scripts
  • Content Security Policy implemented
  • No outdated or vulnerable libraries detected

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
basic

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 no blocking detected.
  2. Strong branding and consistent user experience.
  3. Comprehensive information on transportation services and local events.
  4. Use of modern web technologies and frameworks.
  5. Good privacy and cookie policy presence with consent mechanisms.
  6. No direct contact emails or phone numbers found in the provided HTML snippet; likely available on contact page.
  7. WHOIS data missing, which is a transparency concern but not necessarily malicious.
  8. Social media presence is strong and linked to official platforms.
  9. No security.txt or explicit vulnerability disclosure found.
  10. No explicit security policy or incident response contact found.
Technical notes

Notes

The website is built on a modern React and Next.js stack, utilizing server-side rendering and optimized asset delivery for performance. It employs Google Tag Manager for analytics and tracking, and uses normalized CSS for consistent styling. The site is mobile-optimized with responsive design and accessibility features such as skip links and ARIA roles. The absence of CMS-specific footprints suggests a custom or proprietary content management system. Performance is fast with preloading and efficient script loading. Technical risks are minimal but include dependency on third-party scripts and the need for continuous security updates.
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 ilevia.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 ilevia.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.