Skip to main content

Security report for favv-afsca.be

Federaal Agentschap voor de veiligheid van de voedselketen · Government · Belgium

Medium risk. 4 critical or high findings in GDPR outside view and Security headers.

Security score

75/100

Risk levelMedium

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

The website belongs to the Belgian Federal Agency for the Safety of the Food Chain, a government entity responsible for food safety regulation and public information. The site serves as a language selection portal, supporting Dutch, French, German, and English, reflecting Belgium's multilingual nature. The agency operates under the auspices of the Prime Minister's Chancellery, as confirmed by WHOIS data, with a domain age dating back to 2000, indicating a well-established presence. Technically, the website is built on Drupal 10, leveraging modern web technologies including jQuery and accessibility frameworks such as WAI-ARIA. It employs Matomo analytics with a GDPR-compliant cookie consent mechanism, ensuring user privacy and transparency. The site demonstrates good mobile optimization, accessibility, and SEO practices, contributing to a positive user experience. From a security perspective, the site uses HTTPS and implements cookie consent but lacks explicit security headers and published security policies or incident response contacts. No vulnerabilities or exposed sensitive data were detected in the analyzed content. The WHOIS data aligns perfectly with the website's official government status, reinforcing trust and legitimacy. Overall, the website is professional, trustworthy, and compliant with privacy regulations, though it could improve by publishing detailed security policies and enhancing security headers. There are no indications of adult or questionable content, making it safe for general audiences.

Scanned

NIS2 and GDPR posture

GDPR outside view
55/ 100 · Medium
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

4 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. 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 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 favv-afsca.be

This scan found 17 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
95
Security headers
55
Email security
75
DNS health
70
Network security
100
GDPR outside view
55
Average
75

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 agency occupies a critical role in the Belgian government ecosystem, focusing on food safety regulation and public communication. Its market position is that of an essential government service provider with a large operational scale. The business model is non-commercial, centered on regulatory oversight and public service. The multilingual approach targets a broad audience including citizens, food industry stakeholders, and regulatory partners. The use of official government domains and branding enhances credibility. The agency's digital presence is modern and compliant, though it lacks direct contact information on this page, possibly centralized elsewhere. No commercial partnerships or subsidiaries are evident from the data provided.

Security posture

The website demonstrates a moderate to good security posture with mandatory HTTPS and GDPR-compliant cookie consent. However, the absence of explicit security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces the overall security robustness. No incident response or vulnerability disclosure information is published, which is a gap in transparency and readiness. The use of Matomo analytics with consent is a positive privacy practice. No signs of vulnerabilities or exposed sensitive data were found. The WHOIS data confirms the domain's legitimacy, reducing risk of phishing or spoofing. Overall, security maturity is adequate but could be enhanced with published policies and improved header configurations.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to strengthen defense against common web attacks.
  2. Publish a dedicated security policy and incident response contact information to improve transparency and readiness.
  3. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  4. Ensure all pages include clear contact information for user support and security concerns to enhance trust.
  5. Regularly audit third-party scripts and libraries to avoid potential vulnerabilities and maintain compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Federaal Agentschap voor de veiligheid van de voedselketen
Description
Belgian Federal Agency responsible for food chain safety, providing information and services related to food safety regulation and compliance.
Key services
Food safety regulation, Public information on food safety, Language selection for accessibility
Content quality
good
Branding
consistent

Technology

Stack
Drupal 10, jQuery, OreJime (cookie consent), WAI-ARIA patterns, Matomo analytics
Frameworks
Drupal
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • Cookie consent with opt-in/out
  • No exposed sensitive data in HTML
  • Use of HTTPS (implied by canonical URL)

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Transparency
basic

Site quality

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

Key observations

  1. Website is a language selection landing page for a Belgian federal agency.
  2. Content is fully accessible with no blocking or WAF challenges.
  3. Uses Drupal 10 CMS with modern frontend technologies.
  4. Cookie consent mechanism is implemented and GDPR compliant.
  5. No contact emails or phone numbers found on this page.
  6. No explicit security or incident response policies published on this page.
  7. Matomo analytics used for tracking with consent requirement.
  8. No advertising or affiliate programs detected.
  9. No social media links found on this page.
  10. WHOIS data confirms official government ownership and long domain age.
Technical notes

Notes

The website is built on Drupal 10, a modern and widely supported CMS, ensuring a solid technical foundation. It uses jQuery and WAI-ARIA patterns for accessibility, indicating attention to inclusive design. The presence of OreJime for cookie consent shows compliance with privacy regulations. Matomo analytics is used for user tracking with consent, avoiding reliance on third-party trackers like Google Analytics. The site is mobile optimized and has good SEO metadata. Performance is moderate, likely due to the extensive CSS and JS assets loaded. No broken elements or errors were detected. Hosting appears to be managed by Belgian government infrastructure, enhancing reliability and security. Opportunities exist to optimize performance and enhance security headers.
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 favv-afsca.be. 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 favv-afsca.be.

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.