Yageo logo

Yageo

Yageo manufactures and distributes passive electronic components including resistors, capacitors, inductors, and wireless components. The company serves various industries such as automotive, telecommunications, industrial, and consumer electronics through a global network of production facilities and sales offices. UpGuard continuously monitors the security posture of Yageo using open-source, commercial, and proprietary threat intelligence feeds. Our analysis is centered on objective, externally verifiable information.

Start a free trial for full access

Yageo Security Rating

Yageo's security rating is based on the analysis of their external attack surface. The higher the rating, the better their security posture. Start a free trial to get a more in-depth risk assessment for Yageo.

Company info

Yageo
Company Yageo Employees 510 Location Taiwan Last updated April 28, 2026

Last updated April 28, 2026

Yageo Vendor Risk Report

This vendor risk report is based on UpGuard's continuous monitoring of Yageo's security posture using open-source, commercial, and proprietary threat intelligence feeds. The results are summarized into a security rating based on the analysis of hundreds of individual checks across five risk categories: website security, email security, phishing & malware, brand & reputation risk, and network security.

Start a free trial for full access

Website Security

Yageo

Server information header exposed

Exposing information about the server version increases the ability of attackers to exploit certain vulnerabilities. The website configuration should be changed to prevent version information being revealed in the 'server' header.

X-Frame-Options is not deny or sameorigin

Browsers may display this website's content in frames. This can lead to clickjacking attacks.

CSP is not implemented

No valid Content Security Policy is implemented. This increases the risk of XSS and clickjacking attacks.

HttpOnly cookies not used

When HttpOnly cookies are not used, the cookies can be accessed on the client, which enables certain type of client-side attacks. The website configuration should be changed to enforce HttpOnly cookies.

X-Content-Type-Options is not nosniff

Browsers may interpret files as a different MIME type than what is specified in the Content-Type HTTP header. This can lead to MIME confusion attacks.

Unmaintained page detected

This domain appears to be unmaintained based on indicators like page content or status code. Unmaintained pages expand the attack surface for malicious actors.

Secure cookies used

Using secure cookies reduces the risk of third parties intercepting information contained in these cookies.

X-Powered-By header not exposed

Information about specific technology used on the server is obscured.

Referrer policy is not unsafe-url

The website's Referrer Policy is not configured to allow unsafe information to be sent in the referrer header.

ASP.NET version header not exposing specific ASP.net version

Ensuring the ASP.NET version header is not exposing a specific version makes it harder for attackers to exploit certain vulnerabilities.

ASP.NET version header not exposed

Ensuring the ASP.NET version header is not exposed makes it harder for attackers to exploit certain vulnerabilities.

DMARC policy is not p=none

DMARC reject policy provides the most effective protection against fraudulent emails being sent from a domain.

DMARC policy exists

DMARC protects against fraudulent emails being sent from a domain.

SPF syntax correct

Sender Policy Framework (SPF) record passes basic syntax checks.

DMARC policy percentage is default

DMARC policy percentage is set to default 100%, ensuring all mail is covered by the policy.

Strict SPF filtering - not using ~all

Sender Policy Framework (SPF) record strictly enforces specific domains allowed to send email on its behalf.

SPF ptr mechanism not used

Sender Policy Framework (SPF) record does not include the ptr mechanism.

DNSSEC not enabled

DNSSEC records prevent third parties from forging the records that guarantee a domain's identity. DNSSEC should be configured for this domain.

Domain registrar or registry deletion protection not enabled

Domain is not protected from unsolicited deletion requests with the registrar or registry. The domain should have clientDeleteProhibited or serverDeleteProhibited set.

Domain registrar or registry update protection not enabled

Domain is not protected from unsolicited update requests with the registrar or registry. The domain should have clientUpdateProhibited or serverUpdateProhibited set.

No unregistered MX records detected

No unregistered MX records that could lead to receiving mail on behalf of the target organization were detected.

Domain has not expired

Domain has not expired.

No subdomain takeover vulnerability detected

No dangling DNS records that could lead to subdomain takeover were detected.

Domain does not expire soon

Domain does not expire within 30 days.

Domain not flagged as inactive

Domain is not flagged as inactive.

Domain not pending deletion

Domain is not pending deletion with the registrar.

Domain not pending restoration

Domain is not pending restoration with the registrar.

Domain registrar or registry transfer protection enabled

Domain is protected from unsolicited transfer requests.

Domain free of registrar DNS resolution hold

Domain is not under a DNS resolution hold with the registrar.

Domain free of registry DNS resolution hold

Domain is not under a DNS resolution hold with the registry itself.

Domain renewal not prohibited by registry

Domain is not prohibited from renewal at the registry itself.

CAA enabled

The domain contains a valid Certification Authority Authorization (CAA) record. A CAA record indicates which Certificate Authorities (CAs) are authorized to issue certificates for a domain.

Encryption

Yageo

HTTP does not redirect to HTTPS

The domain is still accessible over HTTP. All HTTP requests should be redirected to HTTPS.

Common Diffie-Hellman prime used in key exchange

Commonly used Diffie-Hellman primes smaller than 2048 bits are likely to have been broken by organized groups or nation-state actors, allowing passive eavesdropping on traffic. It is recommended to use a 2048 bit or stronger Diffie-Hellman prime.

Insecure SSL/TLS versions available

Any version of the SSL protocol, and TLS prior to version 1.2, are now considered insecure. The server should disable support for these old protocols.

Only weak cipher suites supported in TLS 1.2

Weak cipher suites can potentially be broken by a well resourced attacker, and should not be used where possible. This server also does not appear to support any secure cipher suites, which means clients will either not be able to make a secure connection, or only make a weak one.

Domain was not found on the HSTS preload list

The domain was not found on the HSTS preload list. Users who visit the website for the first time will be vulnerable to MITM attacks. The requirements for inclusion on the preload list are specified by hstspreload.org.

Certificate not found on our revoked certificate list

The site's certificate chain was checked against our list of revoked certificates.

SSL available

SSL is supported for this site.

Hostname matches SSL certificate

The site's hostname matches the SSL certificate.

SSL has not expired

SSL certificate has not expired.

Trusted SSL certificate

The certificate presented by this domain was issued by a trusted certificate authority.

HTTP Strict Transport Security (HSTS) enforced

With HSTS enforced, people browsing this site are less susceptible to man-in-the-middle attacks.

SSL certificate chain present in server response

A complete SSL certificate chain was presented by the server for this domain.

SSL chain certificates do not expire within 20 days

SSL intermediate and root certificates do not expire within 20 days.

SSL expiration period shorter than 398 days

The SSL certificate presented by the server has an expiration period shorter than 398 days.

SSL has more than 20% of its valid period remaining

SSL certificate does not expire in less than 20% of its total valid period.

Strong SSL algorithm

Industry standard SHA-256 encryption in use.

HSTS header contains includeSubDomains

The HTTP Strict Transport Security (HSTS) header contains the includeSubDomains directive.

Strong public certificate key length

The site's public certificate provides at least 112 bits of security strength.

Data leakage

Yageo

No open cloud storage service detected

No cloud storage service configured to allow anonymous file listing was detected.

Domain index is not a listable directory

The domain index is not a listable directory.

IP/Domain Reputation

Yageo

No reports of botnet activity in the last 30 days

This IP/domain has not been reported as a source of botnet activity in the last 30 days.

No reports of brute force login attempts in the last 30 days

This IP/domain did not appear on any list of IPs and domains known to perform brute force login attempts in the last 30 days.

No reports of malware distribution in the last 30 days

This IP/domain has been reported for distributing malware in the last 30 days.

No reports of unsolicited scanning in the last 30 days

This IP/domain has not been reported for performing unsolicited scanning in the last 30 days.

No reports of phishing activity in the last 30 days

This IP/domain has not been reported as a phishing site in the last 30 days.

No reports of botnet activity in the last 90 days

This IP/domain has not been reported as a source of botnet activity in the last 90 days.

No reports of brute force login attempts in the last 90 days

This IP/domain did not appear on any list of IPs and domains known to perform brute force login attempts in the last 90 days.

No reports of malware distribution in the last 90 days

This IP/domain has been reported for distributing malware in the last 90 days.

No reports of unsolicited scanning in the last 90 days

This IP/domain has not been reported for performing unsolicited scanning in the last 90 days.

No reports of phishing activity in the last 90 days

This IP/domain has not been reported as a phishing site in the last 90 days.

Vulnerability Management

Yageo

Not vulnerable to CVE-2014-0160 (Heartbleed)

A bug in OpenSSL's implementation of the TLS heartbeat extension allows access to portions of memory on the targeted host e.g. cryptographic keys and passwords.

Not vulnerable to CVE-2014-3566 (POODLE)

The server does not support SSLv3, and is not vulnerable to the POODLE attack.

Not vulnerable to CVE-2015-0204 (FREAK)

The server does not offer RSA_EXPORT cipher suites, so clients are not vulnerable to the FREAK attack.

Not vulnerable to CVE-2015-4000 (Logjam)

The server is using strong Diffie-Hellman parameters and is not vulnerable to the Logjam attack.

Security reports related to Yageo

Compare Yageo's security performance with other companies in their industry.

Cybersecurity & Risk Management Library

The ultimate guide to attack surface and third-party risk management – actionable advice for security teams, managers, and executives.

Free instant security score

How secure is your organization?

Request a free cybersecurity report to discover key risks on your website, email, network, and brand.
  • Instant insights you can act on immediately
  • Hundreds of risk factors including email security, SSL, DNS health, open ports and common vulnerabilities
Website Security scan results table Cyber security rating score 850 out of 950