Skip to main content

Security report for brandhunters.cz

YouTube / Google · Technology · United States

Low risk. 4 critical or high findings in GDPR outside view and SSL/TLS.

Security score

82/100

Risk levelLow

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

This website is a consent management interface for YouTube, a service owned by Google LLC. It is designed to handle user consent for cookies and data processing, particularly targeting users in Germany as indicated by the 'gl=DE' parameter. The page is part of the broader YouTube and Google ecosystem, reflecting a mature and enterprise-level digital infrastructure. The business model revolves around advertising and content delivery, with user data consent as a critical compliance component. Technically, the site employs modern JavaScript frameworks and Google-hosted services, ensuring fast performance and good mobile optimization. Security is robust, with HTTPS enforced and multiple security headers present, reflecting Google's high standards. However, explicit privacy and cookie policy links are not present on this specific page, likely centralized on main domains. Overall, the site is trustworthy, secure, and professionally maintained, with no indications of adult or unsafe content.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 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

4 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 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 Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

    • High

      Third-party services without privacy policy

      Detected services: YouTube, Google APIs

      What to do: Document all third-party data sharing in your privacy policy

  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 brandhunters.cz

This scan found 13 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
75
Security headers
90
Email security
85
DNS health
90
Network security
100
GDPR outside view
50
Average
82

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

YouTube, as a market leader in online video sharing and streaming, operates on an advertising-driven business model that requires strict compliance with privacy regulations such as GDPR. This consent page is a critical touchpoint for managing user permissions and data privacy, ensuring legal compliance and user trust. The platform targets a global audience, with localization for specific regions like Germany. Google's extensive infrastructure supports this service, providing scalability and reliability. The lack of direct contact information or detailed business disclosures on this page is consistent with its function as a technical consent interface rather than a corporate landing page. The business ecosystem includes partnerships with various Google services and advertising networks, reinforcing its dominant market position.

Security posture

The security posture of this consent page is strong, leveraging HTTPS, Content Security Policy, and other security headers to protect user data and prevent common web vulnerabilities. The use of Google infrastructure and APIs further enhances security and reliability. No vulnerabilities or exposed sensitive data were detected in the page content. The absence of explicit security or incident response policies on this page is typical, as such information is usually centralized on corporate or main service domains. The site demonstrates adherence to best practices in secure web development and data protection, supporting compliance with GDPR and other regulations.

Recommendations

  1. Add explicit links to privacy policy and cookie policy on the consent page for improved transparency and user trust.
  2. Include contact information or links to support for privacy and security inquiries to enhance compliance and user confidence.
  3. Regularly audit third-party scripts and tracking technologies to ensure they comply with privacy standards.
  4. Maintain and update security headers and SSL configurations to stay ahead of emerging threats.
  5. Consider implementing a security.txt file or vulnerability disclosure policy to facilitate responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
YouTube / Google
Description
Consent management page for YouTube, part of Google services, handling user consent for cookies and data processing.
Key services
User consent management, Cookie and privacy settings, Access control to YouTube content
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Google APIs, XMLHttpRequest, Beacon API
Frameworks
Material Design Components (MDC)
Platforms
Web
Performance
fast
Mobile
good
Accessibility
good
SEO
basic

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Content Security Policy implemented
  • No exposed sensitive data in HTML
  • Secure cookie consent mechanism

Analytics and tracking

Services
Google Analytics
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Google Ads
Marketing tools
Google Marketing Platform
Transparency
good

Site quality

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

Key observations

  1. The page is a consent management interface for YouTube users, primarily targeting German users (gl=DE).
  2. No WHOIS data for the subdomain, which is expected for subdomains.
  3. No contact information or privacy policy links explicitly found on this page; likely handled on main YouTube or Google domains.
  4. The page uses modern JavaScript and Google infrastructure.
  5. No signs of adult or unsafe content.
  6. No WAF or blocking detected; content fully accessible.
  7. Strong security posture with HTTPS and security headers.
  8. Extensive use of Google tracking and analytics technologies.
Technical notes

Notes

The website is built using modern JavaScript and Google-hosted APIs, with Material Design Components for UI consistency. Performance is optimized with asynchronous script loading and use of browser APIs like Beacon. The site is mobile-optimized and accessible, with semantic HTML and ARIA roles implied by MDC usage. SEO is basic but sufficient for a consent page. Hosting on Google Cloud ensures high availability and scalability. No CMS detected, as this is a specialized consent interface. The technical implementation reflects a mature, enterprise-grade infrastructure with minimal technical debt.
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 brandhunters.cz. 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 brandhunters.cz.

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.