Skip to main content

Security report for rumble.com

Rumble · Media · N/a

Partial score · DNS & email only

75/100

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

Rumble is a well-established video hosting and streaming platform founded in 1998, serving content creators and viewers seeking an alternative to mainstream video services. The platform offers video hosting, streaming, and monetization services, positioning itself as a media company with a focus on free speech and creator empowerment. Technically, the website is hosted on Amazon AWS infrastructure and uses modern web technologies including JavaScript and web fonts. Facebook Pixel is used for analytics and tracking, indicating moderate user tracking practices. Security posture is adequate with HTTPS enabled and domain transfer protections in place, but lacks DNSSEC and security headers, and does not publish security or privacy policies on the main page. The absence of privacy and cookie policies and contact information reduces privacy compliance and business transparency scores. Overall, the website is professional and functional but would benefit from enhanced privacy compliance and security disclosures.

Scanned

NIS2 and GDPR posture

GDPR outside view
70/ 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching rumble.com

This scan found 12 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
77
Email security
85
DNS health
85
Network security
100
GDPR outside view
70
Average
83
After the cap
75

Not counted

  • Security headers: 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

Rumble operates in the media sector as a video platform targeting content creators and viewers interested in alternative video hosting and monetization. Its business model revolves around providing video hosting and streaming services with monetization options for creators. The company has a long domain history consistent with its business age. The platform's market position is as an alternative to mainstream video platforms, emphasizing free speech. No explicit partnerships or subsidiaries were identified in the provided data. The website content is relevant and professionally presented, targeting a general audience interested in video content. The use of Facebook Pixel suggests a focus on marketing and user engagement analytics.

Security posture

The website uses HTTPS, ensuring encrypted communications. Domain registration includes clientTransferProhibited and clientUpdateProhibited statuses, which protect against unauthorized domain transfers and updates. However, DNSSEC is not enabled, which could expose the domain to DNS spoofing attacks. No security headers such as Content Security Policy, HSTS, or X-Frame-Options were detected in the provided data, which are recommended best practices to mitigate common web vulnerabilities. There is no evidence of published security policies, incident response contacts, or vulnerability disclosure programs, which limits transparency and readiness for security incidents. The use of Facebook Pixel introduces moderate user tracking, which should be disclosed in privacy policies. Overall, the security posture is moderate but could be improved by implementing security headers, DNSSEC, and publishing security-related policies.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Implement and configure security headers such as CSP, HSTS, and X-Frame-Options.
  3. Publish comprehensive privacy and cookie policies including GDPR compliance details.
  4. Provide clear contact information including security incident response contacts.
  5. Establish and publish a vulnerability disclosure policy and security.txt file to improve transparency and security culture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Rumble
Description
Rumble is a video platform offering video hosting and streaming services, targeting content creators and viewers seeking an alternative to mainstream video platforms.
Key services
Video hosting, Video streaming, Content monetization
Content quality
good
Branding
consistent

Technology

Stack
AWS DNS, Facebook Pixel, Inter font (WOFF2), JavaScript
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled

Analytics and tracking

Services
Facebook Pixel
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Facebook Pixel
Transparency
basic

Site quality

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

Key observations

  1. Website is accessible with full content.
  2. No explicit privacy, cookie, or terms of service policies found in the provided HTML.
  3. No contact emails or phone numbers explicitly found in the HTML content.
  4. Uses Facebook Pixel for tracking and analytics.
  5. Domain is old and registered with a reputable registrar.
  6. No security.txt or vulnerability disclosure information found.
  7. No explicit security policies or incident response contacts found.
  8. No evidence of adult or NSFW content.
  9. Website design and navigation are professional and user-friendly.
Technical notes

Notes

The website is built with modern web technologies including JavaScript and uses web fonts loaded via WOFF2 format for performance. Hosting is on Amazon AWS infrastructure, providing scalability and reliability. Facebook Pixel is integrated for analytics and marketing tracking. The site appears mobile-optimized with responsive design elements. Performance is moderate based on the use of external resources and scripts. Accessibility features are basic but present. SEO optimization is basic with canonical links and meta viewport tags. There is no detected CMS or framework explicitly identified. The site lacks DNSSEC and security headers, which are technical risks. Overall, the technical implementation is solid but has room for security and privacy enhancements.
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 rumble.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 rumble.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.