Skip to main content

Security report for qimiq.com

QimiQ Handels GmbH · Retail · Austria

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

Security score

48/100

Risk levelHigh

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

QimiQ Handels GmbH operates a well-established retail website focused on food products and cooking ingredients, targeting both consumers and professional chefs. The company offers a range of products such as QimiQ Classic, Sahne-Basis, Whip, Vegan, and Tiramisu, complemented by recipe content, professional workshops, and a newsletter. The website is multilingual and professionally designed, reflecting a consistent brand presence and active engagement through social media and marketing tools. Technically, the site is built on WordPress with modern plugins and frameworks, leveraging Cloudflare for CDN and caching. However, a critical security gap exists due to the absence of HTTPS/SSL, exposing users to potential risks. Privacy compliance is strong, with comprehensive policies and consent mechanisms in place. Overall, the site demonstrates good business credibility and user experience but requires urgent security improvements.

Scanned

NIS2 and GDPR posture

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

6 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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 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 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 qimiq.com

This scan found 18 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
0
Security headers
40
Email security
50
DNS health
80
Network security
100
GDPR outside view
18
Average
48

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

QimiQ positions itself as a versatile food product provider with a dual focus on end consumers and professional users. Its business model integrates product sales with content marketing and educational workshops, enhancing customer engagement and loyalty. The company maintains a medium-sized operation based in Austria, with a clear digital presence supported by SEO and multilingual capabilities. Partnerships and integrations with platforms like Shopify and HubSpot indicate a mature marketing ecosystem. The active social media channels and customer magazine further support brand visibility and trust. No parent or subsidiary companies were identified, suggesting an independent operation focused on its niche market.

Security posture

The website's security posture is currently weak due to the lack of HTTPS/SSL encryption, which is a fundamental requirement for protecting user data and ensuring trust. While some security headers like X-Content-Type-Options and X-Frame-Options are present, the absence of TLS protocols, HSTS, and OCSP stapling significantly undermines the site's security. No explicit security policies or incident response contacts are published, and no vulnerability disclosure or security.txt files are found. The use of Cloudflare provides some protection at the network level, but the missing SSL certificate is a critical vulnerability that must be addressed immediately to prevent data interception and maintain compliance with privacy regulations.

Recommendations

  1. Implement a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Configure HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Upgrade server to support modern TLS protocols (TLS 1.2 and TLS 1.3) and enable OCSP stapling.
  4. Add comprehensive security headers such as Content-Security-Policy and Referrer-Policy.
  5. Publish a clear security policy and incident response contact information on the website.
  6. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  7. Regularly audit third-party scripts and plugins for security vulnerabilities.
  8. Enhance accessibility features to improve compliance and user experience.
  9. Maintain transparency in data collection and retention policies aligned with GDPR.
  10. Continue leveraging marketing and analytics tools while ensuring user privacy and consent.

Contact details published on the site

Addresses
Legal name
QimiQ Handels GmbH
Technical notes

Notes

The website is built on a WordPress CMS platform using a custom Lightpress theme framework and several advanced plugins including Yoast SEO Premium, Advanced Custom Fields Pro, and TranslatePress for multilingual support. It integrates modern JavaScript libraries such as Alpine.js and Swiper.js for interactive UI components. Hosting and CDN services are provided by Cloudflare, which offers caching and some security features. Despite these modern technologies, the site lacks HTTPS, which is a major technical deficiency. Performance metrics are not available, but the site appears optimized for mobile with responsive design and SEO best practices implemented. The presence of multiple external scripts and tracking services indicates a mature digital marketing infrastructure, though it requires careful management to avoid privacy risks.
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 qimiq.com. 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 qimiq.com.

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.