Skip to main content

Security report for bee-secure.lu

BEE SECURE · Government · Luxembourg

Medium risk. 8 critical or high findings in GDPR outside view, DNS health and 1 other check.

Security score

60/100

Risk levelMedium

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

BEE SECURE is a government-backed digital safety awareness platform based in Luxembourg, focused on educating children, youth, parents, and educators about responsible and safe use of digital technologies. The platform offers a variety of services including awareness campaigns, a helpline, a stopline for reporting illegal content, educational resources, and youth consultations. It is co-financed by the European Union and operated in partnership with national agencies such as the police and justice departments. The website is professionally designed, content-rich, and well-structured primarily in French, targeting a broad audience concerned with digital safety. Technically, the website is built on WordPress, utilizing modern web technologies such as jQuery and FontAwesome, and employs Matomo analytics hosted locally in Luxembourg to ensure privacy compliance. The site demonstrates good mobile optimization, accessibility, and SEO practices. Security posture is strong with HTTPS enforced and cookie consent mechanisms in place, although there is room for improvement in publishing explicit security policies and incident response information. From a security perspective, no critical vulnerabilities or exposed sensitive data were detected. The use of Matomo analytics with local hosting aligns with GDPR compliance. However, the absence of WHOIS data due to a malformed query reduces domain transparency and trust from a registration standpoint. Overall, the platform appears legitimate and trustworthy based on content and government affiliations. Strategically, BEE SECURE should focus on enhancing domain registration transparency, publishing security and incident response policies, and maintaining rigorous audits of third-party scripts to sustain and improve its 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

8 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. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • Critical

      DNS Resolution Failed

      Unable to resolve domain A records

      What to do: Verify domain is properly configured and not expired

  3. 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 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 bee-secure.lu

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
95
Security headers
30
Email security
75
DNS health
35
Network security
100
GDPR outside view
25
Average
60

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 bee-secure.lu, from OffSeq Breach.

Total records
4
Employees
0
Customers
4
Third parties
0
Weak passwords
0%

1 subdomain 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 bee-secure.lu.

Select it in the checkout above.

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

BEE SECURE occupies a unique position as a government-supported initiative dedicated to digital safety awareness in Luxembourg. Its competitive advantage lies in official backing, EU co-financing, and partnerships with key national institutions, which enhance credibility and reach. The business model is non-commercial, focusing on public education and support services. Revenue streams are likely government and EU funding. Target customers include children, youth, parents, educators, and the general public. Growth indicators include active event scheduling, new publications, and expanding interactive tools. The partnership ecosystem includes national police, justice, and youth services, reinforcing its authoritative role. Operationally, the platform leverages WordPress for content management and Matomo for privacy-conscious analytics, reflecting a mature digital infrastructure.

Security posture

The security maturity of BEE SECURE is moderate to high. The website enforces HTTPS and uses a cookie consent mechanism that allows users to control tracking scripts, demonstrating compliance with GDPR. Analytics are handled via Matomo hosted within Luxembourg, avoiding third-party data transfers. No security.txt or vulnerability disclosure policies are published, which is a gap in transparency and incident readiness. No direct contact channels for security incidents were found. The absence of security headers in the HTML source is a minor concern. Overall, the platform shows a good security culture but would benefit from formalizing security policies and incident response procedures to enhance trust and preparedness.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and user data protection.
  2. Implement and publicly disclose a vulnerability disclosure program or security.txt file.
  3. Provide clear incident response contact information for security issues.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Regularly audit and update third-party scripts and plugins to mitigate vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
BEE SECURE
Description
BEE SECURE vise à sensibiliser le grand public à une utilisation plus sûre et responsable des technologies numériques, et à renforcer en particulier les enfants, les jeunes et leur entourage (parents, enseignants, éducateurs et autres) par des offres ciblées.
Key services
Awareness campaigns, Helpline for digital safety, Stopline for reporting illegal content, Educational resources and training, Youth consultations
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, jQuery, Matomo Analytics, FontAwesome
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with granular settings
  • Matomo analytics hosted locally in Luxembourg
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Transparency
good

Site quality

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

Key observations

  1. Website is a government-backed digital safety awareness platform
  2. Content is comprehensive and well-structured in French
  3. Strong focus on children and youth digital safety education
  4. Includes multiple interactive tools, publications, and events
  5. Good privacy and cookie compliance with user consent mechanisms
  6. No direct contact emails or phone numbers found on main page; contact via form
  7. No visible security.txt or vulnerability disclosure
  8. WHOIS data unavailable, which is a concern for domain transparency
Technical notes

Notes

The website is built on a WordPress CMS platform with jQuery and FontAwesome libraries for UI components and icons. It uses Matomo analytics hosted on a partner domain within Luxembourg, ensuring data privacy compliance. The site is mobile-optimized with responsive design and good accessibility features. Performance is moderate, with no major issues detected in the HTML structure or CSS. The presence of cookie consent and privacy settings indicates attention to user privacy. However, the hosting provider is not explicitly identified, and no advanced frameworks or platforms beyond WordPress are detected. The site could improve by implementing modern security headers and enhancing WHOIS domain 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 bee-secure.lu. 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 bee-secure.lu.

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.