Skip to main content

Security report for pythonsummit.org

Fundacja Academic Partners · Technology · Poland

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

Security score

67/100

Risk levelMedium

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

Python Summit is a specialized conference targeting Python developers, data engineers, architects, and DevOps professionals, primarily in Poland but with international reach. It is organized by the Fundacja Academic Partners foundation and associated Python communities such as PyData and PyWaw. The event offers both online and onsite participation, with a comprehensive agenda featuring expert speakers and practical case studies. The conference also includes a job fair and offers multipass tickets granting access to related conferences, enhancing its value proposition. Technically, the website employs modern web technologies including AngularJS, Google Tag Manager, Facebook Pixel, and Swiper.js for UI components. It is hosted with DNS managed by Cloudflare and uses HTTPS, ensuring secure communications. The site is mobile-optimized and provides a good user experience with clear navigation and professional design. Analytics and marketing tools are extensively used, with appropriate cookie consent mechanisms in place. From a security perspective, the site enforces HTTPS and uses clientTransferProhibited domain status to prevent unauthorized transfers. However, DNSSEC is not enabled, and advanced security headers like CSP are not explicitly observed. There is no published security policy or incident response contact, which could be improved. Privacy and cookie policies are present and GDPR compliance is indicated through consent banners. Overall, the website presents a professional and trustworthy image with a solid technical foundation and good privacy practices. The domain is newly registered, consistent with the event timeline, and no suspicious indicators are found. Strategic improvements in security headers, DNSSEC, and incident response transparency would enhance the security posture further.

Scanned

NIS2 and GDPR posture

GDPR outside view
80/ 100 · Low
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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching pythonsummit.org

This scan found 26 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
62
Security headers
15
Email security
70
DNS health
75
Network security
100
GDPR outside view
80
Average
67

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention pythonsummit.org, from OffSeq Breach.

No leaked records found

Breach holds no records for pythonsummit.org right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The Python Summit operates in the technology sector as a niche event organizer focusing on Python programming language professionals. Its business model revolves around conference ticket sales, sponsorships, and partnerships with related events. The conference targets developers, data scientists, architects, and DevOps engineers, offering them educational content, networking opportunities, and job fair access. The event leverages partnerships with other conferences to provide multipass tickets, increasing its market appeal. The presence of recognized communities like PyData and PyWaw strengthens its market position. The organization appears small but well-connected within the Python ecosystem in Poland. The website content and structure reflect a mature digital presence with clear branding and professional communication.

Security posture

The website demonstrates a moderate to good security maturity level. HTTPS is enforced, and domain transfer protections are in place. However, DNSSEC is not enabled, which is a recommended best practice for DNS security. The absence of explicit security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces protection against certain web attacks. No public security policy or incident response contact information is provided, which limits transparency and readiness for security incidents. The use of third-party analytics and marketing scripts introduces potential privacy risks, though mitigated by consent mechanisms. Overall, the security posture is adequate for an event website but could benefit from enhancements in DNS security, header policies, and incident response disclosures.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS integrity and security.
  2. Publish a security.txt file with clear vulnerability disclosure and incident response contacts.
  3. Implement and enforce security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Provide explicit incident response and security policy information on the website.
  5. Regularly review and audit third-party scripts to minimize privacy and security risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Fundacja Academic Partners
Description
Python Summit is a conference dedicated to Python language professionals including developers, data engineers, architects, and DevOps. It is organized by PyData and PyWaw communities and includes practical case studies and a job fair called Python Expo.
Key services
Conference events (online and onsite), Networking and matchmaking, Job fair (Python Expo), Multipass access to related conferences
Content quality
good
Branding
consistent

Technology

Stack
AngularJS (ng-app, ng-scope), Google Tag Manager, Google Analytics, Facebook Pixel, Swiper.js, FontAwesome, Cloudflare DNS
Frameworks
AngularJS
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • Cookie consent banner implemented

Analytics and tracking

Services
Google Analytics, Google Tag Manager, Facebook Pixel
Tracking level
extensive
Privacy practices
good

Advertising

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

Site quality

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

Key observations

  1. Website is a professional conference site dedicated to Python developers and related professionals.
  2. Content is rich with detailed agenda, speakers, and event information.
  3. Use of modern web technologies and analytics tools is evident.
  4. Privacy and cookie policies are present with consent mechanisms.
  5. No direct contact emails or phone numbers publicly listed; contact via form.
  6. No explicit security or incident response policies published.
  7. Domain is newly registered but consistent with event schedule.
  8. No suspicious or malicious indicators found.
Technical notes

Notes

The website uses AngularJS framework for frontend rendering, combined with modern UI libraries like Swiper.js and FontAwesome icons. It integrates Google Tag Manager, Google Analytics, and Facebook Pixel for tracking and marketing purposes. The hosting and DNS are managed via Cloudflare, providing reliable infrastructure and DNS management. The site is mobile-optimized and uses responsive design principles. Performance is moderate, with external dependencies on CDN-hosted libraries. No CMS is detected, suggesting a custom-built or static site approach. The technical stack is appropriate for the event's needs but could be modernized by upgrading AngularJS to a newer framework version for better maintainability and security.
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 pythonsummit.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 pythonsummit.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.