Public security report
38/100
A means lowest risk and F means highest, like a school report card. How the score is calculated →
Scanned 2026-10-30 · 18 issue(s) found · 11 checks passed
CyberTrust assessed cnooc.com.cn passively — using only information that is publicly visible on the internet: DNS records, certificates, response headers and reachable services. The result is 38/100, grade F, where A means lowest risk and F means highest, like a school report card.
Email spoofing is possible: no DMARC record was found for cnooc.com.cn, so anyone can send mail that appears to come from @cnooc.com.cn.
Strongest area: reputation and credential exposure (100/100). Weakest area: HTTP security headers (0/100).
18 issue(s) need attention (1 critical, 2 high, 5 medium, 10 low), while 11 checks passed.
Infrastructure observed: the web server identifies as nginx.
56 subdomain(s) of cnooc.com.cn resolve publicly.
| Area | Score | Grade | Issues |
|---|---|---|---|
| DNS hygiene | 84 | B | 2 |
| email spoofing defences (SPF/DKIM/DMARC) | 44 | F | 3 |
| external attack surface | 0 | F | 3 |
| IP threat intelligence | — | — | 0 |
| reputation and credential exposure | 100 | A | 0 |
| TLS encryption and certificates | 44 | F | 3 |
| HTTP security headers | 0 | F | 7 |
Automated bots continuously scan for Elasticsearch on 138.113.199.31:9200 (hosts: bid.cnooc.com.cn, bid.cnooc.com.cn, hxfile.cloud.cnooc.com.cn) and try weak passwords or known exploits; the usual outcome is a full data exfiltration or ransomware wiping.
WebLogic on 138.113.199.31:7001 (hosts: bid.cnooc.com.cn, bid.cnooc.com.cn, hxfile.cloud.cnooc.com.cn) faces constant credential stuffing and exploit attempts; weak or default passwords often hand over full access in one try.
Without it, spoofed mail is usually delivered as normal and you receive no visibility at all; bulk senders are also required by major mailbox providers to publish DMARC.
Printer (JetDirect) on 138.113.199.31:9100 leaks configuration, topology or credentials (SNMP community strings are often 'public') and can be abused for internal pivoting.
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.
64-bit block ciphers are vulnerable to SWEET32 after enough data on one connection, and 3DES is no longer accepted by compliance standards.
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.
Visitors who type the bare domain land on an unencrypted connection and submit data in plaintext, with nothing on screen to warn them.
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.
The policy is too permissive (script-src 'unsafe-inline'; script-src 'unsafe-eval'), so injected scripts still run while giving a false sense of security.
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 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 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.
Without DKIM, mail integrity cannot be verified and DMARC loses one of its two authentication pillars. Note we probed only 46 common selectors, so a custom selector may exist.
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.
Missing Secure lets cookies travel in plaintext; missing HttpOnly lets injected scripts steal sessions; missing SameSite enables CSRF. Affected: INGRESSCOOKIE, app_token.
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 cnooc.com.cn (free) → Open the live interactive report →