Skip to main content

Security report for fooby.ch

FOOBY · Retail · Switzerland

Medium risk. 4 critical or high findings in SSL/TLS, GDPR outside view and 1 other check.

Security score

73/100

Risk levelMedium

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

FOOBY is a culinary content platform operated under the Swiss retail giant Coop, offering recipes, cooking inspiration, and community engagement. The website targets general consumers interested in cooking and food culture, providing a rich set of features including recipe categories, cooking school content, and interactive tools like menu configurators and apps. The platform is well-branded and consistent with Coop's retail identity, positioning FOOBY as a trusted source for culinary content in Switzerland. Technically, the website employs modern web technologies including service workers, consent management via Usercentrics, and tag management with Tealium, indicating a mature digital infrastructure. However, explicit privacy policies and terms of service pages were not found in the analyzed content, which is a gap in compliance and transparency. Security posture is generally good with HTTPS and service workers, but lacks visible security headers and incident response contacts. Overall, FOOBY presents a professional, trustworthy, and content-rich platform with room for improvement in privacy and security disclosures.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 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. 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
  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

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

This scan found 21 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. The full timeline opens with your unlock code.

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
50
Email security
75
DNS health
80
Network security
100
GDPR outside view
68
Average
73

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.

Dark web exposure

Add-on

Leaked records that mention fooby.ch, from OffSeq Breach.

Total records
1
Employees
0
Customers
1
Third parties
0
Weak passwords
0%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for fooby.ch.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

FOOBY leverages Coop's strong market presence in Switzerland to deliver culinary content and services, targeting home cooks and food enthusiasts. Its business model centers on content engagement, likely supporting Coop's retail operations by driving brand loyalty and customer interaction. The presence of multiple subdomains for specialized services (little FOOBY, Swipe & Cook, Menu configurator) indicates a diversified content ecosystem. The platform uses advanced analytics and marketing tools to optimize user experience and engagement. FOOBY's competitive advantage lies in its integration with Coop's retail brand and its comprehensive culinary offerings. Growth potential exists in expanding digital services and enhancing compliance and security transparency.

Security posture

The website enforces HTTPS and uses a modern consent management platform, reflecting good baseline security and privacy practices. The use of service workers indicates progressive web app capabilities. However, the absence of explicit security headers such as Content Security Policy, HSTS, and X-Frame-Options reduces defense-in-depth. No contact information for security incidents or a vulnerability disclosure policy was found, which limits incident response readiness. No vulnerabilities or exposed sensitive data were detected in the analyzed content. Overall, the security posture is solid but could be enhanced by implementing recommended headers and publishing security policies.

Recommendations

  1. Publish a clear and comprehensive privacy policy and terms of service accessible from the main site.
  2. Implement and configure security headers including CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.
  3. Provide explicit contact information for security incidents and designate a data protection officer contact.
  4. Establish and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Regularly audit third-party scripts and tracking tools to ensure compliance with privacy regulations and minimize tracking footprint.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
FOOBY
Description
FOOBY is all about the enjoyment of cooking. Coop’s culinary platform is full of great recipe ideas, lots of know-how, and exciting reports.
Key services
Recipe database, Cooking school content, FOOBYVERSE community and stories, Menu configurator, Swipe & Cook app
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Usercentrics CMP, Tealium Tag Management, Service Workers, Modernizr, SVG graphics
Frameworks
SWC (Swiss Web Components), JSON-LD for structured data
Platforms
Web, Mobile (manifest and app store link present)
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Service worker registered
  • Consent management platform used

Analytics and tracking

Services
Google Analytics, Webtrends, Tealium
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
DoubleClick
Tracking pixels
Webtrends, Tealium
Marketing tools
Tealium Tag Management, Usercentrics CMP
Transparency
basic

Site quality

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

Key observations

  1. Website is a culinary platform associated with Coop, a major Swiss retailer.
  2. Content is rich with recipes, cooking knowledge, and community features.
  3. Good use of modern web technologies and consent management.
  4. Lacks explicit privacy policy and terms of service pages linked in the analyzed content.
  5. No direct contact information or security incident contacts found.
  6. Uses multiple external analytics and marketing services.
  7. No security headers detected in provided data; could be improved.
  8. No signs of adult or questionable content.
Technical notes

Notes

The website uses a modern tech stack with JavaScript modules, service workers, and SVG graphics for UI elements. It integrates Usercentrics for consent management and Tealium for tag management, indicating advanced marketing and privacy controls. The CMS appears to be an enterprise-grade system, likely Adobe Experience Manager, based on URL patterns and asset paths. Performance is moderate with preloading and lazy loading techniques employed. Mobile optimization is good with responsive images and viewport settings. SEO is supported by canonical links, hreflang tags, and structured data in JSON-LD format. Accessibility features are present but not exhaustively analyzed. Technical risks include missing security headers and reliance on multiple third-party tracking services.
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 fooby.ch. 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 fooby.ch.

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.