Skip to main content

Security report for kelloggcompany.com

Kellanova · Retail · United States

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

Security score

43/100

Risk levelHigh

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

Kellanova is a global leader in the food manufacturing sector, specializing in snacking, cereals, noodles, and plant-based foods with a strong portfolio of iconic brands. The company targets consumers worldwide, investors, and potential employees, operating at an enterprise scale with a mature domain presence of over 22 years. The website reflects a professional and consistent brand image with comprehensive content and clear navigation. Technically, the site leverages modern frameworks such as Bootstrap and Adobe Experience Manager, supported by Akamai CDN and integrated with marketing and privacy tools like Google Tag Manager and OneTrust. However, a critical security gap exists due to the absence of a valid SSL/TLS certificate, resulting in no HTTPS support, which significantly impacts the security posture and user trust. Privacy compliance is well addressed with clear privacy and cookie policies and consent mechanisms. The WHOIS data confirms strong domain registration practices and legitimacy. Overall, while the business and content aspects are strong, the lack of HTTPS is a major risk that should be remediated promptly.

Scanned

NIS2 and GDPR posture

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

8 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

    • 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

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

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

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

Kellanova holds a strong market position as a global food manufacturer with a diversified product portfolio and a clear focus on sustainability and equity. The business model centers on manufacturing and retailing food products with a global footprint. The company is undergoing acquisition by Mars, Incorporated, indicating strategic growth and consolidation. The website supports multiple stakeholder groups including consumers, investors, and job seekers, with dedicated subdomains and partner sites for news, careers, and investor relations. The digital presence is mature and professionally managed, with strong domain protection and consistent branding. The partnership ecosystem includes multiple branded domains and regional sites, enhancing market reach and customer engagement.

Security posture

The security posture of the website is currently weak due to the absence of a valid SSL/TLS certificate and lack of HTTPS support, exposing users to potential interception and man-in-the-middle attacks. While the site implements some security headers such as HSTS, it is not fully effective without HTTPS. No DNSSEC or CAA records are enabled, which could improve domain security. There is no evidence of a vulnerability disclosure program or security policy pages, which limits transparency and incident response readiness. The use of modern privacy tools like OneTrust indicates awareness of compliance requirements, but the critical lack of HTTPS undermines overall security. Immediate remediation of SSL/TLS and enhancement of security policies is recommended.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across all domains and subdomains.
  2. Enable DNSSEC and CAA records to strengthen domain security and certificate issuance control.
  3. Publish a dedicated security policy and vulnerability disclosure page to improve transparency and incident response.
  4. Enhance session management with OCSP stapling and session resumption mechanisms.
  5. Continue leveraging privacy compliance tools and ensure all contact channels for security incidents are clearly published.
Technical notes

Notes

The website is built on Adobe Experience Manager CMS with Bootstrap 5.3 and jQuery libraries, indicating a modern and scalable technical foundation. It uses Akamai CDN for content delivery and Adobe Launch for tag management, integrated with Google Tag Manager and OneTrust for analytics and privacy compliance. The site is mobile optimized with responsive design and includes accessibility features, though these could be improved. Performance data was not available, but the use of CDN and modern frameworks suggests moderate to good performance. The absence of SSL/TLS is a significant technical risk. Overall, the infrastructure is robust but requires security upgrades to meet best practices.
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 kelloggcompany.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 kelloggcompany.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.