Security snapshot
Across 4 irepair-child 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.6% avg
Leak usernames75%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 4 indexed WordPress sites with irepair-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 75% versus 38.6% overall (+36.4 percentage points).
Header-grade F is 100% vs 82.6% overall (+17.4 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 irepair-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 |
|---|---|---|---|---|
| b*a*k*o*e*t*t*n*n*.com (WP 6.7.1) | — | F | Aug 31, 2026 | |
| s*u*i*a*r*m*n*a.com (WP 6.8.8) | — | F | Aug 19, 2026 | |
| s*r*i*e*t*c*n*k.center (WP 7.0) | — | F | Aug 4, 2026 | |
| h*n*y*t*b*e*-*e*a*a*u*.de (WP 7.0.2) | — | F | Jul 24, 2026 |
Page 1 of 1