Skip to main content

Security report for ludwig-reiter.com

Ludwig Reiter Schuhmanufaktur GmbH · Retail · Austria

Medium risk. 5 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

53/100

Risk levelMedium

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

Ludwig Reiter Schuhmanufaktur GmbH is a traditional shoe manufacturing company based in Vienna, Austria, founded in 1885. The company operates a well-structured e-commerce website offering a wide range of shoes, accessories, and shoe care products targeting consumers interested in high-quality footwear. The website reflects a consistent brand image and provides comprehensive business and contact information, including social media presence and newsletter subscription options. Technically, the website is built on Magento 2, leveraging modern JavaScript frameworks and marketing tools such as Google Tag Manager and Facebook Pixel. The site is mobile-optimized and features good SEO practices. However, the absence of HTTPS and SSL/TLS certificates is a critical security flaw, exposing users to potential risks. From a security perspective, while several security headers are implemented, the lack of HTTPS severely undermines the site's security posture. Privacy compliance is strong, with clear cookie consent mechanisms and GDPR-aligned privacy policies. Contact information is transparent, but no explicit security or incident response policies are found. Overall, the website is professional and trustworthy from a business and content perspective but requires urgent security improvements, especially enabling HTTPS, to protect user data and enhance trustworthiness.

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

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

  3. 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';…

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

Keep watching ludwig-reiter.com

This scan found 15 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
0
Security headers
65
Email security
50
DNS health
85
Network security
100
GDPR outside view
18
Average
53

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

Ludwig Reiter Schuhmanufaktur GmbH holds a strong market position as a heritage shoe manufacturer with a direct-to-consumer e-commerce model. Their competitive advantage lies in their long-standing brand history and craftsmanship. The business model focuses on retail sales of premium shoes and accessories, supplemented by shoe care products and private custom manufacturing services. The target customer segment includes fashion-conscious consumers valuing quality and tradition. The company maintains an active partnership ecosystem through social media and email marketing platforms. Growth indicators include a modernized online presence and digital marketing integration. Strategically, the company should leverage its brand heritage while enhancing digital security and expanding customer engagement through improved data protection and incident response readiness.

Security posture

The current security maturity level is low due to the absence of HTTPS and SSL/TLS encryption, which is a critical vulnerability. Although security headers such as HSTS, X-Content-Type-Options, and X-XSS-Protection are present, they cannot compensate for the lack of encrypted communication. No evidence of incident response policies or security certifications is found. GDPR compliance is well addressed through cookie consent and privacy policies, but the lack of secure transport undermines data protection efforts. The website does not expose sensitive data or show signs of malware or phishing, but the insecure protocol poses a significant business risk. Incident response readiness appears minimal, with no dedicated security contact channels. The security culture could be improved by implementing HTTPS, regular security audits, and publishing security policies.

Recommendations

  1. Enable HTTPS with a valid SSL/TLS certificate immediately to secure user data and improve trust.
  2. Update server configuration to support modern TLS protocols (TLS 1.2 or 1.3) and strong cipher suites.
  3. Implement OCSP stapling and session resumption to enhance SSL performance and security.
  4. Publish a clear security policy and incident response plan, including dedicated contact channels.
  5. Maintain and regularly update security headers and conduct periodic vulnerability assessments.
Technical notes

Notes

The website uses a robust e-commerce platform (Magento 2) with modern front-end technologies including RequireJS and Bootstrap. Marketing and analytics tools such as Google Tag Manager and Facebook Pixel are integrated for user tracking and advertising. The site is mobile-optimized and features good SEO practices with meta tags and structured navigation. However, the lack of HTTPS is a major technical deficiency. Performance data is unavailable, but the presence of caching headers and CDN usage suggests moderate optimization. Accessibility features are basic but present. The technical debt is moderate, with opportunities to modernize security infrastructure and improve performance monitoring.
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 ludwig-reiter.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 ludwig-reiter.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.