Skip to main content

Security report for dryield.com

DR YIELD software & solutions GmbH · Technology · Austria

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

Security score

42/100

Risk levelHigh

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

DR YIELD software & solutions GmbH is a mature technology company specializing in smart data analysis and AI-driven yield analytics for the semiconductor industry. With over 20 years of experience, the company offers the YieldWatchDog platform and related modules to help semiconductor manufacturers improve product quality, reduce costs, and accelerate yield ramp. The website reflects a professional B2B software provider with a global customer base and strong industry trust signals. Technically, the site is built on WordPress with Elementor and leverages Cloudflare for CDN and caching, alongside Matomo for analytics. However, a critical security gap exists due to the absence of a valid SSL/TLS certificate, leaving the site without HTTPS protection. Privacy compliance is well addressed with GDPR-aligned policies and cookie consent mechanisms. Overall, the site is content-rich and professionally presented but requires urgent security improvements to protect user data and enhance trust.

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

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

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

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

Keep watching dryield.com

This scan found 20 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
15
Email security
50
DNS health
70
Network security
100
GDPR outside view
15
Average
42

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

DR YIELD holds a strong market position as a specialized semiconductor analytics provider with a mature domain and consistent WHOIS data. Their business model focuses on delivering AI-powered software solutions to semiconductor manufacturers, supported by customer testimonials and partnerships with industry leaders. The company targets semiconductor industry leaders and quality managers, offering high-performance, flexible analytics tools with open interfaces for integration. The presence of a dedicated careers page and contact options indicates operational maturity and growth orientation. The related domain dryield.net suggests an extended service ecosystem. The company’s digital presence is professional but could benefit from enhanced security and incident response transparency.

Security posture

The website’s security posture is weak due to the lack of HTTPS and SSL certificate, exposing users to potential data interception risks. No advanced security headers or mechanisms like HSTS, OCSP stapling, or TLS 1.2+ support are configured. While no vulnerable libraries or exposed sensitive data were detected, the absence of secure transport is a critical vulnerability. Privacy policies and cookie consent are well implemented, indicating awareness of compliance requirements. No explicit incident response or security policy pages were found, which could improve transparency and readiness. Overall, the site requires immediate SSL deployment and enhanced security headers to meet modern security standards.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Implement OCSP stapling to improve certificate validation performance and security.
  4. Upgrade server TLS protocols to support TLS 1.2 and TLS 1.3, disabling older insecure versions.
  5. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  6. Publish a security policy and incident response page with clear contact channels for security issues.
  7. Regularly audit and update all plugins, themes, and server software to mitigate vulnerabilities.
  8. Enhance accessibility features and mobile optimization for improved user experience.
  9. Consider adding a security.txt file for vulnerability disclosure and security contact information.
  10. Maintain transparency in data retention policies and update privacy documentation as needed.

Contact details published on the site

Addresses
Legal name
DR YIELD software & solutions GmbH
Technical notes

Notes

The website is powered by WordPress 6.5.5 with Elementor and Elementor Pro page builders, indicating a modern CMS framework. PHP 7.4.33 is used server-side. Cloudflare provides CDN and caching services, improving performance and availability. Matomo Tag Manager is used for analytics, respecting user consent via Complianz GDPR cookie management. The site uses multiple CSS and JS libraries for UI and functionality. However, performance metrics are unavailable, and no SSL/TLS is configured, which is a significant technical risk. The site is mobile optimized with responsive design and uses Google Fonts for typography. Technical debt appears low, but the lack of HTTPS and security headers is a critical modernization need.
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 dryield.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 dryield.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.