Skip to main content

Security report for drupal.org

Drupal Association · Technology · N/a

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

Security score

66/100

Risk levelMedium

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

Drupal.org is the official website for the Drupal content management system, a widely used open-source platform for building websites and applications. The site is operated by the Drupal Association and serves a global community of developers, site builders, and organizations. Drupal holds a strong market position as a leading CMS with extensive community support and resources. However, the current website content is inaccessible due to a Web Application Firewall (WAF) implemented by PerimeterX, which blocks access based on suspected automation or security concerns. This limits the ability to fully assess the site's content, policies, and technical infrastructure. From a technical perspective, the site employs PerimeterX for bot mitigation and security, but no further details on hosting or additional frameworks are available due to content blocking. The lack of visible privacy, cookie, or terms of service policies in the accessible content restricts evaluation of compliance with data protection regulations such as GDPR. Security headers and SSL configuration details are also unavailable, preventing a thorough security posture assessment. The security posture is currently weak in terms of transparency and accessibility, primarily due to the WAF blocking legitimate analysis. No vulnerabilities or exposed sensitive data were detected, but the inability to access the site content and metadata significantly reduces confidence in the overall security and compliance status. The WHOIS data is unavailable or privacy protected, which is common for large open-source projects but reduces trust slightly due to lack of transparency. Overall, the site represents a major technology entity with a strong brand and community presence, but the current access restrictions and lack of visible compliance documentation present challenges for comprehensive security and compliance evaluation. Strategic recommendations include adjusting WAF settings to allow legitimate traffic, publishing clear privacy and security policies, and enhancing transparency around domain registration and security practices.

Scanned

This is an earlier scan of drupal.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

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

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

Keep watching drupal.org

This scan found 21 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
82
Security headers
15
Email security
90
DNS health
75
Network security
100
GDPR outside view
35
Average
66

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

Drupal.org operates as the central hub for the Drupal open-source CMS project, targeting developers, enterprises, and organizations seeking a flexible and scalable content management solution. Its business model revolves around community-driven development, support services, and fostering an ecosystem of contributors and partners. The site is positioned as a leader in the open-source CMS market, competing with other platforms by emphasizing extensibility and community collaboration. Revenue streams likely include donations, sponsorships, and support offerings through the Drupal Association. The absence of visible contact phone numbers or physical addresses in the accessible content suggests a primarily digital and community-focused operation. Partnerships and ecosystem relationships are not discernible from the blocked content, but Drupal's known global community implies a broad network of contributors and service providers.

Security posture

The current security posture assessment is limited by the PerimeterX WAF blocking access to the website content. This blocking indicates an active security control to mitigate automated threats and abuse, which is a positive security practice. However, the lack of accessible security headers, SSL configuration details, and compliance documentation restricts a full evaluation. No incident response contacts or vulnerability disclosure policies are visible, which are important for mature security programs. The WHOIS data is privacy protected, which is typical but reduces transparency. Overall, the site demonstrates some security awareness through WAF deployment but lacks visible indicators of comprehensive security governance and compliance readiness in the accessible content.

Recommendations

  1. Adjust PerimeterX WAF settings to reduce false positives and allow legitimate user and analyst access.
  2. Publish clear and accessible privacy, cookie, and terms of service policies on the website.
  3. Implement and expose security headers and HTTPS configuration details to improve security posture.
  4. Provide visible contact information for security incident response and vulnerability disclosure.
  5. Increase transparency around domain registration and ownership information to enhance trust.
Site observations

Automated reading of the public site. Ratings are indicative.

PerimeterX detected. Access denied page with PerimeterX captcha and blocking due to suspected automation tools. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Company
Drupal Association
Description
Drupal is an open-source content management system used for building websites and applications.
Key services
Drupal CMS software, Community support, Documentation and resources

Technology

Stack
PerimeterX

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
PerimeterX
Transparency
poor

Site quality

Trustworthiness
low

Key observations

  1. Website content is blocked by PerimeterX WAF due to suspected automation.
  2. No WHOIS data available from raw output; domain info is privacy protected or inaccessible.
  3. No privacy, cookie, or terms of service policies detected in the provided HTML.
  4. No contact phone numbers or physical addresses found; only an email contact for help.
  5. No forms or user input fields detected due to blocked content.
  6. External resources are limited to Google Fonts and PerimeterX domains.
  7. No social media links or structured data found in the HTML.
  8. Website is a known open-source CMS platform but analysis is limited by access restrictions.
Technical notes

Notes

The website uses PerimeterX technology for bot detection and mitigation, indicating a focus on protecting against automated threats. The presence of Google Fonts suggests standard web font usage. The CMS is Drupal, a widely adopted open-source platform. Due to the WAF blocking, no further technical details such as hosting provider, additional frameworks, or performance metrics are available. The HTML content is minimal and primarily serves a security challenge page, preventing analysis of SEO, accessibility, or mobile optimization. The site would benefit from improved technical transparency and performance monitoring once access restrictions are adjusted.
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. 66/100Medium30 findingsView report
  2. 66/100 −1Medium30 findingsView report
  3. 67/100Medium25 findingsView report
Reviews of this site

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