Skip to main content

Security report for heineken.com

Heineken · Retail · N/a

Low risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

78/100

Risk levelLow

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

Heineken is a globally recognized brewing company with a strong brand presence. The analyzed webpage serves as an age verification gateway to ensure compliance with legal drinking age regulations before granting access to the main site. The website demonstrates consistent branding and a professional design focused on user compliance and legal adherence. Technically, the site uses modern web standards and fonts but lacks advanced SEO and accessibility features. Security posture is moderate, with no explicit security headers or policies detected, and privacy compliance is limited due to absence of privacy and cookie policies. Overall, the site is legitimate and trustworthy but would benefit from enhanced security and privacy disclosures.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 100 · Low
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

3 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 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. 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 heineken.com

This scan found 16 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
62
Security headers
50
Email security
85
DNS health
85
Network security
100
GDPR outside view
88
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 heineken.com, from OffSeq Breach.

Total records
7,635
Employees
18
Customers
6,192
Third parties
1,425
Weak passwords
27%

Latest record dated 2026-05-15 · 125 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 heineken.com.

Select it in the checkout above.

Masked preview

  • –careersubwaymap.heineken.com2026-05-15
  • –innovationchallenge.heineken.com2026-05-13
  • –globalbrandsportal.heineken.com2026-05-12
  • –careersubwaymap.heineken.com2026-04-21
  • –innovationchallenge.heineken.com2025-09-19

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

Heineken operates in the retail sector of alcoholic beverages, targeting adult consumers worldwide. The business model centers on manufacturing and marketing beer products with a strong emphasis on brand recognition and legal compliance. The website's age verification mechanism reflects regulatory adherence and responsible marketing practices. The company maintains a large enterprise scale with a global footprint. While the site lacks detailed business contact information or certifications, the brand's market position and trust indicators are strong. There is no evidence of partnerships or subsidiaries from the provided data.

Security posture

The website enforces age verification as a key security and compliance measure. However, it lacks visible security headers such as Content Security Policy, HSTS, or X-Frame-Options, which are recommended best practices. No incident response or vulnerability disclosure information is present. The absence of privacy and cookie policies indicates potential compliance gaps with GDPR and other privacy regulations. No analytics or tracking scripts were detected, suggesting minimal user tracking. Overall, the security posture is moderate but could be improved by implementing standard security headers, explicit privacy disclosures, and incident response contacts.

Recommendations

  1. Implement comprehensive privacy and cookie policies with clear consent mechanisms to improve GDPR compliance.
  2. Add security headers including Content Security Policy, HSTS, and X-Frame-Options to enhance protection against common web attacks.
  3. Publish vulnerability disclosure and incident response information to build trust and facilitate security communication.
  4. Provide clear contact information for privacy and security inquiries to improve transparency and user trust.
  5. Conduct regular security audits and update WHOIS information to ensure domain registration transparency and legitimacy.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Heineken
Description
Heineken is a global brewing company known for its beer products. The website content is focused on age verification gateway for access to the main site, indicating compliance with legal drinking age requirements.
Key services
Beer production, Brand marketing, Age verification for legal compliance
Content quality
basic
Branding
consistent

Technology

Stack
Google Fonts, Icomoon icon font, CSS3, HTML5
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • Age verification form to restrict underage access

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is an age verification gateway for Heineken's global site.
  2. No WHOIS data available from raw output; domain appears registered and active.
  3. No privacy, cookie, or terms of service policies found in the provided content.
  4. No contact emails, phone numbers, or physical addresses found in the content.
  5. No security headers or explicit security policies detected in the HTML content.
  6. No analytics or tracking scripts explicitly detected in the provided HTML snippet.
  7. Content is professionally branded and consistent with Heineken's corporate identity.
  8. Site targets adults with alcohol-related content, enforcing age verification.
  9. No WAF or blocking mechanisms detected; content is accessible.
  10. Technical implementation is modern but lacks advanced SEO and accessibility features.
Technical notes

Notes

The website uses modern HTML5 and CSS3 standards with Google Fonts and custom icon fonts for branding. The design is responsive and optimized for mobile devices. However, the site lacks advanced SEO meta tags and structured data beyond basic Open Graph tags. No CMS or hosting provider information is evident from the HTML. Performance appears moderate with no explicit indicators of optimization or caching. Accessibility features are basic, with room for improvement in semantic markup and ARIA attributes. The technical infrastructure supports the business goal of age verification but could be enhanced for better SEO, accessibility, and security.
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. 76/100Low20 findingsView report
Reviews of this site

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