Skip to main content

Security report for redbullscreeningroom.com

Red Bull · Media · N/a

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

70/100

Risk levelMedium

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

Red Bull Screening Room is a media platform operated by Red Bull GmbH, providing curated video content and streaming services related to the Red Bull brand and its associated sports and entertainment properties. The platform targets fans and consumers interested in lifestyle and extreme sports content, leveraging Red Bull's strong brand presence in the media industry. The website functions as a single page application with dynamic content loading and integrates multiple third-party technologies for analytics and user engagement. However, the technical infrastructure shows areas for improvement, particularly in SSL/TLS configuration and site performance, which currently impact security posture and user experience. The security setup includes strict SPF and DMARC email policies and HSTS, but lacks a valid SSL certificate and modern TLS support, which are critical for secure communications. Privacy compliance is well addressed with comprehensive policies and a cookie consent mechanism via OneTrust. Overall, the site demonstrates good business credibility and content quality but requires urgent security enhancements to meet modern standards and protect user data effectively.

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

  2. GDPR outside view

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

    • 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

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

Keep watching redbullscreeningroom.com

This scan found 17 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
97
Security headers
30
Email security
85
DNS health
85
Network security
100
GDPR outside view
25
Average
70

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

The website serves as a branded media distribution channel for Red Bull GmbH, focusing on video content delivery and brand engagement. Its market positioning leverages Red Bull's global recognition in sports and lifestyle sectors. The business model centers on content streaming and media product promotion, targeting a global audience interested in Red Bull's offerings. The platform integrates advanced analytics and marketing tools, indicating a mature digital marketing strategy. However, the lack of visible direct contact information and security policy details suggests a focus on brand presence over direct customer service. The partnership ecosystem includes official Red Bull policy domains and trusted third-party services for analytics and cookie management. Growth potential lies in improving technical performance and security to enhance user trust and engagement.

Security posture

The current security posture is moderate but with significant gaps. The presence of strict SPF and DMARC policies indicates good email security practices. HSTS is enabled, which is positive. However, the absence of a valid SSL certificate and lack of TLS protocol support severely undermine the site's security, exposing users to potential interception and man-in-the-middle attacks. No advanced security headers beyond HSTS are detected, and no incident response or vulnerability disclosure information is available. The site uses reputable third-party analytics and consent management tools, supporting privacy compliance. To improve, the site must implement valid HTTPS, enable modern TLS versions, and adopt additional security headers and best practices. Incident response readiness and vulnerability disclosure mechanisms should also be established to enhance security culture and resilience.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS and secure user communications.
  2. Enable TLS 1.2 or TLS 1.3 protocols and disable insecure protocols to improve encryption standards.
  3. Implement additional security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  4. Establish and publish a security policy and vulnerability disclosure program to improve transparency and incident response.
  5. Optimize website performance to reduce load times and improve user experience, including resource optimization and caching strategies.
Technical notes

Notes

The website is built as a single page application, likely using React, with integration of multiple JavaScript libraries including Video.js for media playback, Quill.js for rich text editing, and CodeMirror for code editing features. Analytics and marketing are managed via Google Tag Manager and Microsoft Clarity. The DNS setup uses Ultradns nameservers, indicating enterprise-grade DNS hosting. However, the SSL/TLS configuration is incomplete or invalid, with no supported TLS protocols and no certificate transparency compliance. The site has a large page size and high resource count, contributing to slow load times. Mobile optimization and accessibility are basic but functional. SEO meta tags and Open Graph tags are present but minimal. Hosting provider is not explicitly identified but likely uses CDN and enterprise DNS services. Overall, the technical stack is modern but requires improvements in security and performance to reduce technical debt and operational risks.
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 redbullscreeningroom.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 redbullscreeningroom.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.