Public security report
34/100
A means lowest risk and F means highest, like a school report card. How the score is calculated →
Scanned 2026-10-30 · 26 issue(s) found · 8 checks passed
CyberTrust assessed coscoshipping.com passively — using only information that is publicly visible on the internet: DNS records, certificates, response headers and reachable services. The result is 34/100, grade F, where A means lowest risk and F means highest, like a school report card.
Email spoofing is possible: a DMARC record exists for coscoshipping.com, but its policy is p=none — receivers are asked to report spoofed mail, not to reject it.
Strongest area: reputation and credential exposure (100/100). Weakest area: TLS encryption and certificates (0/100).
26 issue(s) need attention (4 critical, 3 high, 7 medium, 12 low), while 8 checks passed.
Infrastructure observed: DNS is served by aliyun.
117 subdomain(s) of coscoshipping.com resolve publicly.
1 of them resolve but return a server error instead of a page.
Automated bots continuously scan for MS SQL Server on 121.32.243.57:1433 (hosts: www.coscoshipping.com, charity.coscoshipping.com, en.coscoshipping.com) and try weak passwords or known exploits; the usual outcome is a full data exfiltration or ransomware wiping.
VNC on 121.32.243.57:5901 (hosts: www.coscoshipping.com, charity.coscoshipping.com, en.coscoshipping.com) is the main entry point for ransomware: brute force or an exploit yields full control of the machine.
DNP3 on 121.32.243.57:20000 has essentially no authentication: an attacker can issue commands that alter physical processes, risking damage, downtime or safety incidents.
Kibana on 121.32.243.57:5601 (hosts: www.coscoshipping.com, charity.coscoshipping.com, en.coscoshipping.com) faces constant credential stuffing and exploit attempts; weak or default passwords often hand over full access in one try.
Kafka on 121.32.243.57:9092 is often unauthenticated: business data can be read and forged messages injected, causing downstream systems to act on attacker input.
It expired 58 days ago (2026-09-02): browsers show a full-page warning, most visitors leave, and API or app integrations fail without a clear reason.
This certificate is issued for dtu.spe.coscoshipping.com, www.dtu.spe.coscoshipping.com, so browsers warn; typical causes are missing the bare domain, a stale name, or an incomplete SAN list.
Only 12 days remain, which usually means automated renewal already failed - unattended, that becomes a full outage at expiry.
Versions TLSv1.0, TLSv1.1 are formally deprecated, fail PCI DSS requirements and are no longer supported by modern browsers; they also enable downgrade attacks and fail compliance audits.
Without it, an attacker can strip SSL on the first HTTP request and keep the user on plaintext (SSL stripping), a common attack on public Wi-Fi.
PPTP VPN on 121.32.243.57:1723 leaks configuration, topology or credentials (SNMP community strings are often 'public') and can be abused for internal pivoting.
p=none does not stop anything - forged mail still reaches the inbox. It is only meant as an observation phase.
3 known vulnerabilities are inferred on 103.144.159.127; even un-weaponised ones leave the system open to every published technique. Version-based inference - treat as a patch-currency signal.
Kubernetes API on 121.32.243.57:6443 often has no authentication: an attacker can execute code on the host, commonly to mine crypto or steal cluster secrets.
The server does not staple the certificate revocation status. Every revocation check becomes an extra round trip to the CA, which slows the first visit and, if the CA endpoint is unreachable or the visitor's network blocks it, leaves the browser without a usable revocation status.
Missing Secure lets cookies travel in plaintext; missing HttpOnly lets injected scripts steal sessions; missing SameSite enables CSRF. Affected: BIGipServer5QzVXTIcKgu0vwJcOZ5nlA, TS01255aec, TS6e0dc8de029.
Without it, any injected script runs: session theft, fake payment forms, or card-skimming scripts on compromised pages. CSP limits the damage even when something else fails.
Without it a file uploaded as an image can be executed as HTML/JavaScript on your domain, stealing same-site cookies and sessions.
Without it, attackers overlay a transparent frame of your page and trick users into clicking real actions such as transfers or password changes (clickjacking).
Without it any CA may issue certificates for your domain, enabling a lookalike site with a valid padlock.
Without it, attackers can poison caches or forge answers and send visitors to a lookalike server that harvests credentials.
In testing mode receivers treat DKIM failures as 'not signed', so signature problems stay invisible - the check is effectively half disabled.
At 1024 bits (selector dkim) the key is considered weak; 1024-bit keys can be broken cheaply, letting attackers sign mail that passes DKIM.
Without it an attacker on the network path can force a downgrade to plaintext and read or modify mail such as contracts and payment details.
SSH on 121.32.243.57:2222 (key-only is acceptable) still sees continuous brute force; a weak password or poorly managed key means direct login.
Some hostnames of this domain resolve publicly but answer with an HTTP server error instead of a page. Visitors who follow such a link see a gateway error, search engines index the error, and a hostname that resolves but serves nothing is also a takeover waiting to happen once the record is removed.
Everything above is what anyone can observe from the internet. Domain owners who verify ownership additionally get the full asset inventory — every subdomain with its open ports and running services — look-alike and typosquatting domains registered against the brand, credential-exposure monitoring, and copy-paste fixes for each finding.
Verify ownership of coscoshipping.com (free) → Open the live interactive report →