Skip to main content

Security report for oxfam.ca

Oxfam Canada · Non-profit · Canada

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

Security score

65/100

Risk levelMedium

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

Oxfam Canada is a well-established non-profit organization dedicated to fighting global poverty and promoting women's rights through humanitarian response, long-term development, and advocacy. The website reflects a mature digital presence with comprehensive content, including detailed FAQs, structured data, and multiple engagement forms for donations and volunteering. Technically, the site is built on WordPress with modern frameworks and integrates various analytics and marketing tools, ensuring good performance and SEO. Security posture is strong with HTTPS, secure forms, and cookie consent mechanisms, though explicit security policies and vulnerability disclosures are not publicly visible. The absence of WHOIS data for the domain is a notable anomaly but does not detract significantly from the site's legitimacy given the strong branding and content consistency. Overall, the website is professional, trustworthy, and well-optimized for its mission and audience.

Scanned

NIS2 and GDPR posture

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

7 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 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';…

  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 oxfam.ca

This scan found 25 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
42
Security headers
25
Email security
75
DNS health
65
Network security
100
GDPR outside view
85
Average
65

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

Oxfam Canada operates as a large non-profit entity affiliated with the global Oxfam International confederation. Its business model relies on donations, grants, and partnerships, targeting donors, volunteers, and humanitarian stakeholders. The organization maintains a strong market position in the humanitarian aid sector with a focus on women's rights and social justice. The website supports fundraising and advocacy campaigns and collaborates with partner sites such as unwrapped.oxfam.ca for merchandise sales. The digital ecosystem includes robust marketing and analytics integrations, supporting growth and outreach efforts. Transparency is emphasized through published reports and accreditation badges, enhancing donor confidence.

Security posture

The website demonstrates a solid security posture with enforced HTTPS, secure data collection forms, and cookie consent compliance. Multiple security headers are likely implemented, and no sensitive data exposure was detected in the HTML content. However, the site lacks publicly accessible security policies, incident response information, and vulnerability disclosure mechanisms, which are recommended best practices for organizations handling donor and volunteer data. The use of third-party marketing and analytics scripts introduces a moderate tracking footprint, balanced by privacy compliance measures. Overall, the security maturity is good but could be improved by publishing explicit security documentation and establishing a formal vulnerability disclosure process.

Recommendations

  1. Publish a dedicated security policy and incident response page to enhance transparency and trust.
  2. Implement and publicize a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  3. Regularly audit and update third-party scripts to mitigate potential security risks.
  4. Add contact information for a Data Protection Officer or privacy contact to comply with data protection regulations.
  5. Enhance visible security headers and document their presence for user assurance.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Oxfam Canada
Description
Oxfam Canada is a charity organization focused on ending poverty and inequality globally, with a strong emphasis on women's rights, humanitarian response, long-term development, and advocacy.
Key services
Humanitarian emergency response, Long-term development projects, Advocacy and campaigning for social justice and women's rights
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, jQuery, Beaver Builder, Google Tag Manager, Facebook Pixel, AdRoll, Microsoft Clarity, Intercom
Frameworks
Bootstrap
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Secure forms with required fields
  • Cookie consent mechanism implemented
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics (via GTM), Microsoft Clarity
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
AdRoll, Facebook Ads, Bing Ads, Reddit Ads, Google Ads
Tracking pixels
Facebook Pixel, AdRoll Pixel, Microsoft Clarity
Marketing tools
Intercom
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and structured data
  2. Strong focus on women's rights, poverty alleviation, and humanitarian aid
  3. Multiple forms for sign-up and fundraising with required fields
  4. Comprehensive FAQ section embedded in JSON-LD
  5. Use of multiple third-party marketing and analytics tools
  6. Cookie consent banner present and functional
  7. No visible security or privacy policy pages explicitly labeled as security policy
  8. WHOIS data missing or not publicly available for domain
  9. No signs of adult or NSFW content
  10. Good SEO and social media integration
Technical notes

Notes

The website is built on WordPress CMS using the Beaver Builder framework and Bootstrap for responsive design. It integrates jQuery and multiple third-party services including Google Tag Manager, Facebook Pixel, Microsoft Clarity, AdRoll, and Intercom for analytics, marketing, and user engagement. The site demonstrates good mobile optimization, accessibility, and SEO practices with comprehensive metadata and structured data. Performance is moderate, likely influenced by the number of external scripts and tracking pixels. Hosting provider details are not explicitly identified. The technical infrastructure supports a professional and scalable digital presence suitable for a large non-profit organization.
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 oxfam.ca. 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 oxfam.ca.

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.