Skip to main content

Security report for beiersdorf.com

Beiersdorf AG · Manufacturing · Germany

Medium risk. 4 critical or high findings in GDPR outside view and SSL/TLS.

Security score

56/100

Risk levelMedium

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

Beiersdorf AG is a globally recognized skin care company with a rich history dating back to 1882. The company operates in the manufacturing and retail sectors, offering a portfolio of trusted brands such as NIVEA, Eucerin, and Hansaplast. The website reflects a mature digital presence with comprehensive content targeting consumers, investors, and job seekers. It provides detailed information on sustainability, research, corporate governance, and career opportunities, positioning Beiersdorf as a market leader in skin care products. Technically, the website is built on a custom ASP.NET CMS hosted on Microsoft Azure, utilizing modern front-end frameworks like UIkit and integrating Google Tag Manager for analytics and a Consent Manager for privacy compliance. The site is mobile-optimized with good SEO practices and clear navigation, although performance metrics are not provided. From a security perspective, the site has significant weaknesses, notably the absence of a valid SSL certificate and lack of TLS protocol support, which critically undermines secure communications. While security headers and cookie flags are implemented, the SSL misconfiguration is a major risk. Privacy compliance is strong, with clear privacy and cookie policies and a consent mechanism in place. Incident response contact information is publicly available, enhancing trust. Overall, the website is professional and trustworthy in content and business representation but requires urgent security improvements to protect user data and maintain compliance. Strategic recommendations include immediate SSL certificate installation, enabling modern TLS protocols, and enhancing security header configurations to improve the security posture and user trust.

Scanned

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

4 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 Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • 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

  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

Need hands-on remediation? Email guard@offseq.com

Keep watching beiersdorf.com

This scan found 13 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
75
Email security
50
DNS health
90
Network security
100
GDPR outside view
18
Average
56

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

Beiersdorf AG holds a strong market position as a leading manufacturer and retailer of skin care products with a global footprint. Its business model focuses on innovation in skin biology and epigenetics, sustainability initiatives, and maintaining investor confidence through transparent reporting. The company targets a broad audience including consumers, investors, and potential employees. The website's detailed sections on corporate governance, compliance, and sustainability reflect a mature organizational structure and commitment to ethical business practices. Partnerships with brands like 8x4, Hidrofugal, and tesa expand its portfolio and market reach. The company demonstrates growth potential through investments in research and new campus facilities, signaling ongoing innovation and operational expansion.

Security posture

The current security posture of the website is weak due to the lack of a valid SSL certificate and absence of TLS protocol support, exposing users to potential data interception and man-in-the-middle attacks. Although security headers such as HSTS, X-Content-Type-Options, and Content-Security-Policy are present, HSTS is not effectively enabled, and the CSP allows unsafe-inline and unsafe-eval, which could be improved. Cookies are set with Secure and HttpOnly flags, which is positive. The DNS CAA records are malformed, which could affect certificate issuance security. No known vulnerabilities like Heartbleed or POODLE are detected. Incident response mechanisms and security contact emails are clearly provided, indicating readiness for security incident handling. Immediate remediation of SSL/TLS issues is critical to elevate the security posture.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate supporting TLS 1.2 and TLS 1.3 protocols.
  2. Enable and enforce HSTS with includeSubDomains and preload directives to ensure HTTPS usage.
  3. Correct malformed CAA DNS records to properly restrict certificate authorities.
  4. Enhance Content Security Policy to remove unsafe-inline and unsafe-eval directives.
  5. Implement OCSP stapling and session resumption to improve security and performance.
  6. Regularly audit and update security headers and cookie settings.
  7. Maintain and publicize clear incident response and vulnerability disclosure policies.
  8. Continue to monitor privacy compliance and update consent mechanisms as regulations evolve.
  9. Improve accessibility features to enhance user experience for all users.
  10. Conduct periodic penetration testing and vulnerability assessments.
Technical notes

Notes

The website is built on a custom ASP.NET CMS hosted on Microsoft Azure, leveraging UIkit for front-end styling and Google Tag Manager for analytics. The presence of a Consent Manager indicates attention to privacy compliance. The site is mobile responsive with good navigation and SEO metadata. However, performance data is missing, making it difficult to assess load times and resource optimization. The lack of a valid SSL certificate and disabled TLS protocols represent significant technical debt and risk. DNS records are mostly well configured except for malformed CAA entries. The site uses modern JavaScript and CSS frameworks but could benefit from enhanced accessibility and performance optimizations. Overall, the technical infrastructure supports a professional web presence but requires urgent security upgrades.
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 beiersdorf.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 beiersdorf.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.