Skip to main content

Security report for brookings.edu

Brookings Institution · Government · United States

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

Security score

71/100

Risk levelMedium

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

The Brookings Institution operates as a leading nonprofit public policy organization based in Washington, DC, with a mission to conduct in-depth research to solve societal problems at multiple levels. The website reflects a mature digital presence with comprehensive content, professional design, and strong SEO and accessibility features. Technically, the site leverages WordPress CMS with modern frameworks and integrates Google Analytics, Tag Manager, and Osano for consent management, indicating a robust infrastructure. Security posture is strong with HTTPS enforced and use of reCAPTCHA, though explicit security headers could be improved. Privacy compliance is well addressed with clear privacy and cookie policies and consent mechanisms. Overall, the site demonstrates high business credibility and trustworthiness, though WHOIS data for the www subdomain is unavailable, which is typical for edu domains. No critical security or content safety issues were detected.

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

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 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 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 brookings.edu

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. 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
75
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
68
Average
71

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

Brookings holds a prominent market position as a large, established think tank in the government and nonprofit sectors, serving policymakers, academics, and the public. Its business model centers on independent research and policy analysis, supported by publications, events, and digital media. The organization maintains a consistent brand and high-quality content, with a broad topical scope including federal fiscal policy, trade, education, and artificial intelligence. The website's integration with multiple analytics and marketing tools suggests active audience engagement and outreach. No suspicious domains or partners were identified, reinforcing its legitimacy.

Security posture

Brookings exhibits a mature security posture with mandatory HTTPS, use of Google reCAPTCHA on forms, and a comprehensive cookie consent mechanism via Osano CMP. However, explicit security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options were not detected in the provided data, representing an area for enhancement. No exposed sensitive data or vulnerable libraries were found. Incident response and security policy information are not publicly evident, which could be improved for transparency. Overall, the site is secure but could benefit from additional header hardening and published security policies.

Recommendations

  1. Implement and enforce Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options headers to enhance browser security.
  2. Publish clear security and incident response policies accessible from the website to improve transparency and trust.
  3. Regularly audit third-party scripts and dependencies to mitigate potential vulnerabilities.
  4. Enhance contact information visibility, including security contact channels, to support incident reporting.
  5. Maintain and update privacy and cookie policies to ensure ongoing GDPR and global compliance.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Brookings Institution
Description
The Brookings Institution is a nonprofit public policy organization based in Washington, DC. Its mission is to conduct in-depth research that leads to new ideas for solving problems facing society at local, national, and global levels.
Key services
Policy research, Public policy analysis, Events and conferences, Publications and commentary, Podcasts and newsletters
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress CMS, Yoast SEO plugin, Google Tag Manager, Google Analytics, Google reCAPTCHA, Osano Consent Management Platform, UIkit framework, Swiper.js
Frameworks
UIkit
Platforms
WordPress
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
excellent

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA for forms
  • Consent management via Osano CMP
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Parsely
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google Ads
Tracking pixels
Parsely
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 professional design.
  2. Strong privacy and cookie consent mechanisms implemented.
  3. No contact emails or phone numbers explicitly found in provided content.
  4. No explicit security or incident response policies found on main pages.
  5. Use of modern web technologies and SEO best practices.
  6. No suspicious or malicious content detected.
  7. WHOIS data for www.brookings.edu subdomain not found, typical for edu domains.
Technical notes

Notes

The website is built on WordPress CMS with a modern tech stack including UIkit framework, Swiper.js for UI components, and Google services for analytics and tag management. The site is mobile-optimized with responsive design and accessibility features. Performance is moderate, likely due to rich media content and third-party integrations. The use of Osano CMP indicates a commitment to privacy compliance. Hosting provider details are not explicit. The site benefits from SEO best practices including structured data (JSON-LD) and Open Graph metadata. Opportunities exist to improve security headers and possibly optimize performance further.
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 brookings.edu. 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 brookings.edu.

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.