Skip to main content

Security report for ekom21.de

ekom21 – KGRZ Hessen · Government · Germany

Medium risk. 4 critical or high findings in GDPR outside view, Security headers and 1 other check.

Security score

73/100

Risk levelMedium

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

ekom21 – KGRZ Hessen is a prominent IT service provider specializing in digital solutions for public administration in the German state of Hessen. The company offers a broad range of services including software solutions, consulting, IT infrastructure, and training seminars tailored to the needs of municipal governments and public sector entities. Their market position is strong within the regional public sector IT landscape, supported by certifications such as ISO 27001 and ISO 9001:2015, which underscore their commitment to quality and information security. Technically, the website is built on the ionas4 CMS platform and leverages modern web technologies including jQuery, Vue.js, SystemJS, and Matomo analytics. The site demonstrates good mobile optimization, accessibility, and SEO practices, providing a professional and user-friendly experience. The presence of a cookie consent mechanism and comprehensive privacy policies indicates a mature approach to privacy compliance. From a security perspective, the site enforces HTTPS, uses invisible reCAPTCHA for forms, and prominently displays certifications related to information security. While some advanced security headers could be improved, no critical vulnerabilities or exposed sensitive data were detected. The domain WHOIS data is limited but consistent with the business claims, and no WAF or blocking mechanisms interfere with content access. Overall, ekom21 presents a trustworthy, professional, and secure digital presence aligned with its role as a public sector IT service provider. Strategic recommendations include enhancing security headers, publishing a security.txt file, and improving incident response contact visibility to further strengthen their security posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
48/ 100 · High
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

4 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

    • 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. 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';…
  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 ekom21.de

This scan found 20 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
77
Security headers
65
Email security
70
DNS health
75
Network security
100
GDPR outside view
48
Average
73

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention ekom21.de, from OffSeq Breach.

Total records
2,042
Employees
0
Customers
2,025
Third parties
17
Weak passwords
60%

56 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for ekom21.de.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

ekom21 operates as a specialized IT service provider for the public sector in Hessen, Germany, focusing on digital transformation and IT infrastructure for municipal administrations. Their competitive advantage lies in their regional focus, comprehensive service portfolio, and adherence to recognized quality and security standards. Revenue streams likely include software licensing, consulting services, training seminars, and IT support contracts. The target customers are local government entities and public administration professionals. The company maintains a professional partnership ecosystem, as indicated by framework agreements and certifications. Growth indicators include active event hosting and continuous digital content updates. The website reflects a mature and stable operation with a clear market niche.

Security posture

The security maturity of ekom21's website is solid, with HTTPS enforced and ISO 27001 certification indicating a formalized information security management system. The use of invisible reCAPTCHA and cookie consent mechanisms further enhance security and privacy compliance. No critical vulnerabilities or exposed sensitive data were found. However, the absence of some recommended security headers (e.g., Content-Security-Policy, Strict-Transport-Security) suggests room for improvement. Incident response contact information is present but could be more explicit with dedicated security email addresses. Overall, the security culture appears strong, aligned with public sector requirements and certifications.

Recommendations

  1. Implement additional HTTP security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to harden the website against common attacks.
  2. Publish a security.txt file at the root domain to facilitate responsible vulnerability disclosure and improve transparency.
  3. Enhance visibility and clarity of incident response contacts by providing dedicated security-related email addresses (e.g., security@ekom21.de, abuse@ekom21.de).
  4. Regularly audit and update third-party libraries and dependencies to mitigate risks from known vulnerabilities.
  5. Increase transparency regarding hosting provider and infrastructure to support trust and incident response.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
ekom21 – KGRZ Hessen
Description
ekom21 is a municipal IT service provider for the state of Hessen, Germany, offering digital solutions and IT services to public administration and local governments.
Key services
Digitalization & Politics solutions, IT services and products, Consulting, Software framework agreements, Training and seminars
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, SystemJS, Vue.js, Pikaday datepicker, Axios, Clipboard.js, Matomo analytics
Frameworks
CMS ionas4
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with opt-in mechanism
  • No exposed sensitive data in HTML
  • Use of CAPTCHA (Invisible reCAPTCHA)
  • Security certifications ISO 27001 and ISO 9001

Analytics and tracking

Services
Matomo
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Matomo
Transparency
basic

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is professionally designed and well-structured.
  2. Strong focus on public sector IT services and digitalization.
  3. Comprehensive privacy and cookie policies with consent mechanisms.
  4. Use of modern web technologies and CMS ionas4.
  5. Security certifications ISO 27001 and ISO 9001 are prominently displayed.
  6. Contact information is clear and includes multiple channels.
  7. No signs of adult or questionable content.
  8. No WAF or blocking mechanisms detected.
  9. Matomo analytics used with cookie consent enforcement.
Technical notes

Notes

The website is built on the ionas4 CMS platform, utilizing a modern JavaScript stack including jQuery, Vue.js, SystemJS, and Axios. It employs Matomo for privacy-conscious analytics and Pikaday for date inputs. The site is well-structured with responsive design and accessibility considerations. Performance is moderate, with preloading of fonts and scripts to optimize loading times. The technical implementation reflects a mature digital infrastructure suitable for a public sector IT provider. Opportunities exist to modernize security headers and improve hosting transparency to reduce technical risks.
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 ekom21.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 ekom21.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.