Skip to main content

Security report for deliveroo.be

Deliveroo · Transportation · Belgium

Low risk. 2 critical or high findings in Security headers and SSL/TLS.

Security score

81/100

Risk levelLow

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

Deliveroo.be is a well-established online food and grocery delivery platform operating in Belgium, part of the global Deliveroo brand founded in 2014. The website offers consumers a seamless experience to order from local restaurants and shops, supported by mobile apps for iOS and Android. The business model focuses on connecting customers with local partners while managing delivery logistics. The site demonstrates a strong market position with consistent branding and comprehensive service offerings including corporate meal solutions and rider recruitment. Technically, the website leverages modern web technologies such as React and Next.js, supported by Google Tag Manager and OneTrust for privacy compliance. The site is hosted on a CDN, ensuring fast performance and excellent mobile optimization. Accessibility and SEO practices are well implemented, contributing to a professional user experience. From a security perspective, the site enforces HTTPS and employs multiple security headers, reflecting a mature security posture. However, explicit security policies and incident response contacts are not publicly available, representing an area for improvement. Privacy compliance is robust with clear policies and consent mechanisms aligned with GDPR requirements. Overall, Deliveroo.be presents a low-risk profile with strong business credibility, technical maturity, and privacy compliance. Strategic recommendations include publishing dedicated security and incident response policies and enhancing transparency around vulnerability disclosures to further strengthen trust and security culture.

Scanned

This is an earlier scan of deliveroo.be. View the latest report

NIS2 and GDPR posture

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

2 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 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. 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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching deliveroo.be

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
60
Email security
82
DNS health
70
Network security
100
GDPR outside view
100
Average
81

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

Deliveroo.be operates in the transportation and e-commerce sectors, focusing on food and grocery delivery services in Belgium. The company benefits from a strong brand presence and international backing by Deliveroo Holdings Ltd. Its competitive advantages include a large partner network, integrated delivery logistics, and a user-friendly digital platform. Revenue streams likely include delivery fees, service charges, and partnerships with restaurants and shops. The target customer segment is broad, encompassing individual consumers and corporate clients. Growth indicators include active rider recruitment and promotional meal deals. The partnership ecosystem is evident through dedicated portals for restaurants and riders. The company maintains a professional online presence with consistent branding and comprehensive legal and privacy documentation.

Security posture

Deliveroo.be demonstrates a solid security posture with enforced HTTPS, use of security headers such as HSTS, CSP, and X-Frame-Options, and implementation of cookie consent mechanisms. No exposed sensitive data or vulnerable libraries were detected in the analyzed content. However, the absence of a publicly available security policy and incident response contact details limits transparency. There is no evidence of a security.txt file or vulnerability disclosure program. Compliance with GDPR is indicated by privacy and cookie policies. The site’s security maturity is good but could be enhanced by publishing explicit security governance documents and providing clear channels for security incident reporting.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Provide explicit incident response contact information, such as a security@ or abuse@ email address.
  3. Implement and publish a security.txt file to facilitate responsible vulnerability disclosure.
  4. Regularly review and audit third-party scripts and libraries to mitigate potential vulnerabilities.
  5. Enhance transparency by detailing data retention policies and security certifications if applicable.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Deliveroo
Description
We deliver your takeouts or essential groceries from the best-rated local partners straight to your door. Download our app or order online. Food. We Get It.
Key services
Food delivery, Grocery delivery, Restaurant partnership, Rider recruitment, Corporate meal solutions
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, Google Tag Manager, OneTrust Cookie Consent, Polyfill.io, Content Delivery Network (CDN)
Frameworks
Next.js
Platforms
Web, iOS, Android
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of security headers
  • Cookie consent with opt-in mechanism
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics (via Google Tag Manager)
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
OneTrust Cookie Consent
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed and fully functional.
  2. Strong presence of privacy and cookie policies with consent mechanisms.
  3. No direct company emails or phone numbers found on the homepage; contact is via forms.
  4. Social media presence includes Facebook and Twitter official pages.
  5. Use of modern web technologies and frameworks.
  6. Security best practices are implemented but lack explicit security policy and incident response info.
  7. No suspicious or malicious content detected.
  8. WHOIS data supports legitimacy and business history.
Technical notes

Notes

The website is built using modern JavaScript frameworks, primarily React and Next.js, ensuring server-side rendering and good SEO performance. It uses Google Tag Manager for analytics and OneTrust for cookie consent management, indicating compliance with privacy regulations. Hosting is via a CDN (roocdn.com), contributing to fast load times and global availability. The site is mobile-optimized with responsive design and accessibility features. No CMS was explicitly detected, suggesting a custom or proprietary content management solution. The technical infrastructure is robust, with no visible technical debt or deprecated technologies. Opportunities exist to further improve technical documentation and security transparency.
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. 79/100Low22 findingsView report
Reviews of this site

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