Skip to main content

Security report for heineken.sk

Heineken · Retail · Slovakia

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

75/100

Risk levelMedium

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

Heineken's Slovakian website serves primarily as an age verification gateway, ensuring compliance with legal drinking age regulations before granting access to alcohol-related content. The site reflects the brand's global presence and commitment to responsible marketing. Technically, the site uses modern web standards with responsive design and Google Fonts integration, but lacks visible advanced frameworks or CMS indicators. Security posture is moderate; while HTTPS is implied, no explicit security headers or privacy policies are present on this page, which could be improved to enhance trust and compliance. The absence of WHOIS data limits domain legitimacy verification, but the strong brand presence and professional design mitigate concerns. Overall, the site is functional and professional but would benefit from enhanced privacy, security, and contact transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
65/ 100 · Medium
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

5 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. 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

      Third-party services without privacy policy

      Detected services: Google Analytics, Google APIs

      What to do: Document all third-party data sharing in your privacy policy

  3. 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.sk

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. 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
65
Average
75

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

Heineken operates as a global leader in the brewing industry, targeting adult consumers with its beer products. The Slovakian age gateway indicates localized compliance with alcohol regulations. The business model focuses on manufacturing and retail of alcoholic beverages, supported by strong brand marketing. The website's limited content on this page suggests a funnel approach to restrict underage access. No direct revenue streams or e-commerce functionalities are evident here. The company maintains consistent branding and targets mature audiences. Partnerships or subsidiaries are not disclosed on this page. The lack of contact or policy information on this gateway page suggests these are hosted elsewhere on the main site.

Security posture

The website demonstrates basic security measures such as age verification and HTTPS usage (inferred from canonical URL). However, the absence of security headers like Content Security Policy, X-Frame-Options, and HSTS reduces the overall security posture. No visible vulnerabilities or exposed sensitive data were detected in the provided content. The lack of privacy and cookie policies indicates potential compliance gaps with GDPR and other data protection regulations. Incident response contacts and vulnerability disclosure mechanisms are not present, limiting transparency and readiness. Enhancing these areas would improve security maturity and user trust.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies to ensure GDPR compliance.
  2. Add security headers such as Content Security Policy, HSTS, and X-Frame-Options to strengthen security posture.
  3. Provide clear contact information including security and incident response channels.
  4. Ensure WHOIS data is accurate and publicly available to improve domain trustworthiness.
  5. Conduct regular security audits and vulnerability assessments to maintain a robust security culture.
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 primarily an age verification gateway for the Slovakian market, indicating compliance with legal drinking age requirements.
Key services
Beer production, Brand marketing, Age verification for alcohol consumption
Content quality
good
Branding
consistent

Technology

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

Security

Observed score
50/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
good
Content relevance
basic
Navigation
basic
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is an age verification gateway for Heineken in Slovakia.
  2. No WHOIS data available from raw output; domain appears legitimate.
  3. No privacy, cookie, or terms of service policies detected on this page.
  4. No contact information or security policies found on this page.
  5. No analytics or advertising scripts detected in provided content.
  6. Site uses HTTPS (implied by canonical URL) but no explicit security headers found in data.
  7. Content is professionally designed and mobile optimized.
  8. No WAF or blocking detected; content fully accessible.
Technical notes

Notes

The website uses standard HTML5 and CSS3 with Google Fonts integration, indicating a modern but basic tech stack. No advanced JavaScript frameworks or CMS platforms were detected in the provided content. The site appears mobile optimized with responsive design elements. Performance is moderate given the use of external font loading and image assets. Accessibility features are basic, with room for improvement in ARIA roles and semantic markup. SEO optimization is minimal on this page, lacking meta descriptions and keywords. Hosting provider and infrastructure details are not discernible from the content. Overall, the technical implementation is solid for a gateway page but could be enhanced for full site sections.
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 heineken.sk. 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.sk.

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.