Skip to main content

Security report for mission-21.org

Mission 21 · Non-profit · Switzerland

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

Security score

27/100

Risk levelHigh

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

Mission 21 is a well-established Swiss non-profit organization dedicated to sustainable development and humanitarian aid across 18 countries in Africa, Asia, and Latin America. Their work focuses on peace promotion, education, health, food sovereignty, and combating violence against vulnerable groups. The organization is supported by church bodies, foundations, government agencies, and private donors, reflecting a robust and diverse funding model. The website presents comprehensive content in multiple languages, demonstrating a strong commitment to accessibility and outreach. Technically, the website is built on WordPress using the Astra theme and integrates various plugins for forms, e-commerce, and multimedia content. While the site is mobile-optimized and SEO-friendly, performance metrics are not available, indicating potential areas for improvement. The security posture is currently weak due to the absence of a valid SSL certificate and modern TLS protocols, which poses significant risks to user data and trust. Privacy compliance is well addressed with clear privacy and cookie policies, including a consent mechanism, aligning with GDPR requirements. However, the site lacks explicit security policies and incident response information, which are important for transparency and user confidence. Overall, the domain registration data aligns well with the organization's identity, supporting legitimacy. Strategically, Mission 21 should prioritize securing their website with valid SSL/TLS certificates and updating their security configurations to protect user data and enhance trust. Enhancing transparency around security policies and incident response would further strengthen their credibility. Continuous monitoring and performance optimization will also benefit user experience and engagement.

Scanned

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

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

  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. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  4. 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 mission-21.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. 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
25
Email security
50
DNS health
70
Network security
0
GDPR outside view
18
Average
27

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 · found on this site
  • 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 mission-21.org, from OffSeq Breach.

No leaked records found

Breach holds no records for mission-21.org right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

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

Business context

Business profile

Mission 21 occupies a significant position in the non-profit sector focused on international development and humanitarian aid. Their competitive advantage lies in their long history, strong partnerships, and certifications such as ZEWO and EduQua. The organization leverages a multi-channel approach including online donations, educational webinars, and active social media engagement to reach donors and stakeholders. Their target customers include private donors, church communities, and institutional partners. The presence of multilingual content and diverse project portfolios indicates a strategic focus on inclusivity and global impact. Growth indicators include active event scheduling and ongoing project updates. The partnership ecosystem includes recognized entities like ACT Alliance and certification bodies, enhancing their operational credibility.

Security posture

The current security maturity level of Mission 21's website is low due to the lack of a valid SSL certificate and absence of modern TLS protocols, which are critical for secure communications. This exposes the site to risks such as data interception and undermines user trust. While some security headers like HSTS are present, key features such as OCSP stapling, strong cipher suites, and session resumption are missing. There is no visible security policy or incident response information, indicating gaps in compliance and readiness. The site does not show signs of vulnerable libraries or exposed sensitive data, but the fundamental lack of HTTPS is a critical vulnerability. To improve, the organization should implement comprehensive security measures, including valid certificates, updated protocols, and transparent security policies.

Recommendations

  1. Obtain and install a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Enable and configure modern TLS protocols (TLS 1.2 and TLS 1.3) and strong cipher suites to enhance encryption.
  3. Implement OCSP stapling and submit the site for HSTS preload to improve security and performance.
  4. Publish a clear security policy and incident response plan on the website to increase transparency and user confidence.
  5. Regularly audit website components and update plugins and libraries to mitigate vulnerabilities.

Contact details published on the site

Addresses
Legal name
Evangelisches Missionswerk Basel
VAT number
CHE-105.706.527
Technical notes

Notes

The website is built on a mature WordPress platform using the Astra theme, enhanced with multiple plugins for forms, e-commerce (WooCommerce), sliders, and multilingual support (TranslatePress). It integrates external services such as ActiveCampaign for newsletters and Google Analytics for tracking. The site is mobile-optimized and includes accessibility features like skip links and ARIA labels. However, performance data is missing, suggesting a need for monitoring and optimization. The hosting appears to be managed by armacom.ch, a Swiss provider. The absence of a valid SSL certificate and modern security protocols is a significant technical risk. The site uses modern web fonts and icon libraries (FontAwesome), and includes structured data (JSON-LD) for SEO and social media integration.
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 mission-21.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 mission-21.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.