Skip to main content

Security report for toffifee.ca

Storck Canada · Retail · Canada

Medium risk. 4 critical or high findings in Email security, GDPR outside view and 1 other check.

Security score

70/100

Risk levelMedium

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

The website www.toffifee.ca represents the Canadian online presence of the Toffifee confectionery brand, owned by Storck. It provides product information, brand history, and consumer engagement content targeted at Canadian customers. The site is built on TYPO3 CMS and uses modern JavaScript libraries and Piwik PRO for analytics. The website is well-designed, mobile-optimized, and provides clear navigation and relevant content. Privacy and cookie policies are present and GDPR compliant, with a cookie consent mechanism implemented. However, no direct company contact emails or phone numbers are found on the homepage, only a contact form. The WHOIS data for the domain is unavailable, which limits the ability to verify domain registration legitimacy and age, but the website content aligns with the known brand, mitigating some concerns. Security posture is good with HTTPS enforced and no exposed sensitive data, though additional security headers and explicit security policies could improve the security maturity.

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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

  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. 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 toffifee.ca

This scan found 23 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
62
Security headers
80
Email security
40
DNS health
70
Network security
100
GDPR outside view
68
Average
70

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

Toffifee Canada operates as a medium-sized retail brand website under the parent company Storck. The business model focuses on brand marketing and consumer engagement for confectionery products. The website links to partner brands such as Merci and Werther's Original, indicating a broader partnership ecosystem within Storck's portfolio. The site targets Canadian consumers interested in confectionery, leveraging a professional and consistent brand presence. Revenue streams are likely indirect through retail sales channels supported by brand awareness. The website's digital presence is modern but could benefit from enhanced contact transparency and security documentation to strengthen business credibility.

Security posture

The website demonstrates a good security posture with HTTPS enabled and a cookie consent mechanism in place, supporting GDPR compliance. No security policy or incident response information is published, which is a gap in transparency. No vulnerabilities or exposed sensitive data were detected in the HTML content. The use of Piwik PRO analytics indicates moderate user tracking, balanced with privacy compliance. Security headers beyond HTTPS are not evident, suggesting room for improvement. Overall, the site is secure for general consumer use but would benefit from enhanced security best practices and published policies to improve trust and incident readiness.

Recommendations

  1. Implement and publish a formal security policy and incident response contact information on the website.
  2. Add additional HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Enhance transparency by providing direct company contact emails and phone numbers where appropriate.
  4. Regularly review and update privacy and cookie policies to maintain GDPR and other compliance standards.
  5. Consider obtaining and displaying relevant security certifications or trust badges to improve user confidence.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Storck Canada
Description
Toffifee is a confectionery brand offering a unique combination of hazelnut, nougat cream, caramel and chocolate. The website promotes Toffifee products and brand history targeted at Canadian consumers.
Key services
Product information, Brand storytelling, Consumer engagement
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, jQuery, RequireJS, Slick Carousel, Piwik PRO Analytics
Frameworks
TYPO3 CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Piwik PRO
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Piwik PRO
Marketing tools
Piwik PRO Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professionally presented and consistent with a confectionery brand.
  3. No direct company contact emails or phone numbers found on the homepage; contact form is available.
  4. Privacy and cookie policies are present and GDPR compliant.
  5. No explicit security policy or incident response information found.
  6. WHOIS data is missing, which limits domain legitimacy verification.
  7. Use of modern CMS TYPO3 and analytics via Piwik PRO.
  8. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on TYPO3 CMS, a robust open-source content management system, and uses modern JavaScript libraries including jQuery, RequireJS, and Slick Carousel for UI components. Analytics are handled via Piwik PRO, indicating a focus on privacy-conscious tracking. The site is mobile-optimized with responsive images and good navigation clarity. Performance is moderate, with asynchronous loading of scripts and deferred JavaScript. No major technical debt or deprecated technologies were detected. Hosting provider details are not explicit in the HTML content. Overall, the technical infrastructure supports a professional and user-friendly experience but could be enhanced with improved accessibility features and additional 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 toffifee.ca. 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 toffifee.ca.

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.