Skip to main content

Security report for gronda.eu

Gronda · Technology · N/a

High risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

44/100

Risk levelHigh

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

Gronda operates as a leading culinary community platform connecting chefs worldwide to share recipes, culinary creations, and educational content. The business targets professional and aspiring chefs and culinary enthusiasts, offering a mobile app and subscription-based PRO services. The platform is positioned as a top community in its niche with a strong digital presence and active social media engagement. Technically, the website is built on modern web technologies including Webflow CMS, AWS CloudFront CDN, and integrates Google Tag Manager and Weglot for analytics and multilingual support. However, performance data is missing, and inferred loading speed is slow. Security posture is weak due to the absence of a valid SSL certificate and incomplete HTTPS implementation, which poses risks to user data and trust. Privacy compliance is well addressed with clear policies and cookie consent mechanisms. Overall, the site is professional and credible but requires urgent security improvements to protect users and enhance trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
0/ 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

7 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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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 gronda.eu

This scan found 19 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
0
Security headers
30
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
44

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

Gronda's market positioning as a specialized culinary community platform leverages exclusive content and a PRO subscription model to generate revenue. The business model focuses on community engagement, educational classes, and staff hiring services. The presence of app downloads and high user ratings indicates strong user adoption. The company maintains a consistent brand and leverages partnerships with app stores and social media platforms to expand reach. Growth indicators include multilingual support and active marketing tools. The lack of explicit contact information may limit direct customer engagement but is offset by digital channels. Strategic partnerships appear limited to core platform domains.

Security posture

The current security maturity is low, primarily due to the lack of a valid SSL certificate and disabled HTTPS protocols. This exposes users to potential data interception and undermines trust. Security headers are partially implemented but critical features like HSTS enforcement, OCSP stapling, and session resumption are missing. No explicit security policies or incident response contacts are published, indicating gaps in compliance and readiness. Privacy policies and cookie consent are well implemented, reflecting awareness of GDPR requirements. The absence of vulnerability disclosure or security.txt files suggests limited transparency in security management. Immediate remediation of SSL/TLS issues and publication of security policies are recommended to improve posture.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS and protect user data.
  2. Enable and enforce HSTS with includeSubDomains and preload to prevent protocol downgrade attacks.
  3. Publish explicit security policies and incident response contacts to enhance transparency and compliance.
  4. Implement OCSP stapling and session resumption to improve security and performance.
  5. Enhance contact information availability to improve user trust and support.
Technical notes

Notes

The website is built using Webflow CMS, hosted on AWS CloudFront CDN, and integrates Google Fonts, Google Tag Manager, and Weglot for multilingual support. The design is professional with good mobile optimization and SEO practices. However, performance metrics are missing, and inferred loading speed is slow. Accessibility features are basic but present. The absence of a valid SSL certificate and incomplete HTTPS support represent significant technical debt and security risk. Modernization opportunities include upgrading SSL/TLS configuration, improving performance monitoring, and enhancing accessibility compliance.
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 gronda.eu. 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 gronda.eu.

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.