Skip to main content

Security report for bniuniversity.com

Schoox · Education · N/a

Medium risk. 3 critical or high findings in GDPR outside view and SSL/TLS.

Security score

71/100

Risk levelMedium

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

Schoox operates a sophisticated learning management system platform designed to empower organizations in training, engaging, and developing their workforce. The website analyzed is the login portal for the Schoox LMS, featuring a professional design and integration with Google OAuth for authentication. The platform targets organizational clients seeking scalable LMS solutions and positions itself as an established player in the education technology sector. Technically, the site leverages modern frameworks such as Angular and includes device fingerprinting for security and analytics purposes. The security posture is strong with HTTPS enforced and CSRF protections in place, though there is room for improvement in security headers and cookie consent mechanisms. Privacy policies and terms of service are clearly linked and appear comprehensive, supporting GDPR compliance. Overall, the site presents a moderate to high level of trustworthiness and professionalism, suitable for enterprise use.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
Checks completed
6of 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

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

    • 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. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching bniuniversity.com

This scan found 18 issues across 5 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
65
Security headers
65
Email security
70
Network security
100
GDPR outside view
53
Average
71

Not counted

  • DNS health: did not complete in this scan.
  • 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

Schoox's market positioning as a SaaS LMS provider focuses on medium-sized to large organizations requiring employee training and development tools. The business model revolves around subscription-based access to their platform, with key services including course management, employee engagement, and performance tracking. The company demonstrates consistent branding and provides clear legal and privacy documentation, enhancing credibility. The integration of mobile app links indicates a multi-platform approach. While direct contact details are not prominently displayed on the login page, a help widget facilitates user support. The absence of WHOIS data for the subdomain is typical for SaaS platforms using subdomains under a main corporate domain. No suspicious domains or partners were identified.

Security posture

The website enforces HTTPS and includes security best practices such as CSRF tokens and password input protections. The use of Google OAuth adds a layer of secure authentication. However, the absence of key security headers like Content-Security-Policy and X-Frame-Options reduces the overall security hardening. No vulnerabilities or exposed sensitive data were detected in the HTML content. The lack of a published security policy or incident response contact limits transparency in security governance. Device fingerprinting is used, which may raise privacy considerations but also enhances fraud detection. Overall, the security posture is solid but could be improved with additional headers and published security documentation.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  2. Add a cookie consent banner or mechanism to comply fully with GDPR and other privacy regulations.
  3. Publish a dedicated security policy and incident response contact information to improve transparency and user trust.
  4. Consider creating and hosting a security.txt file to facilitate vulnerability disclosures and responsible reporting.
  5. Enhance accessibility and mobile optimization to improve user experience across devices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Schoox
Description
Schoox is a powerful learning management system that helps organizations train, engage, and develop their employees.
Key services
Learning management system, Employee training, Engagement and development tools
Content quality
good
Branding
consistent

Technology

Stack
Angular 12.2.17, jQuery, MomentJS, FingerprintJS, Google OAuth, Web Components
Frameworks
Angular
Platforms
Web
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • CSRF token in login form
  • Password input with show/hide toggle
  • Google OAuth integration

Analytics and tracking

Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
FingerprintJS
Marketing tools
Google OAuth
Transparency
basic

Site quality

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

Key observations

  1. Website is a login portal for Schoox LMS platform
  2. Content is fully accessible with no blocking or WAF challenges
  3. No exposed sensitive data or credentials in HTML
  4. Use of modern JavaScript frameworks and libraries
  5. Presence of Google OAuth integration for authentication
  6. Privacy and terms policies are linked and accessible
  7. No explicit cookie consent mechanism detected
  8. No direct contact emails or phone numbers on login page
  9. Help widget present for user support
  10. No security.txt or vulnerability disclosure found
Technical notes

Notes

The site uses Angular 12.2.17 as its primary framework, supplemented by jQuery and MomentJS for date/time handling. Google OAuth integration is present for authentication, and FingerprintJS is used for device fingerprinting. The site loads multiple CSS and JS assets from Schoox's own CDN and asset domains, indicating a controlled hosting environment. Performance is moderate with no obvious blocking scripts or heavy assets. The site is mobile optimized to a basic degree but could benefit from improved responsiveness. Accessibility features are minimal but present. SEO optimization is basic with meta tags for title and description but no Open Graph or JSON-LD structured data detected. Overall, the technical implementation is modern but with room for enhancement in performance and SEO.
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 bniuniversity.com. 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 bniuniversity.com.

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.