Security snapshot
Across 7 jq WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 0%
Grade D 14%
Grade F 86%
Fail the header check (F)86%vs 82.6% avg
Leak usernames29%vs 38.6% avg
Expose a sensitive file14.3%vs 1.8% avg
Use HTTPS71%vs 96.3% avg
What stands out
TLDWP currently associates 7 indexed WordPress sites with jq, equivalent to 0% of the current WordPress dataset.
The largest measured difference is HTTPS adoption: 71.4% versus 96.3% overall (-24.9 percentage points).
Sensitive-file exposure is 14.3% vs 1.8% overall (+12.5 pp); Username enumeration is 28.6% vs 38.6% overall (-10 pp); Header-grade F is 85.7% vs 82.6% overall (+3.1 pp).
These are observational associations among sites where TLDWP detected jq, 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 |
|---|---|---|---|---|
| a*p*d*.com (WP 5.0.21) | — | F | Sep 10, 2026 | |
| s*c*a*r*p*r*.ch (WP 4.5.12) | 3.4· 100% conf. | F | Sep 9, 2026 | |
| j*l*u*s*.com (WP 7.1) | — | F | Sep 1, 2026 | |
| v*d*o*k*i*y.cz | — | F | Aug 28, 2026 | |
| e*l*o*t*p*e*n.com (WP 4.6.1) | — | D | Aug 25, 2026 | |
| c*e*r*i*l*w*t*r*e*e*.com (WP 7.0.4) | — | F | Aug 17, 2026 | |
| s*h*l*r*y*o*o*r*s.com (WP 2.9.2) | — | F | Aug 2, 2026 |
Page 1 of 1