wcase.net security report

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

87risk

Critical

Exposed services or known CVEs need attention now.

1Critical

2High

8Medium

4Low

2Info

Collected 9 hours ago3.2sfrom cache

Certificate Transparency7
DNS resolution3
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs10
Registration
DNS posture4
Email authentication1
Certificate
Security headers0
Archived URLs
Analysis17

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.

Shodan matched these CVEs against the service banners it saw on 78.46.233.211 (wcase.net), which advertise ntp 3, nginx 1.10.3, http server 2.4.25, openssh 7.4p1. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2026-49975 CVE-2026-44631 CVE-2026-44186 CVE-2026-44185 CVE-2026-44119 CVE-2026-43951 CVE-2026-42536 CVE-2026-42535 CVE-2026-34356 CVE-2026-34355 CVE-2026-34059 CVE-2026-34032 CVE-2026-33857 CVE-2026-33523 CVE-2026-33007 ...and 113 more
What to do
Confirm the running versions on 78.46.233.211 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-49975 ↗CVE-2026-44631 ↗CVE-2026-44186 ↗CVE-2026-44185 ↗CVE-2026-44119 ↗
asset: 78.46.233.211
Shodan matched these CVEs against the service banners it saw on 159.69.136.112 (meet.wcase.net), which advertise nginx 1.22.1. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2025-23419 CVE-2023-44487
What to do
Confirm the running versions on 159.69.136.112 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2025-23419 ↗CVE-2023-44487 ↗
asset: 159.69.136.112
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.wcase.net TXT "v=DMARC1; p=none; rua=mailto:dmarc@wcase.net"`, review the reports, then move to p=quarantine and p=reject.
asset: wcase.net
78.46.233.211 (wcase.net) reports ntp 3, nginx 1.10.3, http server 2.4.25, openssh 7.4p1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 78.46.233.211
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 78.46.233.211:21
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 78.46.233.211:22
159.69.136.112 (meet.wcase.net) reports nginx 1.22.1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 159.69.136.112
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://wcase.net/
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://wcase.net/
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://wcase.net/
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: wcase.net
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 78.46.233.211:25
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://wcase.net/
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://wcase.net/
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: wcase.net
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: wcase.net
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: wcase.net

final https://wcase.net/status 200time 760msstack cloudflare

✓http:// redirects to https://
✗Strict-Transport-Security
✗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 1 server
mail.wcase.net
!SPFends in ~all
v=spf1 +a +mx include:_spf.google.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
✓4 nameservers
ns-1084.awsdns-07.org ns-1902.awsdns-45.co.uk ns-460.awsdns-57.com ns-911.awsdns-49.net

✓Registered with Hosting Ukraine LLC14.4 years old
wcase.net
✓Registration expiry223 days
2027-04-19
✗Transfer lock
none
✓4 nameservers at registry
ns-1084.awsdns-07.org ns-1902.awsdns-45.co.uk ns-460.awsdns-57.com ns-911.awsdns-49.net

Address	Ports	CVEs	Edge	Network
78.46.233.211 wcase.net +5	2122258081123443	128	direct	—
159.69.136.112 meet.wcase.net +3	804438080	2	direct	—

Archived URLs

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

wcase.net security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames