Skip to main content

Security report for wri.org

World Resources Institute · Non-profit · United States

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

Security score

75/100

Risk levelMedium

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

World Resources Institute (WRI) is a globally recognized non-profit research organization dedicated to advancing environmental sustainability, climate action, and equitable development. The organization leverages data, research, and global partnerships to influence policy and catalyze systemic change across sectors such as climate, energy, forests, freshwater, oceans, cities, and finance. WRI maintains a strong international presence with offices and initiatives worldwide, positioning itself as a leader in environmental research and advocacy. Technically, WRI's website is built on Drupal 10, utilizing modern JavaScript libraries and multiple analytics platforms including Google Analytics, Microsoft Clarity, Matomo, and privacy-focused tools like Osano CMP. The site demonstrates good performance, mobile optimization, and accessibility features, reflecting a mature digital infrastructure. Privacy compliance is robust, with clear cookie consent mechanisms and a comprehensive privacy policy. From a security perspective, the site enforces HTTPS and employs reputable third-party services for analytics and consent management. While explicit security headers were not fully confirmed in the provided data, no vulnerabilities or exposed sensitive data were detected. The WHOIS data is privacy protected, which is typical and justified for a large non-profit entity. Overall, the security posture is strong with room for minor improvements such as explicit security header implementation and vulnerability disclosure mechanisms. The overall risk assessment is low, with the website exhibiting high professionalism, trustworthiness, and compliance with privacy regulations. Strategic recommendations include enhancing security header deployment, establishing a security.txt file for vulnerability reporting, and continuous monitoring of third-party scripts to maintain security integrity.

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

3 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 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 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

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

Keep watching wri.org

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

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

WRI operates as a leading non-profit in the environmental research sector, focusing on climate change, sustainable development, and natural resource management. Its competitive advantage lies in its extensive global network, data-driven approach, and influence on policy frameworks. The business model centers on research, advocacy, and partnerships rather than commercial revenue. Target customers include governments, NGOs, researchers, and international organizations. Growth indicators include expanding initiatives and global reach. Partnerships with platforms like Global Forest Watch and UrbanShift enhance its ecosystem. The organization's operations reflect a mature, well-established entity with strong market positioning in the sustainability domain.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, comprehensive cookie consent, and use of trusted analytics and consent management platforms. No critical vulnerabilities or exposed sensitive information were found. However, explicit security headers such as Content-Security-Policy and X-Frame-Options were not confirmed and should be verified. Incident response contact information and vulnerability disclosure mechanisms are not evident, representing an area for improvement. The privacy policy and ethics reporting links indicate a commitment to compliance and ethical standards. Overall, the security culture appears strong but could benefit from formalized vulnerability disclosure and enhanced header policies.

Recommendations

  1. Implement and verify comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  2. Establish a publicly accessible security.txt file to facilitate vulnerability disclosure and incident reporting.
  3. Regularly audit and update third-party scripts and analytics tools to mitigate supply chain risks.
  4. Enhance incident response readiness by publishing clear contact channels for security issues.
  5. Continue to maintain and improve privacy compliance and transparency to strengthen user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
World Resources Institute
Description
WRI is a global research organization working to improve people’s lives, protect nature and halt climate change.
Key services
Research, Data provision, Initiatives and projects, Insights and publications
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, jQuery 3.7.1, Google Tag Manager, Osano CMP, Microsoft Clarity, Matomo Analytics, RudderLabs, Plausible Analytics, Fathom Analytics
Frameworks
Drupal CMS
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with opt-in/out
  • No exposed sensitive data in HTML
  • Use of reputable analytics and CMP providers

Analytics and tracking

Services
Google Analytics, Microsoft Clarity, Matomo, Plausible, Fathom, RudderLabs
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google Ads (AW-1037792155, AW-11414847197)
Tracking pixels
Google Analytics (G-LM9LVY10E1), Microsoft Clarity, Matomo, Plausible, Fathom, RudderLabs
Marketing tools
Osano CMP
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 no blocking detected.
  2. Strong privacy and cookie consent mechanisms implemented.
  3. Multiple reputable analytics and marketing tools used with consent.
  4. No exposed sensitive data or obvious security vulnerabilities found.
  5. WHOIS data is privacy protected or unavailable but domain appears legitimate.
  6. Website uses modern Drupal CMS and up-to-date JavaScript libraries.
  7. Clear business focus on environmental research and policy advocacy.
  8. Good accessibility and mobile optimization observed.
  9. No suspicious or malicious external domains detected.
Technical notes

Notes

The website is powered by Drupal 10 CMS, indicating a modern and scalable content management system. It uses jQuery 3.7.1 and integrates multiple analytics platforms including Google Tag Manager, Microsoft Clarity, Matomo, Plausible, Fathom, and RudderLabs, reflecting a sophisticated data collection and analysis infrastructure. The presence of Osano CMP shows a strong focus on privacy compliance. The site is mobile-optimized with responsive design and accessibility features. Performance is moderate, likely influenced by multiple third-party scripts. Technical risks include potential complexity from numerous external integrations and the need for continuous security monitoring of these components.
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 wri.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 wri.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.