Skip to main content

Security report for jembi.org

Jembi Health Systems · Healthcare · South Africa

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

Security score

50/100

Risk levelMedium

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

Jembi Health Systems is a South African-based organization specializing in the design, development, and implementation of human-centered health information systems primarily for low-resource settings in Africa. The company partners with international aid organizations and governments to enhance public health through innovative technology solutions. Their market position is strong within the niche of digital health systems, supported by their involvement in significant projects such as the Country Health Information Systems and Data Use (CHISU) project and the OpenHIM interoperability platform. The website reflects a professional and consistent brand image, targeting aid organizations, governments, health workers, and patients in Africa. Technically, the website is built on the Wix platform utilizing modern technologies including React 18 and various Wix-specific SDKs and widgets. The site demonstrates good performance and basic mobile optimization, with standard SEO practices and accessibility features in place. Integration with analytics services like Google Analytics and marketing tools such as Mailchimp is evident, indicating a moderate level of digital maturity. From a security perspective, the site enforces HTTPS and employs script-based security enhancements, including hardened fetch and XHR requests and cookie management restrictions. Error monitoring is implemented via Sentry. However, explicit security headers are not detected, and there is a lack of visible privacy and cookie policies, which are critical for compliance and user trust. No critical vulnerabilities or WAF blocking mechanisms were identified. Overall, the website presents a trustworthy and professional front for Jembi Health Systems, though improvements in privacy compliance and security header implementation are recommended to enhance user trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

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

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

  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"

    • 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 jembi.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
0
Security headers
35
Email security
75
DNS health
80
Network security
100
GDPR outside view
10
Average
50

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

Jembi Health Systems operates in the healthcare technology sector, focusing on digital health information systems for African low-resource environments. Their business model appears to be non-profit or NGO-oriented, collaborating with international aid agencies and governments. The company leverages partnerships and consortiums to deliver scalable health solutions, emphasizing interoperability, data quality, and capacity building. Their target customers include health ministries, aid organizations, and healthcare providers. The website's content and structured data indicate a medium-sized organization with a consistent brand and a clear focus on health system strengthening. The presence of multiple projects and programs suggests active engagement and growth potential in their niche market.

Security posture

The website demonstrates a moderate security posture with HTTPS enforced and several client-side security measures such as hardened fetch/XHR and cookie handling restrictions. The use of Sentry for error monitoring indicates proactive incident detection. However, the absence of explicit security headers like Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces the overall security robustness. No sensitive data exposure or vulnerable libraries were detected in the provided content. The lack of visible security policies or incident response information may impact user confidence and compliance with best practices. Enhancing these areas would improve the security maturity and resilience of the website.

Recommendations

  1. Implement and prominently display comprehensive privacy and cookie policies to ensure GDPR and other regulatory compliance.
  2. Add standard security headers such as CSP, HSTS, and X-Frame-Options to strengthen protection against common web attacks.
  3. Ensure all forms include anti-CSRF tokens and robust input validation to prevent injection attacks.
  4. Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.
  5. Improve mobile optimization and accessibility features to enhance user experience and compliance.

Contact details published on the site

Addresses
Legal name
Jembi Health Systems
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Jembi Health Systems
Description
Jembi partners with international aid organizations and governments to build human-centered health information systems in low-resource settings.
Key services
Design and development of digital health information systems, Implementation, training and support, Data analysis for strategic management, Interoperability solutions (OpenHIM), Technical assistance and capacity building
Content quality
good
Branding
consistent

Technology

Stack
Wix platform, JavaScript, React 18, Wix-specific SDKs and APIs, Google Analytics, Mailchimp integration, Various Wix apps and widgets
Frameworks
React, Wix Thunderbolt
Platforms
Wix
Performance
fast
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced (implied by https URLs)
  • Use of security override scripts to harden fetch and XHR
  • Cookie handling with restrictions on certain cookies
  • Use of Sentry for error monitoring

Analytics and tracking

Services
Google Analytics, Wix Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Mailchimp, Wix Analytics
Marketing tools
Mailchimp, Wix ShoutOut, Wix Chat
Transparency
basic

Site quality

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

Key observations

  1. Website is built on Wix platform with extensive use of Wix apps and widgets
  2. Content is focused on health information systems in Africa, targeting aid organizations and governments
  3. No explicit privacy or cookie policies found on main page
  4. Contact information is clearly provided in footer and structured data
  5. Use of modern technologies and frameworks like React 18
  6. Security measures include HTTPS and some script-based protections
  7. No critical security issues or WAF blocking detected
  8. Social media presence includes LinkedIn, Facebook, Instagram, YouTube, Twitter
  9. No visible vulnerability disclosure or incident response information
Technical notes

Notes

The website is built on the Wix platform, utilizing React 18 and various Wix-specific SDKs and widgets. It integrates with multiple third-party services including Google Analytics and Mailchimp for analytics and marketing. The site uses modern JavaScript frameworks and follows standard web development practices. Performance is optimized with fast loading times and responsive design elements, though mobile optimization is basic. The technical infrastructure is well-maintained with no evident technical debt or deprecated technologies. Opportunities exist to enhance accessibility and implement advanced security headers for improved robustness.
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 jembi.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 jembi.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.