youxiake.com security report

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

49risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

6Medium

1Low

2Info

Collected 5 hours ago13.8sfrom cache

Certificate Transparency3
DNS resolution4
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs8
Registration
DNS posture2
Email authentication1
Certificate
Security headers4
Archived URLs
Analysis10

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.

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.youxiake.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@youxiake.com"`, review the reports, then move to p=quarantine and p=reject.
asset: youxiake.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://www.youxiake.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.youxiake.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.youxiake.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.youxiake.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.youxiake.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.youxiake.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: youxiake.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: youxiake.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: youxiake.com

final https://www.youxiake.com/status 500time 3894msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=63072000; includeSubdomains; preload
✗Content-Security-Policy
✓Clickjacking protection
sameorigin
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin-when-cross-origin
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie yxk_session
no Secure · HttpOnly · no SameSite
✗Cookie yxk_last_visit
no Secure · HttpOnly · no SameSite
✗Cookie sitecode
no Secure · HttpOnly · no SameSite
✗Cookie pingtaiw
no Secure · HttpOnly · no SameSite
✗Cookie site
no Secure · HttpOnly · no SameSite

✓Receives mail via 2 servers
mxbiz1.qq.com mxbiz2.qq.com
!SPFends in ~all
v=spf1 include:spf.mail.qq.com ~all
✗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
ns1.alidns.com ns2.alidns.com

✓Registered with Bizcn.com, Inc.18.4 years old
youxiake.com
✓Registration expiry579 days
2028-04-09
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns1.alidns.com ns2.alidns.com

Address	Ports	Edge	Network
124.160.26.140 youxiake.com	80443	direct	—
117.148.176.140 youxiake.com	80443	direct	—
183.131.19.244 youxiake.com	80443	direct	—
129.226.102.73 mail.youxiake.com +11	80443	direct	—

Archived URLs

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

youxiake.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames