Skip to main content

Security report for dostajemrznje.org

Non-profit · N/a

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

Security score

49/100

Risk levelHigh

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

DostaJeMrznje.org is a non-commercial advocacy platform designed to enable users to report hate speech and hate-motivated acts across various public and digital spaces. The website is built as a React single-page application with a focus on simplicity and user safety, including a quick escape button to redirect users instantly to a safe site. The platform targets individuals concerned about hate speech and aims to facilitate reporting and tracking of such incidents. Technically, the site uses modern web technologies such as React and Webpack, and includes Google Fonts for styling. However, it lacks advanced SEO metadata, structured data, and comprehensive accessibility features. Security-wise, the site uses HTTPS and includes a user safety feature but lacks important security headers and published policies, which limits its security posture. No contact or business information is provided, which impacts trust and compliance evaluation. Overall, the site is functional for its purpose but would benefit from enhanced security, privacy compliance, and transparency measures.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
Checks completed
6of 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

8 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 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

    • 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

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

Keep watching dostajemrznje.org

This scan found 25 issues across 5 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
15
Email security
70
DNS health
70
GDPR outside view
35
Average
49

Not counted

  • Network security: 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

Technical appendix

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

Business context

Business profile

The website operates as a small-scale, likely non-profit or advocacy entity focused on combating hate speech. Its business model centers on providing a reporting tool rather than commercial services. The lack of contact information and formal policies suggests a lean operational structure. The platform's competitive advantage lies in its focused mission and simple user interface. There is no indication of revenue streams or partnerships. The target audience is broad, encompassing anyone affected by or witnessing hate speech. Growth potential depends on outreach and trust-building, which currently is limited by minimal transparency and lack of formal compliance documentation.

Security posture

The security maturity of the website is basic. HTTPS is enforced, and a quick escape button enhances user safety in sensitive situations. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces protection against common web attacks. No vulnerability disclosure or incident response information is provided, limiting the ability to handle security incidents effectively. The lack of privacy and cookie policies also indicates compliance gaps, particularly regarding GDPR. No analytics or tracking scripts reduce privacy risks but also limit insight into user behavior. Overall, the site is low risk but would benefit from formalizing security and privacy practices.

Recommendations

  1. Publish comprehensive privacy and cookie policies to improve transparency and GDPR compliance.
  2. Implement standard security headers to enhance protection against web vulnerabilities.
  3. Provide clear contact information including security incident contacts to improve trust and incident response readiness.
  4. Add a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  5. Enhance accessibility and SEO features to improve user experience and discoverability.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
DostaJeMrznje.org is a tool for reporting hate-motivated acts and hate speech in public spaces, social networks, internet, and media.
Key services
Reporting hate speech, Reporting hate-motivated acts, Checking status of reports
Content quality
basic
Branding
consistent

Technology

Stack
React, Webpack, Google Fonts
Frameworks
React
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • HTTPS usage assumed (URL is HTTPS)
  • Quick escape button implemented for user safety

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a simple React-based single page application focused on hate speech reporting.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No contact emails, phone numbers, or physical addresses are provided.
  4. No social media links or external business-related links except Google Fonts and a quick escape redirect to google.com.
  5. Security best practices partially implemented (HTTPS, quick escape button), but missing security headers and policies.
  6. No analytics or advertising scripts detected.
  7. No forms with explicit input fields visible in the HTML; buttons likely trigger React app modals or routes.
  8. Content is minimal but relevant to the stated purpose.
  9. No structured data (JSON-LD) or Open Graph metadata present.
  10. No WHOIS data provided; assumed privacy protected domain registration.
Technical notes

Notes

The website is built using React and bundled with Webpack, indicating a modern JavaScript-based single-page application architecture. Google Fonts are used for typography styling. The site loads CSS and JS chunks asynchronously, which is standard for React apps. There is no evidence of a CMS or backend platform from the HTML content. Performance is likely moderate given chunked assets but no explicit performance metrics are available. Mobile optimization appears good based on viewport meta tags and responsive design elements. Accessibility is basic with a noscript fallback and some ARIA labels but could be improved. SEO optimization is minimal with only a title tag and no meta description or Open Graph tags. No analytics or advertising scripts are present, indicating minimal tracking. Overall, the technical implementation is modern but basic and could be enhanced with additional metadata, accessibility, and security 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 dostajemrznje.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 dostajemrznje.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.