Skip to main content

Security report for stojimezaukrajinou.cz

Non-profit · Czech Republic

Medium risk. 10 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

55/100

Risk levelMedium

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

The website 'Stojíme za Ukrajinou' is a volunteer-driven non-profit initiative established in 2022 to support Ukraine following the Russian invasion. It serves as an informational and solidarity platform promoting crowdfunding projects aiding Ukrainian defenders and civilians. The site is modest in size and scope, targeting the general public interested in humanitarian support. Technically, the website uses a simple, clean HTML structure with Google Fonts and Plausible Analytics for privacy-conscious visitor tracking. Hosting and DNS are managed via Cloudflare, indicating a reliable infrastructure. However, the site lacks advanced security headers and explicit privacy or cookie policies, which are important for compliance and trust. No contact information or formal business details are provided, reflecting its grassroots nature rather than a commercial enterprise. Overall, the site is functional, fast, and accessible but could improve in privacy compliance and security best practices.

Scanned

NIS2 and GDPR posture

GDPR outside view
10/ 100 · Critical
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

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

  2. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  3. 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 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';…

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

Keep watching stojimezaukrajinou.cz

This scan found 27 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
72
Security headers
30
Email security
40
DNS health
75
Network security
100
GDPR outside view
10
Average
55

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 project operates as a small non-profit entity focused on humanitarian aid and solidarity with Ukraine. It leverages partnerships with organizations like Česko.Digital and several crowdfunding platforms to amplify its impact. The business model is based on volunteer efforts and public donations rather than commercial revenue. Its market position is grassroots and community-driven, with a clear mission to support Ukraine through digital means. The absence of formal business registrations or contact details aligns with its volunteer nature. Growth potential depends on continued public interest and partnerships. The ecosystem includes trusted Czech digital and humanitarian organizations, enhancing credibility.

Security posture

Security maturity is basic. The use of Cloudflare nameservers suggests some level of protection and performance optimization. The site uses HTTPS (implied by external resources), but no explicit security headers were detected in the provided data, which could expose it to common web vulnerabilities. There is no evidence of vulnerability disclosure policies or incident response contacts, limiting transparency and readiness. The absence of privacy and cookie policies also indicates compliance gaps with GDPR. No forms or user input fields reduce attack surface but also limit user engagement. Overall, the security posture is adequate for a small informational site but should be enhanced to improve trust and compliance.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy with GDPR compliance details.
  2. Add standard security headers such as Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options.
  3. Provide clear contact information including an email address for general and security-related inquiries.
  4. Consider adding a vulnerability disclosure policy or security.txt file to improve transparency and incident response readiness.
  5. Regularly audit and update third-party scripts and dependencies to avoid vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
A volunteer-driven project supporting Ukraine in response to the 2022 Russian invasion, promoting solidarity and crowdfunding initiatives to aid defenders and civilians affected by the war.
Key services
Information dissemination, Crowdfunding support, Solidarity promotion
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, Google Fonts, Plausible Analytics, Cloudflare DNS
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • Use of Cloudflare nameservers
  • HTTPS implied by external resources

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Plausible Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is a small volunteer-driven non-profit project supporting Ukraine.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers provided on the main page.
  4. Uses Plausible Analytics for privacy-focused tracking.
  5. No security headers detected in provided data; HTTPS usage assumed but not confirmed.
  6. Content is in Czech language and focused on humanitarian aid and solidarity.
  7. External links point to relevant partner organizations and crowdfunding platforms.
  8. No forms or data collection fields detected in the HTML content.
  9. No social media links explicitly found in the provided content.
  10. No structured data (JSON-LD, Open Graph) metadata present.
Technical notes

Notes

The website is built with clean, modern HTML and CSS, using Google Fonts for typography and Plausible Analytics for privacy-friendly visitor tracking. The hosting infrastructure leverages Cloudflare DNS, which likely provides CDN and DDoS protection benefits. The site is lightweight and fast loading, with good mobile optimization and basic accessibility. However, it lacks advanced SEO metadata such as Open Graph or JSON-LD structured data, which could improve search engine visibility and social sharing. No CMS or complex frameworks are detected, indicating a static or simple site architecture. The absence of forms or interactive elements reduces complexity but also limits user engagement. Overall, the technical implementation is solid for a small informational site but could be enhanced with SEO and security improvements.
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 stojimezaukrajinou.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 stojimezaukrajinou.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.