chinahute.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

68risk

Elevated

Several issues worth triaging this week.

0Critical

3High

2Medium

2Low

2Info

Collected 19 hours ago3.6sfrom cache

Certificate Transparency2
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs1
Registration
DNS posture2
Email authentication0
Certificate
Security headers2
Archived URLs
Analysis9

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.

A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://chinahute.com/
Nothing tells receiving mail servers which hosts may send as @chinahute.com, so anyone can. Phishing that impersonates this domain will land in inboxes.
What to do
Publish an SPF TXT record listing your senders and ending in -all.
asset: chinahute.com
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.chinahute.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@chinahute.com"`, review the reports, then move to p=quarantine and p=reject.
asset: chinahute.com
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://chinahute.com/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://chinahute.com/
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://chinahute.com/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: chinahute.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: chinahute.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: chinahute.com

final https://chinahute.com/status 526time 2508msstack cloudflare

✗http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN
✗X-Content-Type-Options
✓Referrer-Policy
same-origin
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 2 servers
mxbiz1.qq.com mxbiz2.qq.com
✗SPF
no record
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns7.cnmsn.net ns8.cnmsn.net

✓Registered with Alibaba Cloud Computing (Beijing) Co., Ltd.8.1 years old
chinahute.com
✓Registration expiry681 days
2028-07-19
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns7.cnmsn.net ns8.cnmsn.net

Address	Ports	CVEs	Edge	Network
112.86.177.34 chinahute.com +1	1883	0	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

chinahute.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames