Security snapshot
Across 3 js_composer-s3idf WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 33%
Grade D 0%
Grade F 67%
Fail the header check (F)67%vs 82.6% avg
Leak usernames67%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 3 indexed WordPress sites with js_composer-s3idf, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 66.7% versus 38.6% overall (+28.1 percentage points).
Header-grade F is 66.7% vs 82.6% overall (-15.9 pp); HTTPS adoption is 100% vs 96.3% overall (+3.7 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected js_composer-s3idf, 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 |
|---|---|---|---|---|
| s*i*f.us (WP 7.1) | — | F | Aug 30, 2026 | |
| s*i*f.in (WP 7.1) | — | F | Aug 30, 2026 | |
| s*i*f.org (WP 7.0.2) | — | C | Jul 25, 2026 |
Page 1 of 1