Skip to main content

Security report for zomerfolk.nl

Hospitality · Netherlands

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

Security score

63/100

Risk levelMedium

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

Zomerfolk.nl is the official website for the Rapalje Zomerfolk Festival held in Groningen, Netherlands. The site primarily serves as an informational and ticketing platform for the folk music festival, targeting folk music enthusiasts and local attendees. The business model revolves around event promotion and ticket sales, with a niche market position in the regional festival space. The website is built on WordPress using the Divi theme and WooCommerce for e-commerce functionality, supplemented by Google Adsense for advertising and Mailchimp for marketing communications. Technical infrastructure is modern and includes HTTPS and DNSSEC for security, but lacks some advanced security headers and formal privacy and cookie policies. The site demonstrates good mobile optimization and user experience but has room for improvement in privacy compliance and security best practices. The domain registration is consistent and transparent, supporting the legitimacy of the business.

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

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

    • 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

    • 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

  2. 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 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 zomerfolk.nl

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

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 festival operates in the hospitality sector, focusing on cultural events and entertainment. Its competitive advantage lies in its established presence since 2013 and association with the band Rapalje, appealing to a dedicated folk music audience. Revenue streams likely include ticket sales, merchandise, and sponsorships. The target customer segment is regional festival-goers and folk music fans. The website's partnership ecosystem includes Google Adsense and Mailchimp, indicating reliance on established marketing and advertising platforms. Strategic observations suggest the need to enhance privacy compliance and security posture to build greater trust and meet regulatory requirements.

Security posture

The website employs HTTPS and DNSSEC, which are strong indicators of secure communication and DNS integrity. Google reCAPTCHA is used to mitigate automated abuse. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options reduces protection against common web attacks. No evidence of a security policy, incident response contacts, or vulnerability disclosure mechanisms were found, indicating gaps in security governance and transparency. The site does not expose sensitive data or use vulnerable libraries based on the provided content. Overall, the security maturity is moderate but could be significantly improved by implementing recommended headers, formal policies, and disclosure practices.

Recommendations

  1. Implement comprehensive privacy and cookie policies with clear GDPR compliance statements.
  2. Add security headers including Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  3. Publish a security policy and incident response contact information to improve transparency.
  4. Create and host a security.txt file to facilitate vulnerability disclosures.
  5. Enhance accessibility features and conduct regular security audits to maintain compliance and security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Website for Zomerfolk, a folk festival in Groningen associated with the band Rapalje.
Key services
Festival information, Ticket sales, Event updates
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Divi Theme, WooCommerce, Google reCAPTCHA, Google Adsense, TranslatePress
Frameworks
WooCommerce, Divi
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enabled
  • DNSSEC enabled
  • Google reCAPTCHA implemented

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Ad networks
Google Adsense
Marketing tools
Mailchimp
Transparency
basic

Site quality

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

Key observations

  1. Website is a WordPress-based event site for a folk festival in the Netherlands.
  2. No explicit privacy, cookie, or terms of service policies found in the provided content.
  3. Uses Google Adsense and Mailchimp for marketing and advertising.
  4. Security best practices partially implemented; HTTPS and DNSSEC enabled, but missing some security headers.
  5. No contact emails or phone numbers explicitly found in the provided HTML snippet.
  6. No security.txt or vulnerability disclosure policy detected.
  7. Good domain age and registration transparency support legitimacy.
Technical notes

Notes

The website is built on a widely used CMS (WordPress) with the Divi theme and WooCommerce plugin, indicating a standard e-commerce and content management setup. It uses Google Fonts, Adsense, reCAPTCHA, and Mailchimp integrations, reflecting a modern marketing and advertising stack. Performance is moderate with good mobile responsiveness. The site lacks advanced SEO and accessibility features but maintains a professional design and navigation structure. Hosting provider details are not explicit. Technical risks include potential plugin vulnerabilities if not regularly updated and missing security headers that could expose the site to certain attacks.
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 zomerfolk.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 zomerfolk.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.