Security snapshot
Across 2 js_composer-stop WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 0%
Grade D 50%
Grade F 50%
Fail the header check (F)50%vs 82.5% avg
Leak usernames0%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 2 indexed WordPress sites with js_composer-stop, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 0% versus 38.5% overall (-38.5 percentage points).
Header-grade F is 50% vs 82.5% overall (-32.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-stop, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| o*h*r*p*c*.com (WP 6.7.7) | F | Sep 6, 2026 | |
| j*k*r*a*o*p*.com (WP 6.0.14) | D | Aug 23, 2026 |
Page 1 of 1