Skip to main content

Security report for disney.com

The Walt Disney Company · Media · United States

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

Security score

57/100

Risk levelMedium

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

The website disney.com is the official domain of The Walt Disney Company, a leading global media and entertainment conglomerate. The company operates in multiple sectors including film production, theme parks, and media networks, serving a broad audience worldwide. However, the website content is currently inaccessible due to a security mechanism likely implemented by Akamai, resulting in an 'Access Denied' page. This prevents direct analysis of the site's content, policies, and user experience. From a technical perspective, the domain is hosted behind Akamai's infrastructure, but the SSL/TLS configuration is severely lacking with no valid certificate and no HTTPS support detected. This represents a critical security gap. DNS and mail configurations appear consistent with a large enterprise. The WHOIS data confirms legitimate ownership by The Walt Disney Company with no privacy protection, consistent domain age, and trustworthy registration details. Security posture is weak due to missing HTTPS, lack of modern TLS protocols, and absence of security headers. No privacy or cookie policies were found on the accessible page, and no contact or incident response information is available. The site is blocked by a WAF or similar security control, limiting the ability to assess content quality, SEO, or analytics usage. Overall, the site shows high business credibility based on domain ownership and WHOIS data but scores very low on content accessibility and security configuration. Strategic recommendations include immediate remediation of SSL/TLS issues, enabling HTTPS, and reviewing WAF rules to allow legitimate access for analysis and users.

Scanned

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

NIS2 and GDPR posture

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

6 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 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';…

  2. 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 Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

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

Keep watching disney.com

This scan found 17 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
15
Email security
50
DNS health
85
Network security
100
GDPR outside view
40
Average
57

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 disney.com, from OffSeq Breach.

Total records
73,523
Employees
1,409
Customers
55,080
Third parties
17,034
Weak passwords
6%

Latest record dated 2026-06-18 · 479 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 disney.com.

Select it in the checkout above.

Masked preview

  • –login.myid.disney.com2026-06-18
  • –outlooksts.disney.com2026-06-18
  • –login.myid.disney.com2026-06-18
  • –outlooksts.disney.com2026-06-17
  • –outlooksts.disney.com2026-06-17

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)

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 holds a dominant position in the global media and entertainment industry, leveraging a diversified business model that includes content creation, theme parks, and media networks. The disney.com domain is a critical digital asset for brand presence and customer engagement. The company benefits from strong brand recognition and a broad target audience including families and entertainment consumers worldwide. Subsidiaries such as Pixar, Marvel, and Lucasfilm enhance its content portfolio. The domain's DNS and mail infrastructure reflect enterprise-grade configurations. However, the current website access restrictions limit digital engagement and analysis of online business operations. Disney's revenue streams are likely supported by multiple digital channels, but the blocked site content restricts visibility into these aspects.

Security posture

The security posture of disney.com is currently inadequate due to the absence of a valid SSL certificate and lack of HTTPS support, which are fundamental for secure communications. The site is protected by a WAF or similar security mechanism, which effectively blocks unauthorized access but also prevents legitimate content analysis. No modern TLS protocols or security headers are enabled, increasing exposure to potential attacks if HTTPS were enabled improperly. There is no evidence of privacy compliance mechanisms or incident response contacts on the accessible page. While DNS and mail configurations are robust, the lack of SSL/TLS and security headers represents a critical vulnerability. The security culture appears focused on perimeter defense but lacks transparency and user-facing security best practices.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the site.
  2. Enable modern TLS protocols (TLS 1.2 or TLS 1.3) and disable all insecure protocols.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Review and adjust WAF/security rules to allow legitimate user and analyst access without compromising security.
  6. Publish clear privacy, cookie, and terms of service policies accessible to users.
  7. Provide visible contact information and incident response channels for security and abuse reporting.
  8. Conduct regular security audits and vulnerability assessments to maintain a strong security posture.
  9. Improve website accessibility and performance once content access is restored.
  10. Enhance transparency around data protection and compliance with GDPR and other regulations.
Technical notes

Notes

The technical infrastructure for disney.com is hosted on Akamai's platform, indicating use of a major CDN and security provider. DNS records are well configured with multiple authoritative name servers and enterprise-grade mail exchange servers. However, the SSL/TLS configuration is critically deficient with no valid certificate and no enabled TLS protocols, resulting in no HTTPS support. The HTTP headers indicate minimal security controls and no advanced security headers. Performance data is unavailable due to blocked content, but the presence of Akamai suggests potential for high performance and scalability. No CMS or frameworks could be detected from the limited HTML. The site is currently inaccessible due to WAF or security blocking, which limits further technical assessment. Modernization opportunities include enabling HTTPS, improving security headers, and enhancing content delivery and accessibility.
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. 69/100Medium29 findingsView report
Reviews of this site

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