Security snapshot
Across 7 billey-child WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 14%
Grade C 0%
Grade D 0%
Grade F 86%
Fail the header check (F)86%vs 82.6% avg
Leak usernames14%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 7 indexed WordPress sites with billey-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 14.3% versus 38.6% overall (-24.3 percentage points).
HTTPS adoption is 100% vs 96.3% overall (+3.7 pp); Header-grade F is 85.7% vs 82.6% overall (+3.1 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected billey-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 |
|---|---|---|---|---|
| h*a*i*h*g*o*a*.com (WP 6.8.2) | — | F | Sep 3, 2026 | |
| b*p*n*o*i.com (WP 7.1) | — | F | Aug 29, 2026 | |
| l*s*c*r*s*s.com (WP 5.7.17) | — | F | Aug 21, 2026 | |
| h*a*i*h*.c*m.ar (WP 6.8.2) | — | F | Aug 1, 2026 | |
| r*o*s*e*a*m*.com | — | B | Jul 23, 2026 | |
| s*g*a*u*e*c*m*u*i*a*i*n.com (WP 7.0.2) | — | F | Jul 22, 2026 | |
| s*g*a*u*e*c*m.com (WP 7.0.2) | — | F | Jul 22, 2026 |
Page 1 of 1