Skip to main content

Security report for schuelke.com

Schülke & Mayr GmbH · Healthcare · Germany

High risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

38/100

Risk levelHigh

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

Schülke & Mayr GmbH is a well-established company specializing in hygiene, infection prevention, and specialty chemicals with a history dating back to 1889. The company targets healthcare, life sciences, and consumer markets, offering a broad range of products and services including hand hygiene, surface disinfection, and scientific expertise. Their market position is strong, supported by certifications such as the Ecovadis GOLD medal and a comprehensive digital presence with multilingual support. Technically, the website is built on Weblication CMS, hosted via Microsoft Online DNS, and integrates marketing and analytics tools like Google Analytics and Pardot. However, the website suffers from critical security shortcomings, notably the absence of a valid SSL certificate and lack of modern TLS protocols, which significantly impact its security posture. Privacy compliance is well addressed with clear cookie and privacy policies and user consent mechanisms. Overall, the site is professional and trustworthy but requires urgent security improvements to protect user data and maintain trust.

Scanned

This is an earlier scan of schuelke.com. View the latest report

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

7 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

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

This scan found 16 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
55
Email security
50
DNS health
85
Network security
20
GDPR outside view
18
Average
38

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

The company operates primarily in the healthcare and manufacturing sectors, focusing on infection prevention and industrial hygiene. Its business model includes B2B and B2C channels, supported by a global partner network and regional sites. The company demonstrates a commitment to sustainability and quality management, as evidenced by its certifications and corporate responsibility sections. The website content and structure reflect a mature digital strategy with clear navigation, multilingual support, and active marketing tools. The partnership with career platforms and regional distributors indicates a broad ecosystem supporting growth and recruitment.

Security posture

The current security posture is weak due to the lack of a valid SSL certificate and disabled TLS protocols, exposing users to potential data interception risks. While security headers like X-Frame-Options and X-XSS-Protection are present, the absence of HTTPS and HSTS significantly undermines overall security. No explicit incident response or security policy pages were found, indicating potential gaps in security governance. The site uses secure cookies with HttpOnly and SameSite attributes, which is positive. Immediate remediation of SSL/TLS issues is critical to prevent data breaches and maintain compliance with security standards.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate supporting TLS 1.2 or TLS 1.3.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  3. Implement OCSP stapling and session resumption to improve SSL performance and security.
  4. Publish a dedicated security policy and incident response information to enhance transparency.
  5. Regularly audit and update security headers and ensure all forms use secure input handling.
Technical notes

Notes

The website uses Apache server and Weblication CMS, with DNS hosted on Microsoft Online. It integrates Google Tag Manager, Google Analytics, and Pardot for marketing and analytics. The site is multilingual with structured navigation and uses responsive design techniques. However, performance metrics are missing or zero, indicating possible measurement gaps. The SSL configuration is invalid, and no modern TLS protocols are enabled, which is a significant technical risk. Accessibility and SEO are basic to good, with proper meta tags and language alternates. The site uses lazy loading for images and deferred CSS loading for performance optimization. Hosting appears stable but could benefit from performance monitoring and SSL improvements.
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

Earlier scans of this domain

  1. 58/100Medium31 findingsView report
Reviews of this site

Share your experience with schuelke.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 schuelke.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.