Skip to main content

Security report for cryptofest.cz

cryptofest · Technology · N/a

Medium risk. 3 critical or high findings in GDPR outside view and SSL/TLS.

Security score

68/100

Risk levelMedium

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

The website is a public GitHub repository page for the project 'cryptofest/web'. It serves as a platform for source code hosting and collaboration within the developer community. The repository is hosted on GitHub, a leading platform in software development, indicating a credible and established presence. The site targets developers and contributors interested in the project. Technically, the site leverages modern web technologies including React and GitHub's asset delivery network, ensuring good performance, mobile optimization, and accessibility. Security posture is strong with HTTPS enforced and domain registration protected against unauthorized changes, although DNSSEC is not enabled. However, the site lacks explicit privacy, cookie, and terms of service policies, as well as direct contact information, which are areas for improvement. Overall, the site is trustworthy for its intended purpose but could enhance compliance and user trust by adding relevant policies and contact details.

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

3 findings rated critical or high. Fix these first.

  1. 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

  2. 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 cryptofest.cz

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
57
Security headers
75
Email security
80
DNS health
90
Network security
40
GDPR outside view
68
Average
68

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 repository is positioned as an open source project under the 'cryptofest' organization on GitHub. It benefits from GitHub's platform features such as version control, issue tracking, and collaboration tools. The business model is community-driven open source development, with no direct commercial transactions evident on the page. The target audience includes developers and open source contributors. The project has moderate visibility with 31 stars and 2 forks, indicating some community interest. There is no evidence of partnerships or subsidiaries related to this repository. The lack of explicit business information and contact details suggests a primarily community-maintained project rather than a commercial enterprise.

Security posture

The website enforces HTTPS with a valid SSL certificate, ensuring encrypted communication. Domain registration includes protective statuses such as clientDeleteProhibited, clientTransferProhibited, and clientUpdateProhibited, which prevent unauthorized domain modifications. However, DNSSEC is not enabled, which could enhance DNS security. No security headers were detected in the HTML content, and there is no published security policy or incident response information. The absence of a security.txt file or vulnerability disclosure policy limits transparency for security researchers. No vulnerabilities or exposed sensitive data were identified in the content. Overall, the security posture is adequate for a public code repository but could be improved with additional security headers and published policies.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a comprehensive privacy policy and cookie policy on the repository or associated website.
  3. Add contact information or a dedicated security contact email for incident reporting.
  4. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Consider adding a security.txt file to facilitate vulnerability disclosures and improve security transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
cryptofest
Description
Contribute to cryptofest/web development by creating an account on GitHub.
Key services
Source code hosting, Version control, Collaboration tools
Content quality
basic
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, React, GitHub platform
Frameworks
React
Platforms
GitHub
Performance
fast
Mobile
good
Accessibility
good
SEO
basic

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain status includes clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited

Analytics and tracking

Services
GitHub internal analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a public GitHub repository page for 'cryptofest/web'.
  2. No explicit privacy, cookie, or terms of service policies found on the page.
  3. No direct contact emails or phone numbers found in the content.
  4. Site uses HTTPS with valid SSL configuration.
  5. No DNSSEC enabled on domain.
  6. No security.txt or vulnerability disclosure information found.
  7. Site content is primarily code repository metadata and navigation.
  8. No advertising or affiliate marketing detected.
  9. Site uses modern web technologies including React and GitHub's internal assets.
  10. No adult or NSFW content detected.
Technical notes

Notes

The website is hosted on GitHub, leveraging its infrastructure and content delivery network for fast and reliable performance. The front-end uses React and standard web technologies, ensuring good mobile responsiveness and accessibility. The site includes meta tags for SEO and social sharing (Open Graph), although no JSON-LD structured data was detected. The absence of CMS or third-party advertising tools indicates a clean technical environment focused on code hosting. Performance is expected to be fast due to GitHub's optimized hosting. There is no evidence of technical debt or outdated libraries in the visible content. The site could benefit from enhanced SEO metadata and accessibility improvements such as ARIA landmarks and roles.
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 cryptofest.cz. 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 cryptofest.cz.

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.