Skip to main content

Security report for thalia.at

Thalia · Retail · Austria

High risk. 8 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

The website thalia.at represents an established retail brand focused on books and related products in the German-speaking market, primarily Austria. The site is currently inaccessible due to a Cloudflare security challenge page that requires users to complete a security check before accessing the online shop. This limits the ability to analyze the full content and business details. The technical infrastructure includes Cloudflare for CDN and WAF services and Mimecast for email security, indicating a professional setup. However, the absence of a valid SSL certificate and HTTPS support on the analyzed page is a critical security weakness. The site lacks visible privacy, cookie, or terms of service policies, and no contact information is presented on the challenge page, which negatively impacts trust and compliance assessments.

Scanned

This is an earlier scan of thalia.at. View the latest report

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

This scan found 15 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
55
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
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

Thalia.at operates in the retail sector with a focus on e-commerce for books and related products. The presence of multiple logos for associated brands suggests a broad retail network. The domain registration and DNS setup are consistent with legitimate business operations, using reputable providers like Hetzner and Cloudflare. The lack of visible business information and policies on the landing page is likely due to the security challenge blocking access rather than an absence of such information on the full site. The business model is typical for large retail e-commerce platforms targeting German-speaking customers. Partnerships with Mimecast and Cloudflare indicate attention to email and web security infrastructure.

Security posture

The security posture is currently weak due to the lack of a valid SSL certificate and HTTPS support on the analyzed page, which is a critical issue. The site benefits from multiple security headers and uses Cloudflare's WAF to mitigate threats, as evidenced by the security challenge page. No known vulnerabilities such as Heartbleed or POODLE are detected. The absence of HSTS and OCSP stapling further reduces security robustness. The security challenge page helps prevent automated attacks but also blocks content access, limiting user experience and analysis. Overall, the site demonstrates some security best practices but requires urgent improvements in SSL/TLS configuration and transparency of privacy and security policies.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable legacy protocols.
  3. Implement HSTS with includeSubDomains and preload to enforce secure connections.
  4. Publish clear privacy, cookie, and terms of service policies accessible without security challenges.
  5. Provide visible and verified contact information including support and security incident contacts.
  6. Review Cloudflare WAF settings to balance security with user accessibility and SEO.
  7. Enable OCSP stapling and session resumption to improve SSL performance and security.
  8. Conduct a full security audit to identify and remediate any hidden vulnerabilities.
Technical notes

Notes

The website uses Cloudflare as a CDN and WAF, with DNS hosted on Cloudflare name servers and email security via Mimecast. The HTTP headers indicate strong security policies such as cross-origin policies and permissions policy restricting many browser features. However, the SSL configuration is non-functional with no valid certificate and no TLS protocols enabled, resulting in no HTTPS support. The page content is minimal and serves as a security challenge, blocking access to the actual site content. Performance data is unavailable due to the blocked content. The site appears to be built with standard HTML and inline CSS, with no detected CMS or JavaScript frameworks beyond Cloudflare challenge scripts. The technical setup is professional but incomplete due to SSL issues and content blocking.
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

Earlier scans of this domain

  1. 73/100Medium28 findingsView report
  2. 73/100Medium28 findingsView report
Reviews of this site

Share your experience with thalia.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 thalia.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.