Security snapshot
Across 6 jarvis_wp-child WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 0%
Grade D 17%
Grade F 83%
Fail the header check (F)83%vs 82.6% avg
Leak usernames67%vs 38.7% avg
Expose a sensitive file33.3%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 6 indexed WordPress sites with jarvis_wp-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is sensitive-file exposure: 33.3% versus 1.8% overall (+31.5 percentage points).
Username enumeration is 66.7% vs 38.7% overall (+28 pp); HTTPS adoption is 100% vs 96.3% overall (+3.7 pp); Header-grade F is 83.3% vs 82.6% overall (+0.7 pp).
These are observational associations among sites where TLDWP detected jarvis_wp-child, 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 |
|---|---|---|---|---|
| t*c*e*i*o*o*l*b*a*z*.com (WP 7.1) | 3.8· 100% conf. | F | Sep 9, 2026 | |
| s*o*a*a*e*y.de (WP 6.5.10) | — | F | Sep 5, 2026 | |
| a*z*a.es (WP 6.9.5) | — | F | Aug 17, 2026 | |
| j*s*l*i*r*d*i*u*z*a*a*g*.com (WP 6.9.5) | — | F | Aug 14, 2026 | |
| v*s*a*e*i*e*c*.com (WP 7.0.2) | — | D | Jul 27, 2026 | |
| m*r*a*b*i*.com (WP 7.0.2) | — | F | Jul 23, 2026 |
Page 1 of 1