Skip to main content

Security report for pydata.org

NumFOCUS · Technology · N/a

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

Security score

69/100

Risk levelMedium

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

PyData.org is the official website for the PyData community, organized under the non-profit NumFOCUS. It serves as a hub for developers, data scientists, and researchers interested in open-source data science tools, primarily in Python. The site offers information about community events, projects, and resources, positioning itself as a key player in the open-source data science ecosystem. The business model is community-driven, focusing on education and collaboration rather than commercial sales. The domain is well-established since 2011, reinforcing its credibility and longevity in the market. Technically, the website is built on WordPress using the Divi theme, leveraging common web technologies such as jQuery and Google Fonts. It employs Cloudflare for DNS and uses Google Analytics and HubSpot for marketing and analytics. The site demonstrates moderate performance and good mobile optimization but lacks advanced accessibility features. SEO is basic but functional. From a security perspective, the site uses HTTPS with a good SSL configuration and has domain transfer protections enabled. However, it lacks DNSSEC and security headers, which are recommended for enhanced security. There are no visible privacy or cookie policies, nor incident response or vulnerability disclosure information, which are gaps in compliance and transparency. The WHOIS data is consistent and public, with no privacy protection, supporting legitimacy. Overall, PyData.org is a reputable and professional community website with solid business credibility and technical implementation. To improve, it should implement comprehensive privacy and cookie policies with consent mechanisms, enhance security headers, and publish security and incident response policies to strengthen trust and compliance.

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 Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

  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 pydata.org

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

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

PyData.org operates as a community platform under NumFOCUS, targeting data science professionals and enthusiasts. Its competitive advantage lies in its strong association with NumFOCUS and its role as a central hub for open-source data science tools and events. The business model is non-commercial, focusing on community engagement and support for open-source projects. Revenue streams likely include sponsorships, donations, and event fees. The target customer segments are developers, researchers, and data scientists globally. Growth indicators include a long domain history and integration with major analytics and marketing platforms. The partnership ecosystem includes NumFOCUS and various open-source projects. Strategic observations highlight the need for improved privacy and security transparency to align with industry best practices.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enabled and domain transfer protections in place. However, the absence of DNSSEC and security headers such as Content-Security-Policy and Strict-Transport-Security represents potential vulnerabilities. No exposed sensitive data or vulnerable libraries were detected in the HTML content. The lack of published security policies, incident response contacts, and vulnerability disclosure mechanisms indicates gaps in security governance and transparency. Compliance with GDPR and other privacy regulations is unclear due to missing privacy and cookie policies. The security culture appears limited in public documentation, suggesting room for improvement in security awareness and communication.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Implement and publish comprehensive privacy and cookie policies with user consent mechanisms.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to improve protection against common web attacks.
  4. Publish incident response and vulnerability disclosure policies, including dedicated contact channels like security@ or abuse@ emails.
  5. Regularly audit and update third-party scripts and plugins to mitigate vulnerabilities and improve overall security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
NumFOCUS
Description
PyData is a community for developers and users of open-source data science tools, organized under NumFOCUS.
Key services
Community events and conferences, Support for open-source data science projects, Educational resources and networking
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Divi Theme, jQuery, Google Fonts, Google Analytics, Cloudflare DNS
Frameworks
WordPress CMS
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited

Analytics and tracking

Services
Google Analytics, MonsterInsights
Tracking level
moderate
Privacy practices
poor

Advertising

Ad networks
Google Ads
Tracking pixels
HubSpot, Facebook Pixel
Marketing tools
MonsterInsights, HubSpot
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is a community platform for PyData under NumFOCUS.
  2. Uses WordPress CMS with Divi theme and common plugins.
  3. No explicit privacy or cookie policies found on homepage HTML.
  4. Uses multiple third-party marketing and analytics scripts.
  5. No visible contact emails or phone numbers in the HTML content.
  6. No security.txt or vulnerability disclosure information found.
  7. No incident response or security policy information found.
  8. Domain is well-registered and not privacy protected.
  9. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built on a mature and widely used CMS platform, WordPress, with the Divi theme providing a flexible design framework. It uses standard web technologies including jQuery and Google Fonts, and integrates marketing and analytics tools such as Google Analytics, HubSpot, and Facebook Pixel. Hosting and DNS are managed via Cloudflare and NameCheap, providing reliable infrastructure. Performance is moderate, with good mobile responsiveness but basic accessibility features. SEO is functional but could benefit from enhanced metadata and structured data implementation. Technical risks include reliance on multiple third-party scripts which require regular security reviews. Opportunities exist to modernize security configurations and improve compliance documentation.
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 pydata.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 pydata.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.