set-sail logo

set-sail

set-sail.com.cn develops and manufactures automation equipment, testing equipment, fixtures, and technical solutions for various industries including electronics, automotive, new energy, and semiconductors. The company serves customers primarily in the East China region. UpGuard continuously monitors the security posture of set-sail 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

set-sail Security Rating

set-sail'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 set-sail.

Company info

set-sail
Company set-sail Last updated April 28, 2026

Last updated April 28, 2026

set-sail Vendor Risk Report

This vendor risk report is based on UpGuard's continuous monitoring of set-sail'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

set-sail

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.

CSP allows insecure passive sources

The Content Security Policy on this site allows insecure passive content.

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.

HttpOnly cookies used

Using HttpOnly cookies reduces the risk of client side script attacks, by preventing cookies being read on the client.

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.

Start a free trial for full access

Email

set-sail

DMARC policy is p=none

DMARC policy is p=none. This provides no protection against fraudulent emails. The DMARC policy should be migrated to p=quarantine, and eventually p=reject.

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. This record should preferably not use the ~all mechanism, as this does not instruct the mail receiver to reject messages from unauthorised sources. When DMARC is not being enforced, -all should be used on the SPF record.

DMARC policy exists

DMARC protects against fraudulent emails being sent from a domain.

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.

Start a free trial for full access

Network

set-sail

'HTTP' port open

The 'HTTP' 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.

Start a free trial for full access

DNS

set-sail

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.

Start a free trial for full access

Encryption

set-sail

SSL not available

SSL is the standard encryption method for browsing websites. Enabling SSL requires installing an SSL certificate on the site.

HTTP does not redirect to HTTPS

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

HTTPS is redirected to an insecure protocol

HTTPS is redirected to an insecure protocol. HTTPS requests should not be redirected to insecure protocols, as they do not ensure encrypted communication between the website and its visitors.

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.

Weak cipher suites supported in TLS 1.2

Weak cipher suites can potentially be broken by a well resourced attacker, and should not be supported by the server unless very old devices or browsers must be supported.

Certificate not found on our revoked certificate list

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

No insecure SSL/TLS versions available

No insecure SSL/TLS versions are available for this site.

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.

Strong public certificate key length

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

Start a free trial for full access

Data leakage

set-sail

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.

Start a free trial for full access

IP/Domain Reputation

set-sail

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.

Start a free trial for full access

Vulnerability Management

set-sail

End-of-life version of NGINX detected

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

NGINX 1.23.0 has potential vulnerabilities

NGINX 1.23.0 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-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.

Start a free trial for full access

Security reports related to set-sail

Compare set-sail's security performance with other companies in their industry.

View all security reports

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
Free score
Website Security scan results table Cyber security rating score 850 out of 950