# AMSC ASA Security Rating, Vendor Risk Report, and Data Breaches

> This is a plain-markdown summary of [https://www.upguard.com/security-report/american-shipping](https://www.upguard.com/security-report/american-shipping), generated for AI agents and LLMs. Security scores and check results reflect UpGuard's independent analysis and are kept in sync with the source page. Visit the source URL for the full interactive report.

## Overview
- Domain: amscasa.com
- Grade: C (Fair)
- Score: 417 / 950
- Last scan: August 22, 2026
- Website: https://www.amscasa.com

## Vendor risk summary
This vendor risk report is based on UpGuard's continuous monitoring of AMSC ASA'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.

## Security categories

### Website Security

- Fail — 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.
- Fail — X-Frame-Options is not deny or sameorigin
  - Browsers may display this website's content in frames. This can lead to clickjacking attacks.
- Fail — 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.
- Fail — CSP is not implemented
  - No valid Content Security Policy is implemented. This increases the risk of XSS and clickjacking attacks.
- Fail — CSP contains unsafe-eval
  - The Content Security Policy is implemented with unsafe-eval, reducing protection against XSS attacks.
- Fail — 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.
- Pass — Secure cookies used
  - Using secure cookies reduces the risk of third parties intercepting information contained in these cookies.
- Pass — X-Powered-By header not exposed
  - Information about specific technology used on the server is obscured.
- Pass — CSP implemented without insecure active sources
  - The Content Security Policy does not allow any insecure active sources.
- Pass — HttpOnly cookies used
  - Using HttpOnly cookies reduces the risk of client side script attacks, by preventing cookies being read on the client.
- Pass — 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.
- Pass — 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.
- Pass — ASP.NET version header not exposed
  - Ensuring the ASP.NET version header is not exposed makes it harder for attackers to exploit certain vulnerabilities.
- Pass — CSP implemented without insecure passive sources
  - The Content Security Policy does not allow any insecure passive (img/media) sources.
- Pass — No unmaintained page detected
  - The page appears to be maintained.

### Email

- Fail — 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.
- Pass — DMARC policy exists
  - DMARC protects against fraudulent emails being sent from a domain.
- Pass — SPF enabled
  - Sender Policy Framework (SPF) records prevent spammers from sending messages with forged addresses.
- Pass — Strict SPF filtering - not using +all
  - Sender Policy Framework (SPF) record strictly enforces specific domains allowed to send email on its behalf.
- Pass — SPF syntax correct
  - Sender Policy Framework (SPF) record passes basic syntax checks.
- Pass — SPF ptr mechanism not used
  - Sender Policy Framework (SPF) record does not include the ptr mechanism.

### Network

- Fail — 'SSH' port open
  - The 'SSH' service is running and exposed to the internet. The configuration of the server should be reviewed and unnecessary ports closed.
- Fail — '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.

### DNS

- Fail — 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.
- Pass — No unregistered MX records detected
  - No unregistered MX records that could lead to receiving mail on behalf of the target organization were detected.
- Pass — Domain has not expired
  - Domain has not expired.
- Pass — No subdomain takeover vulnerability detected
  - No dangling DNS records that could lead to subdomain takeover were detected.
- Pass — Domain does not expire soon
  - Domain does not expire within 30 days.
- Pass — DNSSEC enabled
  - DNSSEC records prevent third parties from forging the records that guarantee a domain's identity.

### Encryption

- Fail — HTTP does not redirect to HTTPS
  - The domain is still accessible over HTTP. All HTTP requests should be redirected to HTTPS.
- Fail — 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.
- Fail — 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.
- Fail — 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.
- Fail — 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.
- Pass — Certificate not found on our revoked certificate list
  - The site's certificate chain was checked against our list of revoked certificates.
- Pass — SSL available
  - SSL is supported for this site.
- Pass — SSL has not expired
  - SSL certificate has not expired.
- Pass — HTTP Strict Transport Security (HSTS) enforced
  - With HSTS enforced, people browsing this site are less susceptible to man-in-the-middle attacks.
- Pass — No insecure SSL/TLS versions available
  - No insecure SSL/TLS versions are available for this site.
- Pass — SSL expiration period shorter than 398 days
  - The SSL certificate presented by the server has an expiration period shorter than 398 days.
- Pass — SSL has more than 20% of its valid period remaining
  - SSL certificate does not expire in less than 20% of its total valid period.
- Pass — Strong SSL algorithm
  - Industry standard SHA-256 encryption in use.
- Pass — Strong public certificate key length
  - The site's public certificate provides at least 112 bits of security strength.

### Data leakage

- Pass — No open cloud storage service detected
  - No cloud storage service configured to allow anonymous file listing was detected.
- Pass — Domain index is not a listable directory
  - The domain index is not a listable directory.

### IP/Domain Reputation

- Pass — 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.
- Pass — 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.
- Pass — No reports of malware distribution in the last 30 days
  - This IP/domain has been reported for distributing malware in the last 30 days.
- Pass — 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.
- Pass — 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.
- Pass — 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.
- Pass — 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.
- Pass — No reports of malware distribution in the last 90 days
  - This IP/domain has been reported for distributing malware in the last 90 days.
- Pass — 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.
- Pass — 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

- Fail — 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.
- Fail — NGINX 1.18.0 has potential vulnerabilities
  - NGINX 1.18.0 has vulnerabilities which might be exploitable under certain conditions. Affected domains should be checked to determine which vulnerabilities might pose a risk.
- Pass — 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.
- Pass — Not vulnerable to CVE-2014-3566 (POODLE)
  - The server does not support SSLv3, and is not vulnerable to the POODLE attack.
- Pass — 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.
- Pass — Not vulnerable to CVE-2015-4000 (Logjam)
  - The server is using strong Diffie-Hellman parameters and is not vulnerable to the Logjam attack.

---
Full interactive report: https://www.upguard.com/security-report/american-shipping
Security Reports Policy: https://www.upguard.com/security-report-policy