Skip to main content

Security report for webasto.com

Webasto Group · Transportation · Germany

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

Security score

51/100

Risk levelMedium

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

Webasto Group is a mature, enterprise-level global automotive supplier specializing in innovative roof systems, battery solutions, heating, and cooling products. The company is positioned among the top 100 automotive suppliers worldwide, serving automotive manufacturers and end customers with a broad portfolio of products and services. The website is professionally designed, leveraging modern technologies such as Adobe Experience Manager and React, providing a rich user experience with clear navigation and relevant content. However, a critical security issue is the lack of a valid SSL certificate, resulting in no HTTPS enforcement, which significantly impacts the security posture. Privacy and cookie policies are present, indicating awareness of compliance requirements, but the absence of a cookie consent mechanism and security policy pages suggests room for improvement in privacy compliance and transparency. Overall, the domain registration is consistent and trustworthy, supporting the legitimacy of the business.

Scanned

NIS2 and GDPR posture

GDPR outside view
15/ 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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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 webasto.com

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. 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
55
Email security
50
DNS health
85
Network security
100
GDPR outside view
15
Average
51

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

Webasto operates in the transportation and energy sectors, focusing on electromobility and automotive components. Its business model includes B2B supply to automotive manufacturers and B2C services such as dealer locators and product finders. The company demonstrates strong market positioning with a mature domain and strong domain protection. The website content targets automotive manufacturers, end customers, and partners, emphasizing innovation, sustainability, and customer proximity. The use of Adobe Experience Manager and React indicates a modern digital infrastructure supporting scalability and content management. The absence of explicit contact emails and phone numbers suggests a preference for controlled communication channels via contact forms.

Security posture

The website implements several security headers such as X-Frame-Options and X-Content-Type-Options, and the server supports no vulnerable SSL/TLS protocols. However, the SSL certificate is invalid or missing, and HTTPS is not properly enforced, which is a critical vulnerability. HSTS header is present but not fully enabled, reducing its effectiveness. There is no public security policy or incident response information, and no security.txt file was found. These gaps indicate a moderate security maturity level with significant room for improvement, especially in SSL configuration and incident response transparency.

Recommendations

  1. Obtain and deploy a valid SSL certificate to enable HTTPS and protect user data in transit.
  2. Fully enable HSTS with includeSubDomains and preload directives to enforce HTTPS.
  3. Implement a cookie consent mechanism to comply with GDPR and enhance user privacy transparency.
  4. Publish a comprehensive security policy and incident response contact information to improve trust and readiness.
  5. Consider adding a security.txt file to facilitate vulnerability reporting and improve security culture.
Technical notes

Notes

The website is built on Adobe Experience Manager CMS with React components, indicating a modern and scalable architecture. It uses Adobe Launch for tag management and tracking. The hosting appears to be via Fastly CDN, providing performance and availability benefits. The site is mobile optimized with good accessibility and SEO practices. However, the lack of a valid SSL certificate and incomplete HSTS implementation are technical risks that could impact user trust and security. Performance metrics were not available, but the use of CDN and modern tech suggests moderate to good performance. The site uses extensive imagery and video content managed via Adobe Dynamic Media.
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 webasto.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 webasto.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.