Skip to main content

Security report for kmk.org

Other · N/a

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

60/100

Risk levelMedium

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

The website kmk.org is currently inaccessible due to a TYPO3 CMS configuration error related to the trusted hosts pattern, resulting in an HTTP 503 error page. This prevents access to any meaningful content or business information. The domain is registered since 1996 with RegistryGate GmbH, indicating a long-standing registration, but no registrant details or business identity are visible on the site. The technical infrastructure is based on TYPO3 CMS, but the site lacks proper configuration and optimization, leading to poor performance and user experience. Security posture is weak due to missing security headers, lack of DNSSEC, and no visible HTTPS enforcement data. No privacy, cookie, or terms of service policies are present, and no contact or incident response information is available, indicating low compliance maturity. Overall, the site is not currently functional for end users or business purposes.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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. 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';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

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

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

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching kmk.org

This scan found 22 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
72
Security headers
70
Email security
70
DNS health
75
Network security
20
GDPR outside view
50
Average
60

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

Due to the site being inaccessible and lacking content, no clear business model, market positioning, or services can be identified. The domain age suggests an established entity, but no supporting data confirms active operations or market presence. No partnerships, subsidiaries, or certifications are visible. The lack of contact information and policies further limits business credibility and transparency.

Security posture

The security posture is poor, primarily due to the TYPO3 trusted hosts pattern misconfiguration causing site inaccessibility. No security headers or HTTPS status are confirmed. DNSSEC is not enabled, and no incident response or vulnerability disclosure information is provided. The site does not demonstrate GDPR compliance or data protection readiness. These factors indicate a low security maturity level and potential risk if the site were operational.

Recommendations

  1. Fix the TYPO3 trusted hosts pattern configuration to restore website accessibility.
  2. Enable and enforce HTTPS with a valid SSL/TLS certificate.
  3. Implement standard security headers such as Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options.
  4. Publish privacy, cookie, and terms of service policies to improve compliance and user trust.
  5. Add clear contact and incident response information including security contact emails.
  6. Enable DNSSEC for the domain to enhance DNS security.
  7. Conduct a security audit to identify and remediate any other vulnerabilities.
  8. Improve website content quality, navigation, and mobile optimization for better user experience.
  9. Consider adding analytics and marketing tools with privacy compliance mechanisms.
  10. Establish a long-term security and compliance strategy aligned with industry best practices.
Site observations

Automated reading of the public site. Ratings are indicative.

None detected. Website is inaccessible due to TYPO3 trusted hosts pattern misconfiguration causing HTTP 503 error page. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Frameworks
TYPO3
Performance
slow
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
20/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website is currently inaccessible due to a TYPO3 configuration error (trusted hosts pattern mismatch).
  2. No visible business or contact information on the landing page.
  3. No privacy, cookie, or terms of service policies found.
  4. No forms or data collection mechanisms detected.
  5. No security headers or HTTPS status information available from provided data.
  6. WHOIS data shows a long-registered domain with a reputable registrar but no registrant details.
  7. No analytics, advertising, or tracking technologies detected.
  8. Website content is minimal and consists solely of an error message.
  9. No social media or contact links found.
  10. No evidence of adult or questionable content.
Technical notes

Notes

The website is built on TYPO3 CMS but currently suffers from a critical configuration error related to trusted hosts, causing a 503 error and blocking access. No additional technologies, scripts, or analytics tools are detected. The domain is hosted by RegistryGate GmbH. The site lacks mobile optimization, accessibility features, and SEO meta tags. No performance data is available, but the error page indicates poor technical health. The absence of security headers and DNSSEC reduces the overall security posture. The site requires modernization and proper configuration to be operational and secure.
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 kmk.org. 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 kmk.org.

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.