Skip to main content

Security report for greenpeace.org

Greenpeace · Non-profit · N/a

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

Security score

76/100

Risk levelLow

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

Greenpeace is a globally recognized non-profit environmental organization dedicated to advocacy and activism for environmental protection and sustainability. The website serves as a global portal linking to numerous country-specific Greenpeace sites, reflecting its extensive international presence and outreach. The content is professionally presented with consistent branding and clear messaging aimed at a general audience interested in environmental issues. Technically, the website employs modern tracking and advertising technologies such as Google Tag Manager and Taboola, indicating a moderate level of digital maturity. The site is mobile-optimized with good navigation and design quality, although some improvements in accessibility and SEO could be made. The lack of visible privacy and cookie policies on the landing page suggests room for enhancement in privacy compliance. From a security perspective, the site uses HTTPS and includes some best practices but lacks visible security headers and explicit incident response or security policy information. No vulnerabilities or suspicious content were detected, and the domain appears legitimate despite the absence of detailed WHOIS data, which is likely due to privacy protection common for non-profit organizations. Overall, the site presents a low risk profile but would benefit from improved transparency and security hardening. Strategically, Greenpeace should focus on enhancing privacy disclosures, implementing comprehensive security headers, and publishing clear contact and incident response information to bolster trust and compliance. These steps will improve user confidence and align with best practices for global non-profit digital presence.

Scanned

This is an earlier scan of greenpeace.org. View the latest report

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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 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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

Keep watching greenpeace.org

This scan found 15 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. See sample alerts.

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
98
DNS health
80
Network security
100
GDPR outside view
35
Average
76

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

Greenpeace holds a leading position in the global environmental NGO sector, leveraging a broad network of country-specific websites to engage diverse audiences worldwide. Its business model is donation-driven, focusing on advocacy, public awareness, and activism campaigns. The organization benefits from strong brand recognition and consistent messaging, which supports its fundraising and outreach efforts. The use of advertising and tracking technologies suggests a strategic approach to digital marketing and audience engagement. Greenpeace's partnerships and global footprint indicate a mature operational structure, although explicit partner domains were not identified in the provided data. Growth opportunities lie in expanding digital transparency and enhancing compliance frameworks to meet evolving regulatory demands.

Security posture

The website demonstrates a moderate security posture with HTTPS enabled and use of reputable third-party analytics and advertising services. However, the absence of key security headers such as Content-Security-Policy and Strict-Transport-Security reduces the overall security effectiveness. No forms or input fields were detected, minimizing attack surface, but the lack of published security policies and incident response contacts limits transparency and preparedness. Compliance with GDPR and other privacy regulations appears minimal based on the landing page content, indicating potential gaps. Overall, the security maturity is adequate for a non-profit but could be significantly improved by adopting standard security headers, publishing privacy and security policies, and establishing clear incident response channels.

Recommendations

  1. Implement comprehensive privacy and cookie policies with user consent mechanisms to enhance GDPR compliance.
  2. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to improve site security.
  3. Publish clear contact information including security incident response and abuse contacts to increase transparency and trust.
  4. Enhance accessibility features to meet WCAG standards and improve user experience for all visitors.
  5. Regularly audit third-party scripts and tracking technologies to minimize privacy risks and ensure compliance with data protection regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Greenpeace
Description
Greenpeace is a global environmental non-profit organization focused on environmental activism and advocacy to change the world for a sustainable future.
Key services
Environmental campaigns, Advocacy, Public awareness, Activism coordination
Content quality
good
Branding
consistent

Technology

Stack
Google Tag Manager, Taboola, JavaScript
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • HTTPS usage

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Taboola
Transparency
basic

Site quality

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

Key observations

  1. Website is a global portal for Greenpeace with links to country-specific sites.
  2. No contact emails or phone numbers explicitly found on the landing page.
  3. No privacy, cookie, or terms of service policies detected on the landing page HTML.
  4. Uses Google Tag Manager and Taboola for analytics and advertising.
  5. No forms detected on the landing page HTML.
  6. No security headers visible in provided data.
  7. HTTPS is implied by URLs but SSL configuration details not provided.
  8. Content is professional, consistent, and aligned with Greenpeace's mission.
  9. No suspicious or malicious content detected.
Technical notes

Notes

The website uses a modern JavaScript-based front end with integration of Google Tag Manager and Taboola for analytics and advertising. The HTML structure is valid and includes responsive design elements for mobile optimization. However, there is no evidence of a CMS or backend platform from the provided data. Performance appears moderate with multiple external script calls which could impact load times. SEO is basic with minimal meta descriptions and no structured data like JSON-LD detected. Accessibility is basic with some alt attributes present but no ARIA roles or landmarks identified. Hosting provider and infrastructure details are not discernible from the data. Overall, the technical implementation is solid but could benefit from performance optimization, enhanced SEO, and improved accessibility compliance.
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

Earlier scans of this domain

  1. 76/100 +26Low24 findingsView report
  2. 50/100Medium22 findingsView report
Reviews of this site

Share your experience with greenpeace.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 greenpeace.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.