Skip to main content

Security report for oikoumene.org

World Council of Churches · Non-profit · Switzerland

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

Security score

68/100

Risk levelMedium

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

The World Council of Churches website serves as the digital presence for a large, established non-profit organization dedicated to fostering unity, justice, and peace among global Christian churches. The site offers rich content including news, events, resources, and educational materials, targeting a worldwide ecumenical audience. The organization is well-positioned in its sector with a history dating back to 1948 and a domain registered since 2003, reflecting stability and credibility. Technically, the website is built on Drupal 11, leveraging modern web technologies and hosted with Cloudflare DNS services. It demonstrates good mobile optimization, accessibility, and SEO practices. The presence of Google Analytics and social sharing tools indicates moderate user tracking balanced with privacy compliance, including a clear cookie consent mechanism. From a security perspective, the site enforces HTTPS, employs standard security headers, and restricts domain transfers, contributing to a strong security posture. However, DNSSEC is not enabled, and explicit security policies or incident response contacts are not published, representing areas for improvement. Overall, the website is professional, trustworthy, and safe for general audiences, with no adult or questionable content detected. The domain registration and website content are consistent, supporting a high legitimacy score. Strategic recommendations include enabling DNSSEC, publishing security and incident response policies, and adding vulnerability disclosure information to enhance transparency and trust.

Scanned

NIS2 and GDPR posture

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

5 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
  2. GDPR outside view

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

    • 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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048
  4. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Domain Expires Soon

      Domain expires in 18 days

      What to do: Renew domain registration before expiration

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

Keep watching oikoumene.org

This scan found 23 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
75
Security headers
65
Email security
55
DNS health
60
Network security
100
GDPR outside view
53
Average
68

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 oikoumene.org, from OffSeq Breach.

Total records
10
Employees
0
Customers
10
Third parties
0
Weak passwords
0%

2 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 oikoumene.org.

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

The World Council of Churches operates as a global non-profit entity focused on ecumenical collaboration among Christian churches. Its business model revolves around advocacy, education, event organization, and resource dissemination to promote unity, justice, and peace. The organization targets churches, faith communities, and ecumenical partners worldwide. Its competitive advantage lies in its long history, global reach, and comprehensive program areas including youth engagement, gender justice, and peacebuilding. The website reflects a mature digital presence with active social media integration and a clear content strategy supporting its mission. Partnerships such as the Green Village project indicate engagement with broader sustainability initiatives. The organization maintains a strong brand consistency and trust signals, positioning it as a key player in the non-profit religious sector.

Security posture

The website demonstrates a solid security foundation with HTTPS enforced and multiple security headers present, including HSTS, X-Content-Type-Options, and Content-Security-Policy. The domain status clientTransferProhibited prevents unauthorized domain transfers. No sensitive data exposure or vulnerable libraries were detected in the HTML content. Cookie consent is implemented with an opt-in mechanism, supporting GDPR compliance. However, DNSSEC is not enabled, which could improve DNS security. The absence of published security policies or incident response contacts limits transparency and readiness perception. No vulnerability disclosure or security.txt file is present, which could be added to enhance security culture and user trust. Overall, the security posture is good but could be strengthened with additional transparency and DNS security measures.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish a dedicated security policy page outlining security practices and commitments.
  3. Add incident response contact information or a dedicated security email address.
  4. Implement and publish a vulnerability disclosure policy or security.txt file.
  5. Regularly review and update third-party libraries and scripts to avoid vulnerabilities.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
World Council of Churches
Description
Inspiring the worldwide fellowship of churches to work together for unity, justice and peace.
Key services
Ecumenical relations, Education, Youth engagement, Mission, Justice advocacy, Peacebuilding, Resources and publications, Events and conferences
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 11, Google Tag Manager, AddToAny sharing, Cloudflare DNS
Frameworks
Drupal
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • Cookie consent banner with opt-in
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Google Analytics (via Google Tag Manager)
Marketing tools
AddToAny social sharing
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 maintained using Drupal 11.
  2. Strong focus on ecumenical cooperation, justice, peace, and unity.
  3. Comprehensive cookie consent mechanism implemented.
  4. No exposed sensitive data or security issues detected.
  5. Social media presence is active and linked.
  6. WHOIS data supports legitimacy and long-term operation.
  7. No explicit security or incident response policies published.
  8. No terms of service page found.
Technical notes

Notes

The website is built on Drupal 11, a modern and supported CMS platform, indicating up-to-date infrastructure. It uses Cloudflare for DNS and likely CDN services, enhancing performance and security. The site includes Google Tag Manager for analytics and AddToAny for social sharing, reflecting a mature digital marketing setup. Performance is moderate, with good mobile responsiveness and accessibility features implemented. SEO is well addressed with proper meta tags and Open Graph data. The site uses standard web technologies and scripts, with no deprecated or vulnerable libraries detected. There is room for improvement in DNS security by enabling DNSSEC. Overall, the technical infrastructure supports a professional and scalable web presence aligned with the organization's mission.
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 oikoumene.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 oikoumene.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.