Skip to main content

Security report for rosenbauer.com

Rosenbauer International AG · Transportation · Austria

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

Security score

41/100

Risk levelHigh

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

Rosenbauer International AG is a globally leading manufacturer of firefighting vehicles and equipment, with a history spanning over 150 years. The company offers a comprehensive product portfolio including municipal fire trucks, airport firefighting vehicles, special industrial vehicles, firefighting systems, protective gear, and digital solutions for fleet and incident management. Their market position is strong, supported by a large international presence and a service network in over 100 countries. Technically, the website is built on TYPO3 CMS with PHP backend and uses legacy jQuery. The site is hosted behind Amazon CloudFront CDN, ensuring global availability. However, the security posture is weak due to the absence of a valid SSL/TLS certificate and lack of HTTPS enforcement, which is a critical vulnerability for any modern business website. Privacy compliance is well addressed with clear privacy and cookie policies, and GDPR compliance is indicated. Business credibility is high given the company's established brand and consistent content quality. Overall, the site is professional and content-rich but requires urgent security improvements to protect user data and maintain trust.

Scanned

This is an earlier scan of rosenbauer.com. View the latest report

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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

This scan found 14 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
70
Email security
50
DNS health
85
Network security
20
GDPR outside view
18
Average
41

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

Rosenbauer operates in the transportation sector specializing in firefighting technology. Their business model combines manufacturing with after-sales services including maintenance and refurbishment. The company targets fire departments, emergency services, and municipal and industrial clients worldwide. Their competitive advantage lies in their long-standing history, innovation leadership, and comprehensive product range. The presence of multiple subsidiaries and partner domains indicates a broad partnership ecosystem. The website supports multiple languages and regions, reflecting a global market approach. Revenue streams likely include vehicle sales, equipment, digital solutions, and service contracts. Strategic observations include a strong brand presence and diversified offerings but a need to modernize technical infrastructure and security.

Security posture

The website demonstrates a basic security posture with several HTTP security headers implemented, such as HSTS, X-Frame-Options, X-XSS-Protection, and Referrer-Policy. However, the lack of a valid SSL certificate and disabled TLS protocols represent critical security gaps that expose the site to interception and man-in-the-middle attacks. No evidence of vulnerability disclosure or incident response contacts was found, which could hinder timely handling of security incidents. The use of legacy jQuery 1.8.1 may also introduce vulnerabilities. Privacy policies and cookie consent mechanisms are in place, supporting GDPR compliance. Overall, the security maturity is low and requires immediate remediation to meet industry standards and protect business and user data.

Recommendations

  1. Install and properly configure 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 deprecated protocols to enhance security.
  3. Implement OCSP stapling and session resumption to improve SSL performance and security.
  4. Update legacy JavaScript libraries such as jQuery to current secure versions.
  5. Publish a security.txt file and provide clear incident response contact information to improve transparency and readiness.
Technical notes

Notes

The website is powered by TYPO3 CMS with PHP 7.4 backend and uses jQuery 1.8.1 on the frontend. It is served by nginx 1.25.0 and distributed via Amazon CloudFront CDN. The site includes multiple CSS and JavaScript assets, some compressed and merged for performance. SEO is supported with meta tags, Open Graph tags, and multi-language hreflang links. The site is mobile responsive and includes accessibility features such as labels on form inputs. However, performance metrics were not available, and the SSL/TLS configuration is critically lacking, which poses a risk to user trust and data security. The technical stack is somewhat dated, especially the JavaScript libraries, indicating potential technical debt and modernization opportunities.
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. 35/100High22 findingsView report
Reviews of this site

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