Skip to main content

Security report for ecookie.nl

Yellowgrape and Hipex · E-commerce · Netherlands

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

Security score

57/100

Risk levelMedium

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

Ecookie.nl is a Dutch website offering a free, easy-to-install cookie banner solution designed to help e-commerce businesses comply with the GDPR (AVG) regulations. Developed collaboratively by the e-commerce agency Yellowgrape and Magento hosting specialist Hipex, the service targets webshops seeking to manage cookie consent efficiently and in their own branding style. The website provides a registration form for users to create accounts and download a whitepaper on privacy laws for webshops. The site is well-structured, mobile-optimized, and presents a professional image consistent with its niche market position. From a technical perspective, the website uses modern web technologies including HTML5, CSS3, JavaScript, and the Symfony PHP framework for user registration. Hosting is likely provided by Hipex, a Magento hosting specialist, indicating a reliable infrastructure. The site performs moderately well with good mobile responsiveness and basic accessibility features. However, explicit security headers are not detected, and no detailed privacy or security policies are published, which are areas for improvement. Security posture is adequate with HTTPS usage and secure form handling including CSRF tokens and mandatory consent checkboxes. No vulnerabilities or exposed sensitive data were identified in the provided content. The absence of published privacy and cookie policies reduces privacy compliance confidence. No incident response or vulnerability disclosure information is available, limiting transparency in security management. Overall, ecookie.nl presents a trustworthy and professional service for GDPR cookie compliance in the Dutch e-commerce sector. Strategic improvements in publishing comprehensive privacy and security policies, enhancing security headers, and providing incident response contacts would strengthen its security posture and compliance standing.

Scanned

NIS2 and GDPR posture

GDPR outside view
80/ 100 · Low
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

5 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 Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

Keep watching ecookie.nl

This scan found 22 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. 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
95
Security headers
15
Email security
60
DNS health
70
Network security
20
GDPR outside view
80
Average
57

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

Ecookie.nl operates as a niche service provider in the GDPR compliance space for e-commerce businesses in the Netherlands. Its partnership with Yellowgrape and Hipex leverages expertise in e-commerce strategy and Magento hosting, respectively, creating a synergistic offering. The business model is based on providing a free tool to attract and support clients, potentially driving business to the partners' core services. The target customers are webshops needing simple cookie consent solutions. The website's content and branding are consistent and professional, supporting a credible market position. The lack of direct contact emails or phone numbers suggests a primarily digital self-service model. The partnership ecosystem is clearly indicated, enhancing trust. Growth potential lies in expanding features and formalizing compliance documentation.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enabled and secure form practices including CSRF protection and mandatory consent checkboxes. However, the absence of explicit security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces defense-in-depth. No vulnerability disclosure or incident response policies are published, limiting transparency and preparedness. No exposed sensitive data or vulnerable libraries were detected in the analyzed content. The site lacks published privacy and cookie policies, which are critical for GDPR compliance. Overall, the security posture is functional but could be significantly improved by adopting best practices in security headers, policy transparency, and incident management.

Recommendations

  1. Publish comprehensive privacy and cookie policies clearly accessible on the website.
  2. Implement and configure security headers including CSP, HSTS, and X-Frame-Options.
  3. Establish and publish a vulnerability disclosure policy and incident response contact information.
  4. Enhance transparency by providing contact emails and phone numbers for support and security inquiries.
  5. Regularly audit and update the technology stack to ensure no vulnerable libraries or components are used.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Yellowgrape and Hipex
Description
Ecookie is a free and simple cookie banner solution developed by e-commerce agency Yellowgrape and Magento hosting specialist Hipex to help webshops become AVG/GDPR compliant by managing cookies and online tracking.
Key services
Cookie banner for GDPR compliance, Cookie management and consent configuration, Customizable branding and easy installation
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • Use of HTTPS assumed (URL is https://)
  • Secure form with CSRF token present
  • Required consent checkbox on registration form

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. Content is focused on GDPR cookie compliance for e-commerce.
  3. No explicit privacy or cookie policy pages found, but cookie consent mechanism is present.
  4. Registration form collects email and password with CSRF token and consent checkbox.
  5. No contact emails or phone numbers explicitly listed on the site.
  6. Partner logos for Hipex and Yellowgrape indicate collaboration.
  7. No social media links or external marketing/analytics scripts detected.
  8. No security headers detected in provided data; security posture could be improved.
  9. Website uses Symfony framework for user registration.
  10. No explicit security or incident response policies published.
Technical notes

Notes

The website is built using standard web technologies (HTML5, CSS3, JavaScript) and the Symfony PHP framework for user registration functionality. Hosting is likely provided by Hipex, a Magento hosting specialist, suggesting a robust infrastructure. The site is mobile-optimized and has a moderate performance profile. SEO and accessibility features are basic but present. The use of CSRF tokens in forms indicates attention to security in user input handling. No advanced CMS or third-party analytics/tracking scripts were detected, reducing complexity and potential privacy risks. Opportunities exist to improve technical maturity by adding security headers, enhancing accessibility, and expanding SEO optimization.
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 ecookie.nl. 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 ecookie.nl.

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.