Skip to main content

Security report for mondelezinternational.com

Mondelēz International, Inc · Retail · United States

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

Security score

50/100

Risk levelMedium

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

Mondelēz International, Inc is a leading global manufacturer and retailer of snack foods, including chocolate, biscuits, gum, candy, and beverages. The company maintains a mature and well-established online presence with a comprehensive website that highlights its brand portfolio, sustainability initiatives, investor relations, and career opportunities. The website is built using modern technologies such as Gatsby and React, hosted on Google Cloud infrastructure, and features a professional design with clear navigation and mobile optimization. However, the site lacks a valid SSL certificate and does not serve content over HTTPS, which is a critical security issue. Despite this, the site includes privacy and cookie policies with consent mechanisms, indicating a good level of privacy compliance. The absence of explicit security and incident response policies suggests room for improvement in security transparency. Overall, the website reflects a large enterprise with strong business credibility but requires urgent security enhancements to protect user data and improve trust.

Scanned

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

NIS2 and GDPR posture

GDPR outside view
18/ 100 · Critical
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

7 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 mondelezinternational.com

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

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

Total records
14,085
Employees
2
Customers
13
Third parties
14,070
Weak passwords
0%

Latest record dated 2025-09-07 · 4 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 mondelezinternational.com.

Select it in the checkout above.

Masked preview

  • –mondelezinternational.com2025-09-07
  • –mondelezinternational.com2025-08-28

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

Mondelēz International operates in the retail sector, focusing on snack foods with a diverse brand portfolio including well-known names like Cadbury, Oreo, and Toblerone. The company targets a broad audience including consumers, investors, suppliers, and job seekers. Its business model centers on manufacturing and distributing snack products globally, supported by sustainability and ESG initiatives prominently featured on the site. The company demonstrates strong market positioning as a mature, enterprise-level organization with a consistent brand image and multiple trust indicators such as investor relations and social media presence. Partnerships with organizations like Cocoa Life and SnackFutures enhance its sustainability and innovation credentials. The website content is rich, relevant, and professionally presented, supporting the company's market leadership and growth strategies.

Security posture

The current security posture of the website is weak due to the absence of a valid SSL certificate and lack of HTTPS support, exposing users to potential data interception risks. No modern TLS protocols are enabled, and critical security headers such as HSTS are missing. The site does not implement OCSP stapling or session resumption mechanisms, which are important for secure and efficient SSL/TLS operations. No explicit security policies or incident response contacts are found, indicating limited transparency and preparedness for security incidents. While no known vulnerabilities or malware are detected, the lack of basic security controls significantly lowers the security score and poses a risk to user trust and data protection.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Enable modern TLS protocols (TLS 1.2 and 1.3) and disable outdated or insecure versions.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options to enforce secure connections.
  4. Enable OCSP stapling to improve certificate revocation checking and reduce latency.
  5. Implement session resumption mechanisms such as session tickets or session caches for performance and security.
  6. Publish explicit security and incident response policies, including dedicated contact channels for security issues.
  7. Regularly audit and update third-party libraries and scripts to avoid vulnerabilities.
  8. Enhance privacy compliance by clearly stating data retention policies and user rights.
  9. Improve accessibility features to meet or exceed standards for all users.
  10. Maintain consistent branding and update content regularly to reflect current business activities.
Technical notes

Notes

The website is built on a modern tech stack using Gatsby and React, indicating a focus on performance and scalability. It leverages external libraries such as jQuery and js-cookie for enhanced functionality. Hosting is provided by Google Cloud, as indicated by IP addresses and HTTP headers. The site includes preconnect hints to optimize resource loading from various domains including Google Analytics and YouTube. However, performance data is incomplete, with no load time or resource counts available, suggesting potential monitoring gaps. The site is mobile optimized with responsive design and accessibility features, but lacks HTTPS which is a critical technical deficiency. SEO optimization is good with proper meta tags and structured navigation. Overall, the technical infrastructure is modern but requires security improvements and performance monitoring enhancements.
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. 71/100 +26Medium28 findingsView report
  2. 45/100High28 findingsView report
Reviews of this site

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