Skip to main content

Security report for dlang.org

D Language Foundation · Technology · N/a

High risk. 12 critical or high findings in Security headers, GDPR outside view and 3 other checks.

Security score

38/100

Risk levelHigh

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

The D Language Foundation operates the official website for the D programming language, a general-purpose, statically typed language with systems-level access and C-like syntax. The foundation supports the language's development, community engagement, and ecosystem growth. The website serves as a comprehensive resource hub offering documentation, tutorials, community forums, package management, and downloadable compiler binaries. It targets software developers and technology enthusiasts interested in efficient and modern programming languages. The foundation is a non-profit entity coordinating volunteer efforts and sponsorships to sustain the language's evolution. Technically, the website is well-structured, leveraging modern web technologies such as HTML5, CSS3, JavaScript, jQuery, and CodeMirror for interactive code examples. It uses Cloudflare for DNS and likely CDN services, ensuring fast performance and good mobile optimization. The site is accessible, SEO-friendly, and provides a rich user experience with clear navigation and relevant content. However, it lacks some modern security headers and DNSSEC is not enabled. From a security perspective, the site enforces HTTPS and avoids exposing sensitive data or vulnerable libraries. There are no forms collecting sensitive personal data, reducing attack surface. However, the absence of a privacy policy, cookie consent mechanism, security policy, and incident response contact information represents compliance and transparency gaps. No vulnerability disclosure or security.txt files were found, which could hinder responsible vulnerability reporting. Overall, the website is professional, trustworthy, and technically sound but could improve privacy compliance and security transparency. Strategic recommendations include publishing privacy and cookie policies, enabling DNSSEC, adding security headers, and providing clear security and incident response information to enhance user trust and regulatory compliance.

Scanned

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

12 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 dlang.org

This scan found 32 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
62
Security headers
30
Email security
75
DNS health
5
Network security
20
GDPR outside view
35
Average
38

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

The D Language Foundation occupies a niche in the programming language ecosystem, offering a modern alternative to C and C++ with a focus on performance and developer productivity. Its open-source business model is supported by community contributions, sponsorships, and donations. The foundation's ecosystem includes a package manager (DUB), extensive documentation, and active community channels such as forums, IRC, Discord, and social media. The foundation's market position is stable with adoption by notable organizations (e.g., Netflix, eBay) and a growing user base. The website reflects a mature digital presence with strategic partnerships and a clear focus on developer engagement and education. Revenue streams likely include sponsorships and donations, with no direct commercial sales evident. The foundation's operations emphasize transparency, community involvement, and open governance.

Security posture

The website demonstrates a moderate to strong security posture with enforced HTTPS, no visible sensitive data leaks, and no use of vulnerable libraries. The use of Cloudflare DNS adds resilience and performance benefits. However, the lack of DNSSEC reduces DNS security. The absence of security headers such as Content-Security-Policy and X-Frame-Options is a missed opportunity to harden the site against common web attacks. The site does not provide a security policy or incident response contacts, which limits transparency and preparedness for security incidents. No vulnerability disclosure mechanisms or security.txt files were found, which could delay vulnerability reporting and remediation. Overall, the site is secure for general use but would benefit from enhanced security controls and compliance documentation.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy with GDPR compliance details.
  2. Implement a cookie consent mechanism to comply with privacy regulations.
  3. Enable DNSSEC to improve domain name system security.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Create and publish a security policy and incident response contact information, including a security@ or abuse@ email address.
  6. Add a security.txt file or vulnerability disclosure page to facilitate responsible vulnerability reporting.
  7. Consider adding explicit contact information for business and support inquiries to improve transparency.
  8. Regularly audit third-party scripts and dependencies for vulnerabilities.
  9. Enhance analytics and tracking transparency or minimize tracking to improve privacy compliance.
  10. Maintain consistent branding and update content regularly to sustain trust and engagement.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
D Language Foundation
Description
D is a general-purpose programming language with static typing, systems-level access, and C-like syntax.
Key services
Programming language development, Documentation and learning resources, Community engagement and support, Package management (DUB), Foundation coordination and sponsorship
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, jQuery 1.7.2, CodeMirror, Cloudflare DNS
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (implied by https://dlang.org URL)
  • No exposed sensitive data in HTML
  • No vulnerable libraries detected
  • No forms collecting sensitive data

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

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 interactive code examples.
  2. No privacy or cookie policies are linked or found on the site.
  3. No explicit contact emails or phone numbers are provided on the homepage or visible content.
  4. Strong community presence with multiple social and forum links.
  5. No security.txt or vulnerability disclosure page detected.
  6. No advertising or tracking scripts detected beyond jQuery and CodeMirror.
  7. Site uses HTTPS and Cloudflare DNS but DNSSEC is not enabled.
  8. No forms collecting personal data except a search form that uses Google search.
  9. Website content is highly technical and targeted at developers.
  10. No signs of suspicious or malicious content.
Technical notes

Notes

The website is built using standard web technologies including HTML5, CSS3, and JavaScript with jQuery 1.7.2 and CodeMirror for code editing and display. It uses Cloudflare for DNS and likely CDN services, contributing to fast load times and good mobile responsiveness. The site does not appear to use a CMS, indicating a custom or static site generation approach. Performance is optimized with minimal external dependencies and efficient content delivery. Accessibility and SEO are well addressed with proper meta tags, viewport settings, and structured navigation. However, the site lacks modern security headers and DNSSEC, which are recommended for improved security. The site includes interactive runnable code examples, enhancing user engagement and educational value. Overall, the technical infrastructure is solid, with opportunities for modernization in security and privacy features.
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 dlang.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 dlang.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.