Security snapshot
Across 3 js-o4w WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 0%
Grade D 0%
Grade F 100%
Fail the header check (F)100%vs 82.5% avg
Leak usernames67%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS67%vs 96.2% avg
What stands out
TLDWP currently associates 3 indexed WordPress sites with js-o4w, equivalent to 0% of the current WordPress dataset.
The largest measured difference is HTTPS adoption: 66.7% versus 96.2% overall (-29.5 percentage points).
Username enumeration is 66.7% vs 38.5% overall (+28.2 pp); Header-grade F is 100% vs 82.5% overall (+17.5 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected js-o4w, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
Js O4w
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| s*l*a*e.com (WP 4.5.33) | F | Aug 24, 2026 | |
| b*b*c*n*a*t.ru (WP 2.8.4) | F | Aug 5, 2026 | |
| t*e*u*c*e*s*o*k*.com (WP 5.7.15) | F | Jul 28, 2026 |
Page 1 of 1