wywyx.com security report

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

45risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

2Medium

3Low

2Info

Collected 16 hours ago6.3sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs1
Registration
DNS posture2
Email authentication1
Certificate
Security headers1
Archived URLs
Analysis8

noteCertificate Transparency did not complete (HTTP 502). Results below are partial.
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.wywyx.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@wywyx.com"`, review the reports, then move to p=quarantine and p=reject.
asset: wywyx.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.wywyx.com/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://www.wywyx.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://www.wywyx.com/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://www.wywyx.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: wywyx.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: wywyx.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: wywyx.com

final https://www.wywyx.com/status 200time 2201msstack cloudflare

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

✓Receives mail via 2 servers
mxbiz1.qq.com mxbiz2.qq.com
!SPFends in ~all
v=spf1 ip4:47.111.144.246 ~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.ename.net ns2.ename.net

✓Registered with eName Technology Co., Ltd.13.8 years old
wywyx.com
✓Registration expiry2637 days
2033-11-26
✓Transfer lock
client delete prohibited, client transfer prohibited
✓2 nameservers at registry
ns1.ename.net ns2.ename.net

Address	Ports	CVEs	Edge	Network
47.111.144.246 wywyx.com	80	0	direct	—

Archived URLs

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

wywyx.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames