blackboxvoting.org security report

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

77risk

Critical

Exposed services or known CVEs need attention now.

1Critical

0High

6Medium

3Low

2Info

Collected 14 hours ago19.3sfrom cache

Certificate Transparency8
DNS resolution8
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs13
Registration
DNS posture2
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis12

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 66.223.49.26 (blackboxvoting.org), which advertise exim 4.99.5, lua-nginx-module 1.31.1.1, openresty 1.31.1.1, openssh 8.0. 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-60002 CVE-2026-60001 CVE-2026-60000 CVE-2026-59999 CVE-2026-59998 CVE-2026-59997 CVE-2026-59996 CVE-2026-59995 CVE-2026-35414 CVE-2026-35388 CVE-2026-35387 CVE-2026-35385 CVE-2025-32728 CVE-2025-26465 CVE-2023-51767 ...and 11 more
What to do
Confirm the running versions on 66.223.49.26 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-60002 ↗CVE-2026-60001 ↗CVE-2026-60000 ↗CVE-2026-59999 ↗CVE-2026-59998 ↗
asset: 66.223.49.26
66.223.49.26 (blackboxvoting.org) reports exim 4.99.5, lua-nginx-module 1.31.1.1, openresty 1.31.1.1, openssh 8.0. 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: 66.223.49.26
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 66.223.49.26:21
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://blackboxvoting.org/
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://blackboxvoting.org/
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://blackboxvoting.org/
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: blackboxvoting.org
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://blackboxvoting.org/
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://blackboxvoting.org/
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: blackboxvoting.org
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: blackboxvoting.org
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: blackboxvoting.org

final https://blackboxvoting.org/status 200time 1975msstack cloudflare · WordPress 5.5.20

✓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
blackboxvoting.org
!SPFends in ~all
v=spf1 ip4:66.223.49.26 ip4:66.223.49.27 include:_spf.epikwebhosting.com +a +mx +ip4:45.88.201.114 +ip4:45.88.201.68 +ip4:88.214.194.85 +ip4:88.214.193.70 +ip4:88.214.197.119 +ip4:88.214.197.116 ~all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:postmaster@blackboxvoting.org
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
gamma1.kc.epik.com gamma2.kc.epik.com

✓Registered with Epik LLC23.2 years old
blackboxvoting.org
✓Registration expiry2862 days
2034-07-09
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
gamma1.kc.epik.com gamma2.kc.epik.com

Address	Ports	CVEs	Edge	Network
66.223.49.26 blackboxvoting.org +11	215380110143443465587+5	26	direct	—

Archived URLs

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

blackboxvoting.org security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames