themewant.com security report

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

79risk

Critical

Exposed services or known CVEs need attention now.

1Critical

1High

5Medium

7Low

2Info

Collected 4 hours ago13.3sfrom cache

Certificate Transparency34
DNS resolution22
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs10
Registration
DNS posture2
Email authentication2
Certificate
Security headers1
Archived URLs
Analysis16

noteFound 34 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.

Shodan matched these CVEs against the service banners it saw on 84.32.84.107 (echo.themewant.com), which advertise php 8.2.30. 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-17543 CVE-2026-14355 CVE-2026-7568 CVE-2026-7262 CVE-2026-7261 CVE-2026-7260 CVE-2026-7259 CVE-2026-6735 CVE-2026-6722 CVE-2025-14179 CVE-2013-2220 CVE-2007-3205
What to do
Confirm the running versions on 84.32.84.107 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-17543 ↗CVE-2026-14355 ↗CVE-2026-7568 ↗CVE-2026-7262 ↗CVE-2026-7261 ↗
asset: 84.32.84.107
Shodan matched these CVEs against the service banners it saw on 84.32.84.121 (account.themewant.com), which advertise php 8.4.21. 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-17544 CVE-2026-17543 CVE-2026-14355 CVE-2026-7260 CVE-2013-2220 CVE-2007-3205
What to do
Confirm the running versions on 84.32.84.121 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-17544 ↗CVE-2026-17543 ↗CVE-2026-14355 ↗CVE-2026-7260 ↗CVE-2013-2220 ↗
asset: 84.32.84.121
84.32.84.107 (echo.themewant.com) reports php 8.2.30. 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: 84.32.84.107
84.32.84.121 (account.themewant.com) reports php 8.4.21. 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: 84.32.84.121
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://themewant.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://themewant.com/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: themewant.com
staging.themewant.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.themewant.com
development.themewant.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: development.themewant.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://themewant.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://themewant.com/
Exact versions in response headers let anyone match the server against a CVE feed without touching it.
What to do
Strip version tokens (`ServerTokens Prod`, `server_tokens off`, remove X-Powered-By).
asset: https://themewant.com/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://themewant.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: themewant.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: themewant.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: themewant.com

final https://themewant.com/status 200time 914msstack cloudflare · PHP/8.1.34 · WordPress 7.1

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

!Cookie PHPSESSID
Secure · no HttpOnly · no SameSite

✓Receives mail via 2 servers
mx1.titan.email mx2.titan.email
!SPFends in ~all
v=spf1 include:spf.titan.email ~all
!DMARCp=none
v=DMARC1;p=none;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
ns1.dns-parking.com ns2.dns-parking.com

✓Registered with HOSTINGER operations, UAB3.7 years old
themewant.com
✓Registration expiry487 days
2028-01-07
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns1.dns-parking.com ns2.dns-parking.com

Address	Ports	CVEs	Edge	Network
84.32.84.107 echo.themewant.com +3	80443	12	direct	—
88.222.222.83 echo.themewant.com +4	80443	0	direct	—
88.222.222.80 account.themewant.com +3	80443	0	direct	—
84.32.84.121 account.themewant.com +3	80443	6	direct	—
77.37.48.66 development.themewant.com	443	0	direct	—
179.61.189.29 development.themewant.com	443	0	direct	—
178.16.134.165 themewant.com +15	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.

themewant.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames