Skip to main content

Security report for youtube.com

Technology · Germany

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

Security score

78/100

Risk levelLow

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

The analyzed website is a consent management interface hosted on the subdomain consent.youtube.com, which is part of the YouTube platform owned by Google LLC. The page is designed to manage user consent for cookies and data processing, particularly in compliance with GDPR and other privacy regulations. The content is accessible and served over HTTPS, leveraging Google's robust infrastructure and modern web technologies. The page itself is minimalistic, focusing on consent UI elements without extensive business or contact information, which is typical for such functional subdomains. Technically, the site uses advanced JavaScript, Google APIs, and Material Design Components to provide a responsive and performant user experience. The hosting and platform are Google-managed, ensuring high availability and security. However, explicit privacy and cookie policies are not directly linked on this page, likely deferred to the main YouTube or Google privacy pages. From a security perspective, the site benefits from Google's strong security posture, including HTTPS enforcement and likely internal security headers and policies. No vulnerabilities or suspicious elements were detected in the content. The lack of explicit contact or incident response information on this subdomain is expected, as these are centralized on the main corporate sites. Overall, the site is legitimate, secure, and professionally maintained, serving a critical compliance function for YouTube users. Strategic recommendations include adding explicit links to privacy and cookie policies on the consent page for transparency and enhancing security headers for defense in depth.

Scanned

This is an earlier scan of youtube.com. View the latest report

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

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.

    • 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, Google Ads

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

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

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention youtube.com, from OffSeq Breach.

Total records
1,057,278
Employees
19
Customers
1,055,418
Third parties
1,841
Weak passwords
17%

Latest record dated 2026-06-12 · 560 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for youtube.com.

Select it in the checkout above.

Masked preview

  • –youtube.com2026-06-12
  • –youtube.com2026-05-25
  • –www.youtube.com2026-05-24
  • –www.youtube.com2026-05-21
  • –youtube.com2026-05-20

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Brand lookalikes

Add-on

Domains that imitate youtube.com and could be used for phishing or spoofed email, tracked in OffSeq Breach.

Tracked
240
Registered
240
Resolving
240
High or critical
0

Last checked 2026-06-19

Masked preview

  • yo•••••.comMediumreplacement
  • yo•••••.comMediumbitsquatting
  • yo•••••.comMediumbitsquatting

See the full lookalike list

A one-off add-on that lists up to 20 of the highest-risk lookalikes of youtube.com with registration, mail-server, certificate and DNS signals.

Select it in the checkout above.

Lookalike data refreshes continuously. Monitoring on Breach alerts you when a variant is registered, gains a mail server or starts serving HTTPS.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

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 subsidiary of Google LLC, operates as a leading global video-sharing platform with a vast user base. The consent.youtube.com subdomain serves as a compliance and user consent management tool, reflecting YouTube's commitment to privacy regulations such as GDPR. The business model is advertising-driven, supported by Google's extensive ad network and data analytics capabilities. The target audience includes global internet users accessing YouTube services, with localized compliance mechanisms for regions like Germany (indicated by 'gl=DE' in URL). YouTube's market position is dominant in online video streaming and content sharing, with strong brand recognition and integration within Google's ecosystem. The consent management page is part of a broader compliance and user trust strategy, essential for maintaining regulatory adherence and user confidence. Partnerships and integrations with Google services enhance operational efficiency and data governance.

Security posture

The security posture of the consent.youtube.com subdomain is robust, leveraging Google's enterprise-grade infrastructure. HTTPS is enforced, ensuring encrypted communications. While explicit security headers were not visible in the provided HTML snippet, Google's platforms typically implement comprehensive security controls including CSP, HSTS, and X-Frame-Options. No exposed sensitive data or vulnerable libraries were detected. The page does not expose contact information for incident response or security policies directly, which is standard for such functional subdomains. Incident response and security governance are centralized at the corporate level. The extensive use of Google APIs and tracking mechanisms indicates a mature data collection framework, balanced by compliance efforts. Recommendations include explicit security header implementation visibility and providing clear links to security and privacy resources to enhance user trust and transparency.

Recommendations

  1. Add explicit links to privacy and cookie policies on the consent management page to improve transparency and user trust.
  2. Implement and visibly confirm security headers such as HSTS, X-Frame-Options, and Content Security Policy for enhanced security posture.
  3. Provide accessible contact information or links to corporate security and incident response teams for improved compliance and user support.
  4. Regularly audit JavaScript libraries and tracking mechanisms to ensure no vulnerable or deprecated components are used.
  5. Enhance accessibility features and SEO metadata to improve user experience and regulatory compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
basic
Branding
consistent

Technology

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

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Content Security Policy (implied by Google)

Analytics and tracking

Services
Google Analytics (implied)
Tracking level
extensive
Privacy practices
basic

Advertising

Ad networks
Google DoubleClick
Tracking pixels
Google Ads tracking
Marketing tools
Google Ads
Transparency
good

Site quality

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

Key observations

  1. The page is a consent management interface for YouTube, served from a Google-owned domain.
  2. No WHOIS data for the subdomain as expected; main domain is well known and trusted.
  3. No contact information or privacy policy links explicitly found on this page; likely handled on main YouTube site.
  4. Page uses modern JavaScript and Google APIs for functionality.
  5. No signs of adult or unsafe content.
  6. No WAF or blocking detected; content fully accessible.
Technical notes

Notes

The website is built using modern JavaScript frameworks and Google APIs, including XMLHttpRequest and Beacon API for asynchronous data transmission. Material Design Components are used for UI consistency and responsiveness. The hosting is on Google's infrastructure, ensuring high performance and availability. The page is mobile-optimized and uses canonical links and viewport meta tags for SEO and usability. No CMS was detected as the site is a specialized functional subdomain. Performance is fast due to Google's CDN and optimized scripts. Accessibility is basic but present, with room for improvement. The technical implementation aligns with enterprise standards, minimizing technical debt and supporting scalability.
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

Earlier scans of this domain

  1. 81/100 +6Low22 findingsView report
  2. 75/100 −8Medium26 findingsView report
  3. 83/100 −2Low20 findingsView report
  4. 85/100 −1Low20 findingsView report
  5. 86/100Low19 findingsView report
  6. 86/100 +3Low19 findingsView report
  7. 83/100Low19 findingsView report
Reviews of this site

Share your experience with youtube.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 youtube.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.