hoax.com security report

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

78risk

Critical

Exposed services or known CVEs need attention now.

0Critical

6High

11Medium

17Low

2Info

Collected 12 hours ago62.5sfrom cache

Certificate Transparency276
DNS resolution21
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs34
Registration
DNS posture4
Email authentication2
Certificate
Security headers2
Archived URLs
Analysis36

noteFound 276 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
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.

Public RDP is the most common ransomware entry point.
What to do
Restrict 3389/tcp to a VPN, bastion, or allow-listed source range.
asset: 176.126.122.206:3389
Public RDP is the most common ransomware entry point.
What to do
Restrict 3389/tcp to a VPN, bastion, or allow-listed source range.
asset: 5.8.93.86:3389
Public RDP is the most common ransomware entry point.
What to do
Restrict 3389/tcp to a VPN, bastion, or allow-listed source range.
asset: 82.97.206.25:3389
Shodan matched these CVEs against the service banners it saw on 5.189.203.135 (api.hoax.com), which advertise openssh 9.2p1, 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 5.189.203.135 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: 5.189.203.135
Public RDP is the most common ransomware entry point.
What to do
Restrict 3389/tcp to a VPN, bastion, or allow-listed source range.
asset: 193.169.239.24:3389
Public RDP is the most common ransomware entry point.
What to do
Restrict 3389/tcp to a VPN, bastion, or allow-listed source range.
asset: 217.195.200.65:3389
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: 176.126.122.206:22
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: 5.8.93.86:22
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: 82.97.206.25:22
5.189.203.135 (api.hoax.com) reports openssh 9.2p1, 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: 5.189.203.135
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: 5.189.203.135:22
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: 193.169.239.24:22
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: 217.195.200.65:22
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: 95.85.93.121:22
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: 80.240.97.121:22
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://hoax.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://hoax.com/
176.126.122.206 (hoax.com) reports lua-nginx-module 1.31.1.1, openresty 1.31.1.1, openssh 10.0p2. 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: 176.126.122.206
5.8.93.86 (buy.hoax.com) reports lua-nginx-module 1.31.1.1, openssh 9.2p1, openresty 1.31.1.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: 5.8.93.86
82.97.206.25 (ww3.hoax.com) reports lua-nginx-module 1.31.1.1, openssh 9.2p1, openresty 1.31.1.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: 82.97.206.25
193.169.239.24 (fun.hoax.com) reports lua-nginx-module 1.31.1.1, openssh 9.2p1, openresty 1.31.1.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: 193.169.239.24
217.195.200.65 (blog.hoax.com) reports lua-nginx-module 1.31.1.1, openresty 1.31.1.1, openssh 10.0p2. 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: 217.195.200.65
95.85.93.121 (beta.hoax.com) reports openssh 9.2p1, lua-nginx-module 1.31.1.1, openresty 1.31.1.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: 95.85.93.121
80.240.97.121 (sad.hoax.com) reports lua-nginx-module 1.31.1.1, openresty 1.31.1.1, openssh 10.0p2. 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: 80.240.97.121
beta.hoax.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: beta.hoax.com
staging.hoax.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: staging.hoax.com
alpha.beta.hoax.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: alpha.beta.hoax.com
bikini.beta.hoax.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: bikini.beta.hoax.com
insurance.beta.hoax.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: insurance.beta.hoax.com
car.insurance.beta.hoax.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: car.insurance.beta.hoax.com
yacht.insurance.beta.hoax.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: yacht.insurance.beta.hoax.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://hoax.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: hoax.com
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: hoax.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: hoax.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: hoax.com

final https://hoax.com/status 526time 1091msstack 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 1 server
mail.computer.com
✓SPFends in -all
v=spf1 ip4:192.64.151.249 mx a -all
✓DMARCp=reject
v=DMARC1; p=reject; adkim=s; aspf=s; rua=mailto:dmarc@hoax.com; ruf=mailto:dmarc@hoax.com
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns1.anydns.com ns2.anydns.com ns3.anydns.com ns4.anydns.com

✓Registered with DNC Holdings, Inc.26.8 years old
hoax.com
!Registration expiry81 days
2026-11-27
✓Transfer lock
client delete prohibited, client transfer prohibited, client update prohibited
✓4 nameservers at registry
ns1.anydns.com ns2.anydns.com ns3.anydns.com ns4.anydns.com

Address	Ports	CVEs	Edge	Network
176.126.122.206 hoax.com +8	228044333895001	0	direct	—
5.8.93.86 buy.hoax.com +2	228044333899100	0	direct	—
82.97.206.25 ww3.hoax.com +1	2253804433389	0	direct	—
5.189.203.135 api.hoax.com +1	22804433000	2	direct	—
193.169.239.24 fun.hoax.com +4	22804433389	0	direct	—
217.195.200.65 blog.hoax.com +2	22804433389	0	direct	—
95.85.93.121 beta.hoax.com +7	2280443	0	direct	—
80.240.97.121 sad.hoax.com +2	2280443	0	direct	—
91.199.82.208 my.hoax.com	3478	0	direct	—
95.85.93.128 staging.hoax.com	none known	0	direct	—

Archived URLs

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

hoax.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames