Security snapshot
Across 2 _js_composer_salient 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 usernames100%vs 38.5% avg
Expose a sensitive file50%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 2 indexed WordPress sites with _js_composer_salient, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 100% versus 38.5% overall (+61.5 percentage points).
Sensitive-file exposure is 50% vs 1.8% overall (+48.2 pp); Header-grade F is 100% vs 82.5% overall (+17.5 pp); HTTPS adoption is 100% vs 96.2% overall (+3.8 pp).
These are observational associations among sites where TLDWP detected _js_composer_salient, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| i*t*r*a*e*f*r*a*i*n.net (WP 6.7.4) | F | Sep 4, 2026 | |
| m*c*a*l*k*y.com (WP 7.0.2) | F | Jul 22, 2026 |
Page 1 of 1