Skip to main content

Security report for rath.at

Aug. RATH jun. Gmbh · Manufacturing · Austria

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

Security score

32/100

Risk levelHigh

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

RATH Austria is a well-established manufacturer specializing in high-quality chamotte stones and related refractory products for heating and stove systems, with a history spanning over 130 years. The company targets stove builders, dealers, and industrial clients primarily in Austria and Europe. Their website is built on TYPO3 CMS and provides comprehensive product and service information, including planning services for stove builders. However, the technical infrastructure shows critical security gaps, notably the absence of HTTPS, which exposes users to significant risks. The site employs some security headers but lacks modern SSL/TLS protocols and DNS records, indicating potential configuration issues. Privacy compliance is partial, with a privacy policy and terms of service present but no cookie consent mechanism. Overall, the business credibility is solid, but the security posture requires urgent improvement to protect user data and maintain trust.

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

7 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 rath.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. The full timeline opens with your unlock code.

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
50
Email security
50
DNS health
50
Network security
40
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

RATH holds a strong market position as a traditional European manufacturer in the refractory materials sector, focusing on B2B sales to stove builders and dealers. Their business model revolves around manufacturing and providing planning services, supported by a professional website with clear navigation and multilingual support. The company is part of the larger RATH-Group, indicating a broader corporate structure. Their digital presence includes social media channels on LinkedIn, Xing, and YouTube, enhancing brand visibility. However, the lack of DNS A/AAAA records and missing HTTPS may impact operational reliability and customer trust. The company should address these technical issues to maintain competitive advantage and comply with evolving digital standards.

Security posture

The website's security posture is weak due to the complete absence of HTTPS and SSL/TLS encryption, which is a critical vulnerability. While some security headers like X-Frame-Options, X-Content-Type-Options, and X-XSS-Protection are implemented, they cannot compensate for the lack of encrypted communication. No HSTS, OCSP stapling, or session resumption mechanisms are in place. The DNS configuration is incomplete, lacking essential records, which may affect domain resolution and email delivery. No vulnerability disclosure policy or incident response contacts are provided, limiting transparency and preparedness. Immediate implementation of HTTPS with a valid certificate and DNS record correction is essential to mitigate risks and comply with security best practices.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate to secure all website traffic.
  2. Configure DNS records properly, including A, AAAA, MX, and NS records, to ensure domain reliability.
  3. Add a cookie consent mechanism to comply with GDPR and enhance privacy transparency.
  4. Enable HSTS header with includeSubDomains and preload to enforce secure connections.
  5. Publish a vulnerability disclosure policy and provide incident response contact information.

Contact details published on the site

Addresses
Legal name
Aug. RATH jun. Gmbh
Technical notes

Notes

The website uses Apache server and TYPO3 CMS with a custom theme and multiple JavaScript and CSS resources. The site is multilingual with German as the primary language and English as an alternate. The absence of DNS A/AAAA records suggests use of a proxy or CDN, but this is not confirmed. Performance metrics are unavailable, but the site appears well-structured with good navigation and mobile optimization. SEO is supported by canonical and hreflang tags. However, the lack of HTTPS and incomplete DNS setup represent significant technical debt and risk. Modernizing the security infrastructure and ensuring proper DNS configuration are critical to maintaining operational stability and user trust.
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 rath.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 rath.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.