Landrex Technologies Co. logo

Landrex Technologies Co.

Landrex Technologies Co. provides automated optical inspection and testing solutions for electronics manufacturing, including systems for PCB testing, LED inspection, touch panel testing, and battery testing for electric vehicles. UpGuard continuously monitors the security posture of Landrex Technologies Co. 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

Landrex Technologies Co. Security Rating

Landrex Technologies Co.'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 Landrex Technologies Co..

Company Landrex Technologies Co. Last updated April 28, 2026

Last updated April 28, 2026

Landrex Technologies Co. Vendor Risk Report

This vendor risk report is based on UpGuard's continuous monitoring of Landrex Technologies Co.'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

Secure cookies not used

When secure cookies are not used, there is an increased risk of third parties intercepting information contained in these cookies. The website configuration should be changed so that all 'Set-Cookie' headers include 'secure'.

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 implemented unsafely

The Content Security Policy may not restrict sources appropriately, or may contain 'unsafe-inline' without the use of a nonce or hash. This increases the risk of XSS 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.

CSP contains unsafe-eval

The Content Security Policy is implemented with unsafe-eval, reducing protection against XSS attacks.

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.

X-Powered-By header not exposed

Information about specific technology used on the server is obscured.

CSP implemented without insecure active sources

The Content Security Policy does not allow any insecure active sources.

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.

CSP implemented without insecure passive sources

The Content Security Policy does not allow any insecure passive (img/media) sources.

DMARC policy not found

DMARC policy was not found. This makes it easier for attackers to send email from this domain. A DMARC policy should be deployed for this domain.

SPF policy uses ?all

Sender Policy Framework (SPF) record is too lenient as to which domains are allowed to send email on the domain's behalf. When DMARC is not being enforced, the SPF record should use -all to instruct mail receivers to reject messages from unauthorised sources.

SPF enabled

Sender Policy Framework (SPF) records prevent spammers from sending messages with forged addresses.

SPF syntax correct

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

SPF ptr mechanism not used

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

'FTP' port open

The 'FTP' service is running and exposed to the internet. The configuration of the server should be reviewed and unnecessary ports closed.

'IMAP' port open

The 'IMAP' service is running and exposed to the internet. The configuration of the server should be reviewed and unnecessary ports closed.

'POP3' port open

The 'POP3' service is running and exposed to the internet. The configuration of the server should be reviewed and unnecessary ports closed.

'SMTP' port open

The 'SMTP' service is running and exposed to the internet. The configuration of the server should be reviewed and unnecessary ports closed.

'DNS' port open

The 'DNS' service is running and exposed to the internet. The configuration of the server should be reviewed and unnecessary ports closed.

'HTTPS' port open

The 'HTTPS' service is running and exposed to the internet. The configuration of the server should be reviewed and unnecessary ports closed.

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.

CAA not enabled

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

No unregistered MX records detected

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

No subdomain takeover vulnerability detected

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

HTTP does not redirect to HTTPS

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

Hostname does not match SSL certificate

The site's hostname does not match the SSL certificate. The domain name should be added to the certificate, either as a Subject Alternative Name or as the Common Name.

SSL expired

SSL certificate has expired. The certificate will need to be renewed for connections to your domain to be trusted.

HTTP Strict Transport Security (HSTS) not enforced

Without HSTS enforced, people browsing this site are more susceptible to man-in-the-middle attacks. The server should be configured to support HSTS.

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.

Insecure cipher suite supported

Insecure cipher suites can be trivially broken by an attacker, allowing them to impersonate your server or eavesdrop on traffic.

Weak SSL algorithm

Industry standard SHA-256 encryption is not in use. The SSL certificate should be migrated to a SHA-256 certificate.

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.

HSTS header does not contain includeSubDomains

The HTTP Strict Transport Security (HSTS) header does not contain the includeSubDomains directive. This directive instructs the browser to also enforce the HSTS policy over subdomains of this domain.

Weak public certificate key length

Public key algorithms and key sizes offering less than 112 bits of security strength are no longer considered secure. Public RSA keys should be at least 2048-bit and ECDSA keys should be at least 224-bit.

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.

Trusted SSL certificate

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

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 Diffie-Hellman prime used in key exchange

TLS connections to the site use a strong Diffie-Hellman prime during key exchange.

No weak cipher suites supported in TLS 1.2

TLS connections to the site do not support any weak cipher suites.

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.

Not a suspected malware provider

This website does not appear to contain malicious code.

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.

Not suspected of unwanted software

This website does not appear to be attempting to install unwanted software.

Not a suspected phishing page

This site does not appear to be a forgery or imitation of another website.

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.

End-of-life version of Apache HTTP Server detected

The detected version of Apache HTTP Server is end of life. The product will likely not receive security updates from the vendor moving forward.

Vulnerable to CVE-2014-3566 (POODLE)

The server supports SSLv3 and is therefore vulnerable to POODLE, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack.

Apache HTTP Server 2.2.15 has potential vulnerabilities

Apache HTTP Server 2.2.15 has vulnerabilities which might be exploitable under certain conditions. Affected domains should be checked to determine which vulnerabilities might pose a risk.

Not vulnerable to CVE-2015-1635 (IIS HTTP.sys Remote Code Execution)

HTTP.sys in Windows Server 2008 R2 SP1, Windows Server 2012 Gold and R2, allows remote attackers to execute arbitrary code via crafted HTTP requests.

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-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 Landrex Technologies Co.

Compare Landrex Technologies Co.'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