Skip to main content

Security report for disneyprivacycenter.com

The Walt Disney Company · Media · United States

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

Security score

59/100

Risk levelMedium

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

The Walt Disney Company Privacy Center website serves as a comprehensive resource for privacy-related information, focusing on transparency and user control over personal data across its digital platforms. The site targets global consumers engaging with Disney's media and entertainment services, providing detailed privacy policies, cookie consent mechanisms, and information tailored for parents and children. The business is a large enterprise with a mature domain and strong brand presence, supported by multiple subsidiary brands such as ABC, ESPN, Marvel, and Hulu. Technically, the website is built on WordPress, leveraging technologies such as Apache, jQuery, Adobe Launch, and OneTrust for cookie consent management. Hosting is via Amazon CloudFront, indicating a scalable and reliable infrastructure. SEO and accessibility features are implemented at a good level, with comprehensive metadata and structured data enhancing search visibility. From a security perspective, the site suffers from a critical issue: the absence of a valid SSL certificate and lack of HTTPS support, severely impacting the security posture and user trust. While some security headers like HSTS are present, they are insufficiently configured. No explicit security policies or incident response contacts are published, and no vulnerability disclosure mechanisms are evident. Overall, the website is professionally designed and content-rich but requires urgent remediation of its SSL/TLS configuration to ensure secure communications and compliance with modern security standards. Strategic improvements in security transparency and incident response readiness would further enhance trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
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. 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 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 disneyprivacycenter.com

This scan found 18 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
50
Security headers
25
Email security
50
DNS health
85
Network security
100
GDPR outside view
43
Average
59

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 Walt Disney Company operates as a global media and entertainment conglomerate with a diversified portfolio of brands and services. The privacy center reflects a mature digital presence aligned with regulatory compliance and consumer trust initiatives. The business model centers on content delivery and user engagement across multiple platforms, supported by robust privacy and data protection frameworks. The company leverages partnerships and subsidiaries to extend its market reach and brand influence. Growth indicators include comprehensive privacy resources and multilingual support, indicating a global audience focus. The strategic use of third-party tools like OneTrust and Adobe Launch demonstrates integration with industry-standard privacy and marketing technologies.

Security posture

The current security posture is weak due to the lack of a valid SSL certificate and absence of HTTPS, exposing users to potential data interception risks. While some security best practices are partially implemented, such as HSTS headers and secure cookie attributes, the overall SSL/TLS configuration is inadequate. No published security policy or incident response contact information limits transparency and readiness. The absence of vulnerability disclosure channels further reduces the ability to manage security risks proactively. Compliance with GDPR is supported by comprehensive privacy policies and cookie consent mechanisms, but technical security gaps undermine full compliance and user trust.

Recommendations

  1. Immediately install and maintain a valid SSL/TLS certificate to enable HTTPS across the site.
  2. Enable and configure modern TLS protocols (TLS 1.2 and TLS 1.3) with strong cipher suites.
  3. Enhance HSTS policy by including subdomains and submitting for preload to browsers.
  4. Publish a clear security policy and incident response contact information on the website.
  5. Implement a vulnerability disclosure program or security.txt file to encourage responsible reporting.
Technical notes

Notes

The website is built on a WordPress CMS platform with Apache server hosting behind Amazon CloudFront CDN. It uses modern web technologies including jQuery, Adobe Launch for analytics and marketing, and OneTrust for cookie consent management. SEO is enhanced with Yoast SEO plugin and structured JSON-LD data. The site is mobile optimized with responsive design and basic accessibility features. However, the absence of a valid SSL certificate and disabled TLS protocols represent significant technical debt and security risk. Performance metrics are unavailable, but the use of CDN and optimized assets suggests moderate to good performance potential. Technical modernization should prioritize security infrastructure upgrades.
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 disneyprivacycenter.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 disneyprivacycenter.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.