Security snapshot
Across 4 js_composer_decode 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 usernames25%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_composer_decode, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 100% versus 82.5% overall (+17.5 percentage points).
Username enumeration is 25% vs 38.5% overall (-13.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_composer_decode, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Version | Exposures | Headers | Last Checked |
|---|---|---|---|---|
| l*r*e*o*k*n.com (WP 6.8.8) | — | F | Sep 1, 2026 | |
| s*a*t*d*.com (WP 4.8) | — | F | Aug 26, 2026 | |
| l*o*a*r*n*u*i*.com (WP 7.1) | — | F | Aug 21, 2026 | |
| i*g*s*.com (WP 4.5.9) | — | F | Jul 23, 2026 |
Page 1 of 1