Security snapshot
Across 6 diver-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.5% avg
Leak usernames17%vs 38.5% avg
Expose a sensitive file16.7%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 6 indexed WordPress sites with diver-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 16.7% versus 38.5% overall (-21.8 percentage points).
Header-grade F is 100% vs 82.5% overall (+17.5 pp); Sensitive-file exposure is 16.7% vs 1.8% overall (+14.9 pp); HTTPS adoption is 100% vs 96.2% overall (+3.8 pp).
These are observational associations among sites where TLDWP detected diver-child, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
Where these sites live — top 1 domain endings
.com
6
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| t*k*n*t*1*0*.com (WP 7.1) | F | Aug 27, 2026 | |
| s*i*a*u*c*r*e*.com (WP 6.9.7) | F | Aug 27, 2026 | |
| s*e*z*e*-*a*.com (WP 6.9.7) | F | Aug 26, 2026 | |
| a*-*i*u.com (WP 7.0.4) | F | Aug 18, 2026 | |
| h*p*o*t*.com | F | Jul 24, 2026 | |
| k*s*r*i*m.com (WP 5.2.24) | F | Jul 24, 2026 |
Page 1 of 1