Skip to main content

Security report for walloniebelgiquetourisme.be

VISITWallonia · Hospitality · Belgium

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

Security score

59/100

Risk levelMedium

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

VISITWallonia.be is the official tourism website for the Wallonia region in Belgium, providing travel information, destination guides, and event listings to tourists and visitors. The site targets a broad audience interested in exploring Wallonia's cultural and natural attractions. The business operates as a regional tourism promotion entity, leveraging multilingual support to cater to diverse visitors. Technically, the website is built on Drupal 7 CMS with integration of modern JavaScript libraries and embedded social media content via Flockler. The site demonstrates good design quality, mobile optimization, and SEO practices, although some accessibility features are basic. Security posture is moderate with HTTPS likely enabled but lacking explicit security headers and formal security policies. Privacy compliance is weak due to absence of visible privacy and cookie policies or consent mechanisms. Overall, the domain registration is consistent and trustworthy, supporting the legitimacy of the business. Strategic improvements in privacy compliance, security headers, and incident response transparency are recommended to enhance trust and security.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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. 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

      Third-party services without privacy policy

      Detected services: Facebook, Twitter, LinkedIn, YouTube, Google APIs

      What to do: Document all third-party data sharing in your privacy policy

  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';…

  3. 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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching walloniebelgiquetourisme.be

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. 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
67
Security headers
70
Email security
70
DNS health
65
Network security
40
GDPR outside view
40
Average
59

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Brand lookalikes

Add-on

Domains that imitate walloniebelgiquetourisme.be and could be used for phishing or spoofed email, tracked in OffSeq Breach.

Tracked
1
Registered
1
Resolving
1
High or critical
0

Last checked 2026-06-20

Masked preview

  • wa••••••.belgiquetourisme.beLowsubdomain

See the full lookalike list

A one-off add-on that lists up to 20 of the highest-risk lookalikes of walloniebelgiquetourisme.be with registration, mail-server, certificate and DNS signals.

Select it in the checkout above.

Lookalike data refreshes continuously. Monitoring on Breach alerts you when a variant is registered, gains a mail server or starts serving HTTPS.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

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 serves as a key digital platform for promoting tourism in Wallonia, positioning itself as the official source for travel inspiration and information. Its multilingual approach and partnerships with sister sites in other languages indicate a comprehensive regional marketing strategy. The business model focuses on providing free informational content to attract visitors, likely supported by regional government or tourism boards. The presence of multiple language domains suggests a broad target market across Europe. The site’s use of Drupal and embedded social media content reflects a mature digital infrastructure. However, the lack of explicit contact information and privacy policies may limit user trust and engagement. The partnership ecosystem includes related language sites and event-focused subdomains, reinforcing its role in regional tourism promotion.

Security posture

The website exhibits a moderate security posture with HTTPS presumably enabled, but no explicit security headers such as Content-Security-Policy or X-Frame-Options were detected in the HTML content. There is no evidence of vulnerability disclosure policies or incident response contacts, which are important for security maturity. The absence of privacy and cookie policies also indicates compliance gaps with GDPR and other data protection regulations. No exposed sensitive data or vulnerable libraries were identified in the provided content. The site would benefit from implementing security best practices including security headers, formal privacy and cookie policies with consent mechanisms, and clear incident response channels to improve its security and compliance standing.

Recommendations

  1. Implement comprehensive privacy and cookie policies with user consent mechanisms to ensure GDPR compliance.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to enhance protection against common web attacks.
  3. Publish a vulnerability disclosure policy and provide clear incident response contact information to improve security transparency.
  4. Conduct a security audit to identify and remediate any potential vulnerabilities or outdated libraries.
  5. Enhance accessibility features and provide clear contact information to improve user trust and engagement.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
VISITWallonia
Description
Voyager en Wallonie, découvrir nos destinations et profiter de nos bons plans. Laissez-vous inspirer par nos idées de séjours et visites dans le sud de la Belgique, tout près de vous.
Key services
Tourism information, Travel inspiration, Destination guides, Event listings
Content quality
good
Branding
consistent

Technology

Stack
Drupal 7, jQuery, Bootstrap, Flockler embed
Frameworks
Drupal
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
50/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Marketing tools
Flockler embed
Transparency
basic

Site quality

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

Key observations

  1. Website is an official tourism portal for Wallonia region in Belgium.
  2. Content is primarily in French with multilingual support links.
  3. No explicit privacy, cookie, or terms of service policies found in the provided HTML snippet.
  4. No contact emails or phone numbers explicitly found in the provided content.
  5. Uses Drupal 7 CMS with several custom and third-party modules.
  6. Includes social media integration via embedded content (Flockler).
  7. No security headers or explicit security policies detected in the HTML.
  8. No vulnerability disclosure or incident response information found.
  9. No signs of adult or questionable content.
  10. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built on Drupal 7 CMS, utilizing jQuery and Bootstrap frameworks, with embedded social media content via Flockler. The site loads CSS and JavaScript assets from a CDN (cdn.wbtourisme.be) and Google Fonts, indicating a distributed content delivery approach. The HTML includes proper meta tags for SEO and social media sharing (Open Graph), but lacks JSON-LD structured data. Performance is moderate with preconnect and dns-prefetch hints for external resources. Mobile optimization is good with viewport meta tags and responsive design elements. Accessibility is basic, with skip links and some ARIA roles, but could be improved. No explicit security headers or advanced security configurations were observed. Overall, the technical infrastructure is stable but could benefit from modernization and enhanced security practices.
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 walloniebelgiquetourisme.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 walloniebelgiquetourisme.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.