Skip to main content

Security report for medizinethik-frankfurt.de

Zentrum für Ethik in der Medizin (ZEM) · Healthcare · Germany

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

Security score

48/100

Risk levelHigh

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

The Zentrum für Ethik in der Medizin (ZEM) was a specialized non-profit center focused on medical ethics, affiliated with the Evangelische Kirche in Hessen und Nassau (EKHN). Founded in 1996, it served as a key institution in the region until its closure in April 2025. The website provides information about its services, publications, and contact details, targeting individuals and organizations interested in medical ethics within the church and healthcare sectors in Germany. Technically, the site is built on TYPO3 CMS and uses Matomo for analytics, indicating a moderate level of digital maturity. However, the absence of a valid SSL certificate and HTTPS support is a critical security shortfall, significantly impacting the site's security posture. The site implements a comprehensive cookie consent mechanism and provides clear privacy policy information, demonstrating good privacy compliance. Overall, the website is functional and professional but requires urgent security improvements to protect user data and enhance trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
0/ 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

6 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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

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

Keep watching medizinethik-frankfurt.de

This scan found 18 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
65
Email security
50
DNS health
70
Network security
100
GDPR outside view
0
Average
48

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 business operates in the healthcare and non-profit sectors, specifically focusing on medical ethics within a church context. Its market position was strong as the first special office for medical ethics in the EKHN region. The business model is non-commercial, supported by the church, offering ethical consultation, publications, and educational resources. The target audience includes healthcare professionals, church members, and the general public interested in medical ethics. The website reflects a small-sized organization with a clear affiliation to EKHN, which enhances credibility. The lack of terms of service and incident response information suggests limited formalization in some operational areas. The partnership ecosystem includes EKHN and related church domains, reinforcing its niche positioning.

Security posture

The security posture is weak due to the lack of HTTPS and valid SSL certificates, exposing users to potential data interception risks. While some security headers like Content-Security-Policy, X-XSS-Protection, and X-Content-Type-Options are present, the absence of modern TLS protocols and HSTS reduces overall security effectiveness. No incident response or vulnerability disclosure policies are evident, indicating limited preparedness for security incidents. The cookie consent implementation and privacy policy are positive indicators of compliance culture. Immediate remediation of SSL/TLS issues is critical to protect user data and maintain trust.

Recommendations

  1. Acquire and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  3. Implement OCSP stapling to improve certificate validation performance and security.
  4. Review and update server configuration to support modern TLS protocols (TLS 1.2 and 1.3).
  5. Develop and publish formal security policies including incident response and vulnerability disclosure.
  6. Add a terms of service page to clarify user agreements and legal protections.
  7. Enhance mobile optimization and accessibility to improve user experience.
  8. Regularly audit and update third-party libraries and CMS extensions to avoid vulnerabilities.

Contact details published on the site

Addresses
Technical notes

Notes

The website is powered by TYPO3 CMS, a mature open-source content management system, hosted on an nginx server with nameservers managed by systemtechnics.de. The site uses compressed CSS and JavaScript assets for performance optimization and integrates Matomo analytics for visitor tracking. However, performance metrics are unavailable, and mobile optimization is basic. The site lacks HTTPS support, which is a major technical deficiency. SEO is basic with meta tags and canonical links present. Accessibility features are minimal but some responsive design elements exist. The technical stack is stable but requires modernization, especially in security protocols and 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 medizinethik-frankfurt.de. 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 medizinethik-frankfurt.de.

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.