Skip to main content

Security report for leifheit.com

Leifheit · Retail · Germany

Partial score · DNS & email only

50/100

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

Leifheit is a well-established German retail company specializing in household and kitchen products, with a strong brand presence and a history of over 65 years. The website serves as an e-commerce platform built on Shopware 6, offering a wide range of products including cleaning tools, laundry drying solutions, and kitchen utensils. The site is professionally designed with good navigation, mobile optimization, and rich multimedia content, targeting household consumers seeking quality products. Technically, the site uses modern JavaScript libraries and integrates marketing and analytics tools such as Bazaarvoice, Klaviyo, and Google Tag Manager. However, a critical security gap exists as the website currently lacks a valid SSL/TLS certificate and does not enforce HTTPS, exposing users to potential risks. Security headers are partially implemented, but the absence of HTTPS severely impacts the overall security posture. Privacy and cookie policies are present and include consent mechanisms, indicating compliance with GDPR requirements. Contact information is available via a contact page, though no explicit emails or phone numbers are embedded in the HTML content. The domain registration and DNS records are consistent with the company's German origin and business claims, supporting legitimacy. Strategic recommendations include immediate implementation of HTTPS, enhancement of security policies, and improved incident response readiness to strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
15/ 100 · Critical
Checks completed
6of 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. 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

    • 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, YouTube

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

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

This scan found 10 issues across 5 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
Email security
50
DNS health
85
Network security
100
GDPR outside view
15
Average
50

Not counted

  • Security headers: did not complete in this scan.
  • 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

Leifheit operates in the retail sector with a focus on household and kitchen products. The company leverages its long-standing brand reputation and German quality control as competitive advantages. The business model centers on direct e-commerce sales supported by a comprehensive product catalog and customer service. The target market includes consumers looking for durable and functional household solutions. The website integrates multiple marketing and analytics tools to support customer engagement and sales optimization. Partnerships with entities like e-point.pl suggest collaboration for technical or hosting services. The company maintains a consistent brand image and offers extended warranties, reinforcing customer trust. Growth indicators include a diverse product range and active social media presence. No suspicious business patterns or inconsistencies were detected.

Security posture

The website demonstrates a basic security posture with some security headers implemented, such as X-Frame-Options and Referrer-Policy. However, the absence of a valid SSL/TLS certificate and lack of HTTPS enforcement represent critical vulnerabilities that expose users to data interception and man-in-the-middle attacks. There is no evidence of advanced security policies, incident response plans, or vulnerability disclosure mechanisms. The use of third-party marketing and analytics scripts introduces potential privacy considerations, though cookie consent mechanisms are in place. Overall, the security maturity is low, and immediate remediation is required to protect user data and maintain compliance with security standards.

Recommendations

  1. Implement a valid SSL/TLS certificate and enforce HTTPS site-wide immediately.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  3. Establish and publish a formal security policy and incident response plan accessible on the website.
  4. Introduce a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Review and audit third-party scripts for security and privacy compliance regularly.
Technical notes

Notes

The website is built on the Shopware 6 e-commerce platform, utilizing modern frontend technologies including Swiper.js for sliders and Bazaarvoice for reviews. It integrates Cookiebot for cookie consent management and Google Tag Manager for analytics and marketing tags. Hosting appears to be via Fastly CDN with Varnish caching, enhancing performance and availability. Despite these modern technologies, the lack of HTTPS and SSL/TLS support is a significant technical risk. Performance metrics were not available, but the site shows good mobile optimization and accessibility features. The technical stack is modern but requires urgent security upgrades to align with best practices and regulatory requirements.
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 leifheit.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 leifheit.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.