Skip to main content

Security report for oxfambelgie.be

Oxfam België · Non-profit · Belgium

Medium risk. 5 critical or high findings in Security headers, Email security and 1 other check.

Security score

61/100

Risk levelMedium

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

Oxfam België is a well-established non-profit organization dedicated to fighting inequality and promoting a just economy in Belgium. The website reflects a mature digital presence with comprehensive content about their mission, activities, and impact. Their market position is strong within the non-profit sector, supported by multiple subsidiaries and partnerships under the Oxfam International umbrella. The site is professionally designed, mobile-optimized, and provides clear navigation and trust signals such as transparency and contact information. Technically, the site uses Drupal 10 CMS with modern analytics and marketing tools, maintaining good performance and accessibility standards. Security posture is robust with HTTPS, security headers, and cookie consent mechanisms, although there is room for improvement in publishing explicit security policies and incident response information. Overall, the website is safe, trustworthy, and compliant with GDPR requirements, making it a credible platform for donors, volunteers, and the general public interested in humanitarian and social justice causes.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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
    • 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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

  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
    • High

      Weak SSL Key Length

      SSL certificate uses 384-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

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

Keep watching oxfambelgie.be

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
52
Security headers
40
Email security
65
DNS health
85
Network security
40
GDPR outside view
83
Average
61

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

The organization operates primarily in the non-profit sector focusing on humanitarian aid, fair trade, and advocacy. Their business model relies on donations, volunteer engagement, and retail through fair trade shops. The website indicates a large organizational size with a broad target audience including individuals, companies, and schools. Their partnership ecosystem includes related Oxfam domains and fair trade entities. The site content and structure suggest a strategic focus on transparency, community involvement, and impact storytelling to drive engagement and funding. Growth indicators include active campaigns, events, and educational programs. The presence of multiple language versions and online shops supports a diversified outreach strategy.

Security posture

The website demonstrates a good security maturity level with enforced HTTPS, comprehensive security headers, and a cookie consent mechanism aligned with GDPR. No exposed sensitive data or vulnerable libraries were detected in the HTML content. However, the absence of a public security policy or vulnerability disclosure page and lack of incident response contact details indicate areas for improvement. The use of multiple third-party analytics and marketing scripts necessitates ongoing monitoring to ensure privacy compliance and mitigate risks. Overall, the security posture is strong but could benefit from enhanced transparency and formalized security documentation.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Implement a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  3. Provide clear incident response contact information for security issues.
  4. Regularly audit and update third-party scripts to minimize privacy and security risks.
  5. Enhance user privacy controls and transparency regarding data collection and retention.

Contact details published on the site

Addresses
Legal name
Oxfam België vzw
VAT number
BE 0408.643.875
Registration number
BE 0743.875.974
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Oxfam België
Description
Oxfam België is a movement fighting against inequality and for a just economy that respects human rights and the planet. They aim to end poverty and injustice now and long term, striving for a future where everyone has equal opportunities to live fully.
Key services
Humanitarian aid, Advocacy and political engagement, Fair trade product sales, Volunteer mobilization, Educational programs
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Matomo Analytics, Google Tag Manager, Google Analytics, Hotjar, Adobe Analytics
Frameworks
Drupal
Platforms
Web
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism
  • No exposed sensitive data in HTML
  • Use of security headers
  • No visible vulnerable libraries

Analytics and tracking

Services
Matomo, Google Analytics, Hotjar, Adobe Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
DoubleClick, AdsRvr
Tracking pixels
Matomo, Hotjar, Adobe Analytics, LinkedIn Insights, Twitter
Marketing tools
Matomo, Hotjar
Transparency
good

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 maintained.
  2. Strong focus on transparency and user engagement.
  3. Comprehensive cookie and privacy policies with consent mechanisms.
  4. Use of multiple analytics and marketing tools with privacy considerations.
  5. No signs of malicious or suspicious content.
  6. Clear contact and business information provided.
  7. No visible security or privacy red flags.
Technical notes

Notes

The website is built on Drupal 10, a modern and secure CMS platform, leveraging Matomo for privacy-friendly analytics alongside Google Analytics and Hotjar for user behavior insights. The site uses Google Tag Manager for marketing tag management. Performance is moderate with good mobile optimization and accessibility features. The presence of multiple external scripts requires careful management to avoid performance degradation and privacy issues. Hosting appears stable with a reputable registrar (Gandi Sas). The site uses canonical and hreflang tags for SEO and multilingual support. Overall, the technical infrastructure is solid with opportunities to optimize performance and security documentation.
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 oxfambelgie.be. 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 oxfambelgie.be.

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.