Skip to main content

Security report for felm.org

Felm · Non-profit · Finland

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

Security score

69/100

Risk levelMedium

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

Felm is a well-established Finnish non-profit organization dedicated to promoting human dignity and justice globally through church cooperation, development projects, peacebuilding, advocacy, and humanitarian aid. With over 160 years of history and operations in 24 countries, Felm maintains a strong market position within the international development and faith-based NGO sector. The website reflects a professional and consistent brand image, targeting donors, partner churches, NGOs, and stakeholders interested in humanitarian and development work. Technically, the website is built on WordPress with modern frameworks like Bootstrap and integrates essential tools such as Google Tag Manager, reCAPTCHA, and social media SDKs. The site is mobile-optimized, accessible, and SEO-friendly, with multilingual support for Finnish, Swedish, and English audiences. Hosting and domain registration are stable and consistent with the organization's profile. From a security perspective, the site uses HTTPS with good SSL configuration and implements standard best practices like cookie consent and form protection via reCAPTCHA. However, it lacks explicit security headers, a published security policy, and a vulnerability disclosure mechanism. Incident response is partially addressed through a whistleblowing policy link, but dedicated security contact channels are absent. Overall, Felm's website demonstrates a solid digital presence with good content quality, technical implementation, and privacy compliance. The security posture is adequate but could be improved with formal policies and enhanced headers. The risk level is low, and the site is trustworthy for users and partners.

Scanned

NIS2 and GDPR posture

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

4 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
    • 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 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 felm.org

This scan found 26 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
62
Security headers
45
Email security
65
DNS health
75
Network security
100
GDPR outside view
68
Average
69

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

No leaked records found

Breach holds no records for felm.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

Felm operates as a medium-sized non-profit entity focused on faith-based international development and humanitarian aid. Its competitive advantage lies in its long history, extensive partnerships with nearly 100 churches and NGOs, and a diversified portfolio of services including church cooperation, development projects, peacebuilding, advocacy, and emergency relief. Revenue streams likely include donations, grants, and fundraising campaigns, supported by clear donation CTAs on the website. The target customer segments include donors, partner churches, NGOs, and international development stakeholders. The multilingual website and social media presence indicate a broad geographic reach and engagement strategy. Strategic observations highlight a strong emphasis on transparency, trust, and community engagement, with room to enhance digital security and compliance frameworks.

Security posture

Felm's security maturity is moderate to good. The website enforces HTTPS and uses Google reCAPTCHA to protect forms, which mitigates common automated abuse. Cookie consent mechanisms align with GDPR requirements, and a whistleblowing policy indicates some governance around incident reporting. However, the absence of key security headers (e.g., CSP, X-Frame-Options), lack of a formal security policy, and no published vulnerability disclosure process represent gaps that could expose the organization to risks. No critical vulnerabilities or exposed sensitive data were detected in the analysis. Enhancing these areas would improve compliance with standards like ISO 27001 or NIST and strengthen incident response readiness. Overall, the security culture appears positive but could benefit from formalization and transparency.

Recommendations

  1. Publish a comprehensive security policy accessible from the website footer or transparency section.
  2. Implement and configure security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to harden the website against common attacks.
  3. Create and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  4. Establish dedicated incident response contact channels (e.g., security@felm.org or abuse@felm.org) to improve communication and response times.
  5. Regularly audit and update third-party plugins and scripts to minimize vulnerabilities and ensure compliance with privacy regulations.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Felm
Description
Felm’s work aims to promote human dignity and justice around the world. Felm works with local lutheran churches and NGOs in 24 countries.
Key services
Church Cooperation, Development Cooperation, Peacebuilding, Advocacy, Humanitarian Aid
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.7.2, jQuery 3.7.1, Bootstrap, Google Tag Manager, Google reCAPTCHA, AddToAny sharing, Instagram Feed plugin, Yoast SEO
Frameworks
Bootstrap
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA on forms
  • Cookie consent banner with settings
  • Whistleblowing policy available

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Facebook SDK
Marketing tools
AddToAny
Transparency
basic

Site quality

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

Key observations

  1. Website is a professionally maintained non-profit organization site
  2. Content is comprehensive and relevant to the organization's mission
  3. Good use of multilingual support with hreflang tags
  4. Cookie consent and privacy policies are implemented
  5. Use of modern web technologies and SEO best practices
  6. No critical security issues detected
  7. Contact information is clear and complete
  8. No terms of service page found
  9. No explicit security policy or vulnerability disclosure found
Technical notes

Notes

The website leverages a mature WordPress CMS platform with modern front-end frameworks like Bootstrap and integrates essential third-party services such as Google Tag Manager, Facebook SDK, and AddToAny sharing tools. The site is multilingual with hreflang tags for Finnish, Swedish, and English, enhancing SEO and user experience. Performance is moderate, with some reliance on external resources (Google Fonts, Maps API) which may impact load times. Accessibility features such as skip links and ARIA labels are present, indicating good attention to inclusive design. The hosting and DNS setup are stable, with domain registration dating back to 1997, reflecting a long-term digital presence. Opportunities exist to optimize performance further and enhance security configurations to reduce technical debt and improve resilience.
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 felm.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 felm.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.