Security snapshot
Across 6 js_composer_start WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 67%
Grade B 0%
Grade C 0%
Grade D 0%
Grade F 33%
Fail the header check (F)33%vs 82.5% avg
Leak usernames67%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 6 indexed WordPress sites with js_composer_start, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 33.3% versus 82.5% overall (-49.2 percentage points).
Username enumeration is 66.7% vs 38.5% overall (+28.2 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_composer_start, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| r*d*i*k.c*m.au (WP 7.0.4) | A | Sep 4, 2026 | |
| b*e*d*n*o*m*n.c*m.au (WP 6.9.7) | A | Sep 1, 2026 | |
| c*o*e*c*m*o*.c*m.au (WP 7.1) | A | Aug 31, 2026 | |
| j*b*a*.com | F | Aug 29, 2026 | |
| m*c*n*o*s.com (WP 6.9.6) | A | Aug 15, 2026 | |
| j*b*a*.c*m.au | F | Aug 4, 2026 |
Page 1 of 1