Skip to main content

Security report for publicprocurement.be

BOSA · Government · Belgium

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

Security score

60/100

Risk levelMedium

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

The website www.publicprocurement.be appears to be a government-related eProcurement platform operated by BOSA, a Belgian government entity. However, the website content is currently inaccessible, showing only a JavaScript loading spinner and a message indicating that JavaScript is required. No meaningful content, contact information, or policies are available on the landing page. The WHOIS data for the domain is not accessible and returns a 'NOT ALLOWED' status, preventing extraction of registrar, creation, expiry, or registrant details. This lack of WHOIS transparency reduces trust and legitimacy verification. Technically, the site uses modern frontend technologies such as Vue.js and Vuetify, indicating a contemporary tech stack. However, due to the blocked content, performance, accessibility, and SEO aspects cannot be assessed. Security headers and SSL configuration details are not available from the provided data, and no security or privacy policies are detected. The security posture is weak due to the lack of accessible content and missing security headers. Privacy compliance cannot be confirmed as no privacy or cookie policies are found. The domain's WHOIS data inconsistency and blocked content suggest potential access restrictions or security controls limiting public visibility. Overall, the site is likely intended for authenticated or internal users only, limiting public access. Strategic recommendations include improving public-facing transparency, publishing privacy and security policies, ensuring WHOIS data availability for trust, and implementing robust security headers and SSL configurations.

Scanned

NIS2 and GDPR posture

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

8 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 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 publicprocurement.be

This scan found 25 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
77
Security headers
15
Email security
60
DNS health
80
Network security
100
GDPR outside view
25
Average
60

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 domain www.publicprocurement.be is associated with BOSA, a Belgian government agency responsible for eProcurement services. The business model focuses on providing a digital platform for public procurement processes, targeting public sector organizations and suppliers in Belgium. The market position is that of a government service provider with a specialized niche in eProcurement. The platform likely facilitates tendering, bidding, and contract management for public contracts. No additional business details, partnerships, or subsidiaries are visible due to limited content. The lack of accessible contact information and policies limits insights into operational maturity and customer engagement strategies.

Security posture

The current security posture assessment is limited by the lack of accessible website content and absence of security headers in the provided data. The site uses HTTPS as inferred from the URL but no SSL configuration details are available. No security policies, incident response contacts, or vulnerability disclosures are found. The WHOIS data is inaccessible, which reduces domain trustworthiness. No forms or input fields are detected, minimizing attack surface from the public page. Overall, the security maturity appears low from a public perspective, with recommendations to publish security policies, implement security headers, and improve WHOIS transparency.

Recommendations

  1. Publish comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  2. Ensure WHOIS data is accessible and accurate to enhance domain legitimacy and trust.
  3. Implement and verify HTTPS with strong SSL/TLS configuration and security headers.
  4. Provide clear contact information and incident response channels for security reporting.
  5. Improve public website content accessibility and transparency to support user engagement and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. WHOIS query response indicates 'NOT ALLOWED' status with message 'Use only approved characters.' The website HTML content is minimal, showing only a loading spinner and a message that JavaScript is required. This suggests content is blocked or inaccessible, possibly due to security or access restrictions. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Company
BOSA
Description
The website appears to be related to BOSA's eProcurement services, likely a government-related procurement platform for public sector entities in Belgium.
Key services
eProcurement services
Content quality
poor
Branding
moderate

Technology

Stack
Vue.js, Uppy (file uploader)
Frameworks
Vuetify

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is minimal and blocked behind a JavaScript loading screen.
  2. No visible contact information, policies, or business details on the landing page.
  3. WHOIS data is inaccessible and returns a 'NOT ALLOWED' status.
  4. No external links or social media profiles found in the HTML.
  5. Uses modern frontend technologies (Vue.js, Vuetify) but no content is rendered.
  6. No security headers or SSL configuration details available from provided data.
  7. No privacy or cookie policies detected.
  8. No forms or data collection elements detected.
  9. Website likely intended for authenticated or internal users only.
Technical notes

Notes

The website employs a modern frontend technology stack including Vue.js and Vuetify UI framework, along with Uppy for file uploads. The HTML structure includes modulepreload and module scripts indicating a modular JavaScript approach. However, the site content is minimal and blocked behind a JavaScript loading spinner, preventing full rendering and content delivery. No CMS or hosting provider information is discernible. Performance, accessibility, and SEO optimizations cannot be assessed due to lack of visible content. The site appears to rely heavily on client-side rendering and requires JavaScript enabled for functionality.
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

Earlier scans of this domain

  1. 60/100Medium34 findingsView report
Reviews of this site

Share your experience with publicprocurement.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 publicprocurement.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.