Skip to main content

Security report for yaskawa.de

Yaskawa · Manufacturing · Germany

Medium risk. 4 critical or high findings in Security headers and SSL/TLS.

Security score

58/100

Risk levelMedium

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

Yaskawa is a prominent provider of industrial automation solutions in Germany, specializing in products such as industrial robots, frequency converters, servomotors, and control systems. The website targets industrial and manufacturing businesses, positioning itself as a leading automation technology provider. The digital infrastructure leverages modern technologies including Bootstrap for frontend styling, Matomo for privacy-respecting analytics, and Usercentrics for cookie consent management, indicating a mature digital presence. Security posture is strong with HTTPS enforced and security headers present, although explicit privacy policies and terms of service are not found in the analyzed content. Overall, the website is professional, well-structured, and trustworthy, but could improve transparency by publishing comprehensive privacy and security policies.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 100 · Low
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

4 findings rated critical or high. Fix these first.

  1. 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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';…

  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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

Need hands-on remediation? Email guard@offseq.com

Keep watching yaskawa.de

This scan found 24 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
72
Security headers
15
Email security
70
DNS health
60
Network security
40
GDPR outside view
88
Average
58

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

Yaskawa operates in the manufacturing and technology sectors, focusing on B2B automation solutions. The company appears to have a large operational scale with a consistent brand presence. The website content is tailored to industrial clients seeking automation products and services. The use of privacy-conscious analytics and consent management tools suggests awareness of regulatory compliance, although explicit documentation is lacking. The absence of detailed contact information and security policies may limit user trust and compliance readiness. No suspicious or unrelated domains are linked, indicating a focused business ecosystem.

Security posture

The website demonstrates a solid security foundation with HTTPS and standard security headers implemented. The use of Matomo analytics reduces privacy risks compared to third-party trackers. Cookie consent is actively managed via Usercentrics, supporting GDPR compliance. However, the lack of a published privacy policy, terms of service, and vulnerability disclosure policy represents compliance gaps. No exposed sensitive data or vulnerable libraries were detected in the analyzed content. Incident response contact channels are not explicitly provided, which could hinder timely security communication. Overall, the security posture is good but can be enhanced by adding formal policies and contact points.

Recommendations

  1. Publish a comprehensive privacy policy page clearly outlining data processing and user rights.
  2. Add terms of service and security policy pages to improve transparency and legal compliance.
  3. Provide explicit contact information for security incidents, including abuse and security email addresses.
  4. Implement and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Enhance website accessibility features to improve compliance and user experience for all visitors.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Yaskawa
Description
Leistungsstarke Automatisierungslösungen: Industrieroboter, Frequenzumrichter, Servomotoren, Steuerungssysteme und vieles mehr
Key services
Industrieroboter, Frequenzumrichter, Servomotoren, Steuerungssysteme
Content quality
good
Branding
consistent

Technology

Stack
Matomo, Google Tag Manager, Usercentrics (consent management), Bootstrap CSS
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism
  • Use of Matomo for privacy-respecting analytics

Analytics and tracking

Services
Matomo, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Matomo
Marketing tools
Usercentrics
Transparency
good

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Cookie consent is implemented with Usercentrics.
  3. Use of Matomo analytics indicates privacy-conscious tracking.
  4. No explicit privacy policy or terms of service pages detected in the provided content.
  5. No contact emails or phone numbers explicitly found in the HTML snippet.
  6. Website uses modern frontend technologies and appears professionally designed.
  7. No security.txt or vulnerability disclosure policy found.
  8. WHOIS data is minimal but consistent with domain usage.
Technical notes

Notes

The website uses a modern technology stack including Bootstrap for responsive design, Matomo for analytics, and Usercentrics for consent management. The CMS appears to be Pimcore, inferred from HTML class names and structure. Performance is moderate with preloading of fonts and scripts, and mobile optimization is good. SEO is supported by proper meta tags and Open Graph data. Security headers and HTTPS are properly configured. There is room for improvement in accessibility and formal documentation of privacy and security policies. No critical technical debt or vulnerabilities were detected in the provided content.
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 yaskawa.de. 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 yaskawa.de.

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.