Skip to main content

Security report for djangoproject.com

Django Software Foundation · Technology · N/a

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

Security score

72/100

Risk levelMedium

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

Django is a mature, open source Python web framework supported by the Django Software Foundation, a non-profit organization. The website serves developers and organizations seeking a robust, scalable, and secure web development framework. It offers extensive documentation, community forums, and active engagement channels such as Discord and GitHub. The business model is community-driven with funding through donations and sponsorships, positioning Django as a leading technology project in the web development ecosystem. Technically, the website employs modern JavaScript technologies including RequireJS and custom scripts, with a clean, responsive design optimized for mobile and accessibility. The site uses HTTPS exclusively, ensuring secure communications. SEO and social media metadata are well implemented, enhancing discoverability and sharing. However, some security best practices such as explicit security headers and cookie consent mechanisms are missing. From a security perspective, the site demonstrates a strong posture with no visible vulnerabilities or exposed sensitive data. The project maintains a documented vulnerability disclosure process, though no dedicated security.txt file was found. Privacy compliance is basic, with no explicit privacy or cookie policies prominently displayed, which could be improved to meet GDPR standards. WHOIS data is unavailable, which is unusual but likely due to privacy or registry policies, though this does not detract from the site's legitimacy given its foundation backing. Overall, the site is professional, trustworthy, and technically sound, with minor areas for improvement in privacy and security transparency. Strategic recommendations include adding explicit privacy and cookie policies, implementing security headers, and publishing a security.txt file to enhance trust and 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

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

    • High

      Third-party services without privacy policy

      Detected services: LinkedIn

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching djangoproject.com

This scan found 18 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
85
Security headers
75
Email security
70
DNS health
65
Network security
100
GDPR outside view
35
Average
72

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

Django holds a strong market position as a leading open source Python web framework, supported by a reputable non-profit foundation. Its competitive advantages include a large, active community, comprehensive documentation, and a proven track record in powering high-traffic websites. The business model relies on community contributions, donations, and sponsorships rather than direct sales. Target customers are developers and organizations seeking rapid, secure web application development. Growth indicators include ongoing releases, active forums, and community events. The partnership ecosystem includes GitHub for code hosting and various community platforms. The organization's operations emphasize transparency, community engagement, and sustainability through non-profit governance.

Security posture

The security maturity of the Django website is high, with HTTPS enforced and no visible security vulnerabilities. The site avoids exposing sensitive data and documents a process for reporting security issues. However, the absence of explicit security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options represents an area for improvement. Privacy compliance is basic, lacking clear privacy and cookie policies, which may pose compliance risks under GDPR and similar regulations. Incident response readiness is implied but not explicitly detailed on the site. Overall, the security culture appears mature but could benefit from enhanced transparency and formalization of policies.

Recommendations

  1. Implement and prominently display a comprehensive privacy policy and cookie consent mechanism to improve GDPR compliance.
  2. Add standard security headers (CSP, HSTS, X-Frame-Options) to strengthen defense against common web attacks.
  3. Publish a security.txt file to facilitate vulnerability disclosure and improve incident response transparency.
  4. Provide clear contact information for security incidents and data protection inquiries.
  5. Regularly review and update privacy and security documentation to maintain compliance with evolving regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Django Software Foundation
Description
Django is a high-level Python web framework that encourages rapid development and clean, pragmatic design. Built by experienced developers, it takes care of much of the hassle of web development, so you can focus on writing your app without needing to reinvent the wheel. It’s free and open source.
Key services
Web framework development and maintenance, Community support and engagement, Documentation and tutorials, Fundraising and sponsorship
Content quality
excellent
Branding
consistent

Technology

Stack
Python, JavaScript, RequireJS
Frameworks
Django
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Security issue reporting documented

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

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 navigation
  2. No forms detected on the homepage or main content
  3. No explicit privacy or cookie policy pages found, but code of conduct page present
  4. Strong community engagement via forums and Discord
  5. No direct contact emails or phone numbers publicly listed
  6. No visible advertising or tracking scripts detected
  7. Modern JavaScript usage with RequireJS and custom scripts
  8. HTTPS enforced with favicon and theme color meta tags
  9. Open Graph and Twitter Card metadata present for social sharing
  10. No JSON-LD structured data found in HTML
Technical notes

Notes

The website is built using modern web technologies including Python-based Django framework and JavaScript with RequireJS for module loading. The site is well-structured with semantic HTML and optimized for mobile devices and accessibility. Performance is fast with efficient resource loading from static subdomains. No CMS is detected, indicating a custom or framework-based implementation. Hosting provider details are not explicitly available. The technical infrastructure supports scalability and maintainability, though some technical debt may exist in the form of missing security headers and privacy features. Overall, the technical implementation is robust and aligned with best practices for open source project websites.
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. 71/100Medium27 findingsView report
Reviews of this site

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

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.