Skip to main content

Security report for rhino.com

Rhino Entertainment · Media · N/a

Medium risk. 5 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

60/100

Risk levelMedium

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

Rhino Entertainment operates a comprehensive music entertainment website offering news, artist features, podcasts, playlists, and an e-commerce store for music products. The site is well-branded and targets music fans and collectors with a focus on classic and exclusive releases. Technically, the site is built on Drupal 10 with modern JavaScript libraries and integrates multiple analytics and marketing tools, demonstrating a mature digital infrastructure. Security-wise, the site uses HTTPS and implements cookie consent mechanisms, though there is room for improvement in security headers and explicit security policies. Overall, the website presents a professional and trustworthy front with extensive user tracking balanced by privacy compliance measures.

Scanned

NIS2 and GDPR posture

GDPR outside view
63/ 100 · Medium
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

5 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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 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
    • 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 rhino.com

This scan found 16 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
0
Security headers
25
Email security
85
DNS health
85
Network security
100
GDPR outside view
63
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

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 positions Rhino as a key player in the music media and e-commerce sector, leveraging its brand to promote artists and sell exclusive music products. The business model combines content marketing with direct sales, supported by a broad ecosystem of analytics and advertising partners. The presence of multiple social media channels and a dedicated customer support platform indicates a well-established customer engagement strategy. The site’s content and marketing tools suggest a focus on growth and audience retention within the music fan community.

Security posture

The site demonstrates a good security posture with mandatory HTTPS and a comprehensive cookie consent framework. No sensitive data exposure or obvious vulnerabilities were detected in the HTML content. However, the absence of explicit security headers and incident response information suggests opportunities to enhance security maturity. The extensive use of third-party scripts requires ongoing monitoring to mitigate supply chain risks. Overall, the security measures are adequate but could be strengthened with additional policies and technical controls.

Recommendations

  1. Implement security headers such as Content Security Policy (CSP), X-Frame-Options, and Strict-Transport-Security (HSTS) to enhance protection against common web attacks.
  2. Publish a dedicated security policy and incident response contact information to improve transparency and readiness.
  3. Regularly audit and update third-party scripts and tracking pixels to minimize vulnerability exposure.
  4. Enhance accessibility features to improve compliance and user experience for all visitors.
  5. Consider adding data retention policies and clearer disclosures regarding analytics data handling.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Rhino Entertainment
Description
Rhino is a media company focused on music entertainment, offering news, artist information, playlists, podcasts, and a store for music products including exclusive and special edition releases.
Key services
Music news and features, Artist information and promotion, Music playlists and podcasts, E-commerce store for music products
Content quality
good
Branding
consistent

Technology

Stack
Drupal 10, jQuery 3.3.1, Owl Carousel, Adobe Launch (Adobe DTM), YouTube Iframe API, OneTrust Cookie Consent, Various analytics and marketing pixels
Frameworks
Drupal
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • Use of HTTPS (canonical and og:url use https)
  • Cookie consent mechanism implemented
  • No exposed sensitive data found in HTML

Analytics and tracking

Services
Adobe Analytics, Google Analytics, Facebook Pixel, Twitter Pixel, Pinterest Pixel, LinkedIn Pixel, Hotjar, Snapchat Pixel, Reddit Pixel, Quantcast
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Google AdWords, DoubleClick, The Trade Desk, SpringServe, Media Math, Verizon Media, Audigent, WebFX
Tracking pixels
Facebook Pixel, Twitter Pixel, Pinterest Pixel, LinkedIn Pixel, Hotjar, Snapchat Pixel, Reddit Pixel, Quantcast
Marketing tools
Adobe Launch, OneTrust Cookie Consent, Adobe Analytics
Transparency
good

Site quality

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

Key observations

  1. Website is a professionally maintained music entertainment and e-commerce platform
  2. Comprehensive cookie and privacy policies with user consent mechanisms are implemented
  3. Extensive use of third-party analytics and marketing pixels for user tracking and advertising
  4. No signs of WAF or content blocking; full content is accessible
  5. No exposed sensitive information or security vulnerabilities detected in the HTML content
  6. Use of modern web technologies and frameworks including Drupal 10 and various JavaScript libraries
  7. Social media presence is clearly linked and consistent with brand identity
  8. Multiple forms for newsletter sign-up with validation and consent checkboxes
  9. Strong branding consistency and professional design throughout the site
Technical notes

Notes

The website uses Drupal 10 as its CMS, supported by jQuery and Owl Carousel for UI components. It integrates Adobe Launch for tag management and multiple analytics and advertising pixels including Google Analytics, Facebook Pixel, Twitter, LinkedIn, and others. The site is mobile-optimized with responsive design and includes accessibility considerations such as skip links. Performance appears moderate with asynchronous script loading. The technical stack is modern and well-integrated, though some legacy scripts and multiple versions of Bootstrap CSS are included, which could be optimized.
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 rhino.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 rhino.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.