Skip to main content

Security report for rewe-group.at

REWE Group in Österreich · Retail · Austria

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

Security score

40/100

Risk levelHigh

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

REWE Group in Österreich is a major retail group operating multiple supermarket and retail brands across Austria and several European countries. The company has a long-standing history of over 70 years and manages well-known brands such as BILLA, PENNY, and BIPA. The website presents comprehensive corporate and sustainability information targeting customers and stakeholders in Austria and Europe. Technically, the site uses modern frontend technologies like Alpine.js and FontAwesome and is likely powered by the Statamic CMS. However, the site lacks a valid SSL certificate and does not serve content over HTTPS, which is a critical security shortfall. Security headers are partially implemented, but the absence of TLS protocols and valid certificates significantly reduces the security posture. Privacy compliance is well addressed with clear privacy and cookie policies and consent mechanisms. Business credibility is high due to consistent branding, detailed corporate information, and alignment with WHOIS data. Overall, the site is professional and content-rich but requires urgent security improvements to enable HTTPS and strengthen its security configuration.

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

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

      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

    • 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 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 rewe-group.at

This scan found 16 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
65
Email security
50
DNS health
85
Network security
40
GDPR outside view
0
Average
40

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

The REWE Group operates in the retail sector with a strong presence in Austria and other European markets. Its business model revolves around supermarket retail, brand management, and logistics. The group consolidates several retail brands under one umbrella, targeting a broad customer base. The website reflects a mature digital presence with multilingual support and detailed corporate governance and sustainability initiatives. Partnerships and initiatives such as 'Blühendes Österreich' indicate active engagement in environmental and social responsibility. The company leverages social media channels for outreach and recruitment. The domain registration and WHOIS data are consistent with the company's Austrian roots and business claims, supporting legitimacy and trust. The absence of direct contact emails or phone numbers on the site suggests a preference for contact forms and controlled communication channels.

Security posture

The website's security posture is weak due to the lack of a valid SSL certificate and absence of HTTPS support, exposing users to potential interception risks. While some security headers like HSTS, X-Frame-Options, X-XSS-Protection, and X-Content-Type-Options are present, their effectiveness is undermined without proper TLS configuration. No vulnerabilities such as Heartbleed or POODLE were detected, but the missing encryption is a critical issue. There is no evidence of published security policies or incident response contacts, which could hinder timely handling of security incidents. The site uses modern JavaScript frameworks and analytics tools but should prioritize securing transport layers and enhancing security governance documentation.

Recommendations

  1. Implement and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable and configure modern TLS protocols (TLS 1.2 and TLS 1.3) and strong cipher suites.
  3. Ensure HSTS header is properly configured and consistent with SSL deployment.
  4. Publish clear security policies and incident response contact information on the website.
  5. Regularly audit and update security headers and monitor for vulnerabilities.
  6. Enhance transparency by providing direct contact emails or phone numbers for customer and security inquiries.
  7. Maintain and update privacy and cookie policies to reflect evolving regulations.
  8. Optimize website performance to improve load times and user experience.
  9. Continue leveraging structured data and SEO best practices to maintain strong digital presence.
  10. Strengthen user trust by showcasing certifications and compliance badges if applicable.
Technical notes

Notes

The website is built on a modern technology stack including nginx web server, Alpine.js for frontend interactivity, and FontAwesome for icons. It uses Statamic CMS as inferred from livewire and statamic references in scripts. The site is mobile optimized and accessible with good SEO metadata including Open Graph and JSON-LD structured data. Performance metrics are not provided but inferred slow load time suggests room for optimization. Hosting appears to be on a cloud or VPS provider with IP 159.69.43.195. External scripts include Fathom Analytics for privacy-focused tracking and CookieLaw.org for cookie consent management. The site uses multiple language versions with hreflang tags for localization. Overall, the technical implementation is modern but requires urgent SSL/TLS configuration and performance tuning.
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 rewe-group.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 rewe-group.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.