Security snapshot
Across 4 js_composerxx 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 usernames75%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 4 indexed WordPress sites with js_composerxx, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 75% versus 38.5% overall (+36.5 percentage points).
Header-grade F is 100% vs 82.5% overall (+17.5 pp); HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected js_composerxx, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| z*p*a*a*i*n.com (WP 6.8.8) | F | Sep 3, 2026 | |
| c*b*l*s*e*.o*g.br (WP 7.0.4) | F | Aug 31, 2026 | |
| c*o*e*r*h.com | F | Aug 21, 2026 | |
| c*i*i*s*e*a*p*s.com (WP 7.0.4) | F | Aug 18, 2026 |
Page 1 of 1