Skip to main content

Security report for carlsberg.com

Carlsberg Group · Manufacturing · Denmark

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

Security score

71/100

Risk levelMedium

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

Carlsberg Group is a globally recognized brewing company with a long history dating back to 1847. The website reflects a mature enterprise with a strong brand presence, focusing on beer production, sustainability, and innovation. The site targets adult consumers and stakeholders interested in the company's products and initiatives. Technically, the website employs modern web technologies including lazy loading, custom fonts, and Google Tag Manager for analytics, delivering a responsive and well-structured user experience. Security posture is strong with HTTPS enforced, security headers present, and an age verification gate to comply with alcohol regulations. Privacy compliance is well addressed with clear policies and cookie consent mechanisms. Overall, the website demonstrates high professionalism, trustworthiness, and business credibility.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 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 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 Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

This scan found 21 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
75
Security headers
15
Email security
85
DNS health
80
Network security
100
GDPR outside view
68
Average
71

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

Carlsberg holds a leading position in the global brewing industry, leveraging its heritage and innovation to maintain market relevance. The business model centers on manufacturing and marketing alcoholic beverages with a focus on sustainability and quality. The website's content and linked domains indicate a well-established partnership ecosystem and a comprehensive compliance framework. The target audience includes consumers, partners, and regulatory bodies. The company emphasizes transparency and responsible consumption, supported by detailed policy documentation and social media engagement.

Security posture

The website exhibits a mature security posture with enforced HTTPS, presence of key security headers, and no visible vulnerabilities or exposed sensitive data. The implementation of an age gate demonstrates regulatory compliance for alcohol-related content. However, the absence of explicit incident response contact information and vulnerability disclosure mechanisms suggests areas for improvement. The privacy and cookie policies are comprehensive and GDPR compliant, indicating a strong data protection culture. Overall, the security measures align well with industry best practices for a large enterprise.

Recommendations

  1. Publish explicit incident response and abuse contact information to enhance security transparency.
  2. Implement and publicize a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  3. Regularly audit third-party scripts and libraries to ensure no vulnerabilities are introduced.
  4. Enhance visibility of security policies and certifications to build user trust.
  5. Continue to monitor and update privacy compliance measures in line with evolving regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Carlsberg Group
Description
Probably The Best Beer In The World - We are always in pursuit of better. And not just better beer. We brew to create a better future for all of us.
Key services
Beer brewing, Sustainability initiatives, Brand marketing
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Google Tag Manager, Rellax.js (parallax), Lazy loading images/videos
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Age verification gate for alcohol content
  • Cookie consent mechanism implemented

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is professionally designed with strong branding.
  2. Comprehensive compliance and policy documentation is provided.
  3. Age verification is implemented to comply with alcohol regulations.
  4. Social media presence is clearly linked and consistent.
  5. No signs of blocking or WAF challenges detected.
  6. No exposed sensitive data or obvious vulnerabilities found.
Technical notes

Notes

The website uses a modern tech stack with asynchronous JavaScript loading, lazy loading of media assets, and custom web fonts to optimize performance and user experience. Google Tag Manager is used for analytics and marketing tracking. The site is mobile-optimized with responsive design and accessibility considerations. While the CMS and hosting provider are not explicitly identified, the technical implementation suggests a professionally managed infrastructure. Performance is moderate, with opportunities to further optimize media delivery and caching strategies. No critical technical debt or risks were identified from the provided data.
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 carlsberg.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 carlsberg.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.