Skip to main content

Security report for yokogawa.com

Yokogawa Electric Corporation · Energy · Japan

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

Security score

38/100

Risk levelHigh

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

Yokogawa Electric Corporation is a century-old global enterprise specializing in measurement, control, and information technologies for industrial sectors such as energy and manufacturing. The company maintains a comprehensive and professionally designed website that serves a global audience with extensive product, solution, and corporate information. Technically, the site employs modern web technologies including AngularJS and integrates analytics and monitoring tools like Google Tag Manager and New Relic. However, the absence of a valid SSL certificate and HTTPS support significantly weakens its security posture, exposing users to potential risks. Privacy policies and cookie consent mechanisms are well implemented, reflecting good compliance with GDPR standards. Overall, the website demonstrates high business credibility and content quality but requires urgent security improvements to align with best practices.

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

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

      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

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

This scan found 17 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
30
Email security
50
DNS health
50
Network security
100
GDPR outside view
0
Average
38

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention yokogawa.com, from OffSeq Breach.

Total records
2,683
Employees
58
Customers
1,724
Third parties
901
Weak passwords
12%

Latest record dated 2026-06-12 · 49 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for yokogawa.com.

Select it in the checkout above.

Masked preview

  • –yokogawa.com2026-06-12
  • –myproject.yokogawa.com2026-06-06
  • –myproject.yokogawa.com2026-06-06
  • –auth.jp.yokogawa.com2026-05-29
  • –partner.yokogawa.com2026-05-16

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Yokogawa holds a strong market position as an established leader in industrial automation and control solutions. Its business model focuses on B2B services across multiple sectors including energy, chemical, and life sciences. The website highlights a broad portfolio of products and services, investor relations, and sustainability initiatives, indicating a mature and transparent corporate structure. Partnerships such as with KBC Advanced Technologies enhance its ecosystem. The company targets industrial clients seeking advanced automation and control technologies, supported by a global regional presence. The digital presence is professional and content-rich, supporting brand trust and customer engagement.

Security posture

The website's security posture is currently basic and requires significant enhancement. While some security headers like X-Frame-Options and HttpOnly cookies are present, the lack of HTTPS and an invalid SSL certificate is a critical vulnerability. This exposes the site and its users to interception and man-in-the-middle attacks. No evidence of incident response or vulnerability disclosure policies was found, which could impact readiness for security events. The site does not implement DNSSEC or HSTS, missing opportunities to strengthen domain and transport security. Privacy compliance is good, but security best practices need urgent attention to protect user data and maintain trust.

Recommendations

  1. Implement a valid SSL/TLS certificate and enforce HTTPS across the entire site.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  3. Deploy DNSSEC to protect against DNS spoofing and improve domain integrity.
  4. Publish a clear security policy and vulnerability disclosure program to enhance transparency and incident readiness.
  5. Regularly audit and update security headers and cookie settings to align with modern security standards.
Technical notes

Notes

The website is built on a modern technology stack including Apache server, AngularJS framework, and uses Amazon CloudFront as a CDN. It integrates Google Tag Manager and New Relic for analytics and performance monitoring. The site is mobile optimized and accessible with good SEO practices. However, performance metrics are not available, and the absence of HTTPS is a major technical shortfall. The CMS appears to be a custom or proprietary system (YokoCMS). The site structure is complex with extensive navigation and multilingual support, indicating a mature digital infrastructure. Technical debt is moderate due to legacy AngularJS usage and missing SSL, suggesting 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

Reviews of this site

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