Skip to main content

Security report for kroeswang.at

Kröswang GmbH · Retail · Austria

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

32/100

Risk levelHigh

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

Kröswang GmbH operates as a leading Austrian wholesale supplier specializing in fresh and frozen food products for the gastronomy and retail sectors. The company maintains a strong market presence with multiple locations and a comprehensive online shop targeting business customers primarily in Austria and Germany. Their business model focuses on B2B supply with emphasis on freshness and quality, supported by a broad product range and reliable 24-hour delivery service. Technically, the website is built on TYPO3 CMS with modern marketing and analytics integrations, including Google Tag Manager and Hotjar, providing a solid digital infrastructure. However, the absence of a valid SSL/TLS certificate and lack of HTTPS severely undermines the security posture, exposing users and business operations to significant risks. While privacy and cookie policies are well implemented and GDPR compliant, the lack of published security policies and incident response mechanisms indicates room for improvement in governance. Overall, the site is professional and content-rich but requires urgent security upgrades to protect business and customer data effectively.

Scanned

NIS2 and GDPR posture

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  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 kroeswang.at

This scan found 19 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
35
Email security
50
DNS health
85
Network security
20
GDPR outside view
0
Average
32

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

Kröswang GmbH holds a strong position in the Austrian retail and gastronomy wholesale market, leveraging a large product catalog and a robust logistics network. Their online presence supports business growth and customer engagement through an integrated shop and content marketing (magazine, news). Partnerships with brands like Eisliebe and Manfreddo enhance their product portfolio and market reach. The company targets professional customers, emphasizing freshness and quality as key differentiators. The website content and supplier transparency build trust, while the absence of explicit certifications or security accreditations suggests potential areas for competitive advantage. The business appears mature and well-established, with consistent branding and professional communication.

Security posture

The website's security posture is weak due to the lack of HTTPS and a valid SSL certificate, which is a critical vulnerability that compromises data confidentiality and integrity. Security headers are partially implemented, including X-Frame-Options and cookie security flags, but the overly permissive CORS policy (allowing all origins) could expose the site to cross-origin attacks. No security or incident response policies are published, and no vulnerability disclosure or security.txt files are present. Forms use CAPTCHA to mitigate spam, but the absence of encrypted transport negates many protections. The site does not implement modern TLS protocols or session resumption, and DNSSEC and CAA records are missing, reducing DNS security. Immediate remediation is required to enable HTTPS and strengthen security controls to protect business and customer data.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Restrict CORS policy to trusted origins instead of wildcard '*' to reduce attack surface.
  4. Publish a security policy and incident response contact information, including security@ or abuse@ emails.
  5. Add a security.txt file to facilitate vulnerability disclosure and improve transparency.

Contact details published on the site

Addresses
Legal name
Kröswang GmbH
Technical notes

Notes

The website is powered by TYPO3 CMS, a mature and extensible content management system, supported by jQuery 3.5.1 and integrated with Google Tag Manager and Hotjar for analytics and user behavior tracking. The site uses Factfinder for search functionality and Google reCAPTCHA v2 for form spam protection. Hosting is on an nginx 1.19.6 server with a single IPv4 address. Performance metrics were not available, but the site appears mobile-optimized with responsive images and structured navigation. SEO is supported by meta tags and Open Graph data. However, the lack of HTTPS and modern TLS protocols is a significant technical debt and security risk. DNS configuration lacks DNSSEC and CAA records, which could be improved to enhance domain security.
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 kroeswang.at. 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 kroeswang.at.

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.