Skip to main content

Security report for pykonik.org

Technology · Poland

Partial score · DNS & email only

72/100

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

Pykonik is a well-established community organization focused on Python programming enthusiasts in Kraków, Poland. The website serves as a hub for event announcements, speaker presentations, and community engagement. It has a strong local presence with a history dating back to 2008, supported by active social media channels and meetup events. The business model revolves around organizing and promoting Python user group meetings and related social gatherings. Technically, the site is built on a modern stack including Python, Django, Bootstrap, and uses Google Analytics for visitor tracking. The site is mobile-optimized and provides a good user experience with clear navigation and relevant content. Security posture is moderate; HTTPS is enabled but lacks advanced security headers and DNSSEC is not configured. Privacy compliance is weak due to absence of privacy and cookie policies and no visible consent mechanisms. Overall, the site is trustworthy but could improve in security and compliance areas.

Scanned

3 of 7 checks could not complete. The site may be unreachable or blocking automated scans, so the results below cover only what could be checked. Try a rescan later.

NIS2 and GDPR posture

NIS2 outside view
Not assessed
GDPR outside view
Not assessed

Both readouts depend on the site's pages, which could not be loaded in this scan.

Priority findings

2 findings rated critical or high. Fix these first.

  1. 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
    • 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 pykonik.org

This scan found 15 issues across 4 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
42
Email security
70
DNS health
75
Network security
100
Average
72

Not counted

  • Security headers: did not complete in this scan.
  • GDPR outside view: did not complete in this scan.
  • 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 pykonik.org, from OffSeq Breach.

No leaked records found

Breach holds no records for pykonik.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

Pykonik operates as a local technology community group, targeting Python developers and enthusiasts primarily in Kraków. Its competitive advantage lies in its long-standing presence and active event schedule, fostering face-to-face knowledge exchange. Revenue streams are likely minimal or community-funded, focusing on event sponsorships and partnerships. The partnership ecosystem includes Meetup, Discord, and other Python community organizations in Poland. Growth indicators include regular event listings and active social media engagement. The business model is non-commercial, emphasizing community building and knowledge sharing.

Security posture

The website demonstrates a basic security maturity level with HTTPS enabled and domain registration protections in place. However, it lacks critical security headers such as Content-Security-Policy and HSTS, and DNSSEC is not enabled, which could expose it to DNS spoofing risks. The exposure of the Google Maps API key in client-side code is a minor vulnerability. No privacy or cookie policies are present, indicating compliance gaps with GDPR. Incident response and security policies are not disclosed. Overall, the security posture is adequate for a community site but requires improvements to meet modern standards and regulatory requirements.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy with GDPR compliance.
  2. Enable DNSSEC for the domain to enhance DNS security.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and HSTS to improve protection against common web attacks.
  4. Secure Google Maps API key usage by restricting it to authorized domains or moving sensitive keys to server-side.
  5. Consider publishing a security policy and incident response contact information to improve transparency and trust.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Pykonik to cykliczne spotkania pasjonatów języka programowania Python z Krakowa i okolic.
Key services
Organizing Python user group meetings, Hosting tech talks and presentations, Community networking events
Content quality
good
Branding
consistent

Technology

Stack
Python 3.13.4, Django 5.2.3, Bootstrap CSS, jQuery, Google Analytics, Google Maps API
Frameworks
Django, Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
55/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML
  • Use of client-side analytics scripts

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a community-driven Python user group based in Kraków, Poland.
  2. Content is primarily in Polish with clear event listings and community engagement.
  3. No privacy or cookie policies found, which is a compliance gap.
  4. No visible security headers or advanced security configurations.
  5. Use of Google Analytics and Google Tag Manager for tracking without visible cookie consent.
  6. No contact phone numbers or physical addresses explicitly provided.
  7. Social media presence is strong with multiple official channels linked.
  8. No forms with sensitive data collection detected on the homepage.
  9. Google Maps API key is exposed in client-side JavaScript.
  10. Domain WHOIS data is consistent and trustworthy.
Technical notes

Notes

The website uses a modern technology stack with Python 3.13.4 and Django 5.2.3, combined with Bootstrap for responsive design and jQuery for client-side scripting. Google Analytics and Google Tag Manager are used for visitor tracking. The site is hosted on infrastructure associated with GoDaddy.com, LLC for domain registration and DNS hosted at mcg.pl. Performance is moderate with good mobile optimization and basic accessibility features. SEO is supported by proper meta tags and Open Graph data. Technical risks include exposed API keys and lack of DNSSEC. There is no CMS detected, indicating a custom or framework-based site. Overall, the technical implementation is solid but could benefit from enhanced 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 pykonik.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 pykonik.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.