Security snapshot
Across 5 cvh-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 usernames0%vs 38.7% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 5 indexed WordPress sites with cvh-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 0% versus 38.7% overall (-38.7 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 cvh-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 |
|---|---|---|---|---|
| l*c*t*n*e*d*.de | 5.0.3· 100% conf. | F | Sep 11, 2026 | |
| t*v*b*r*t*h*i*e.de | — | F | Sep 6, 2026 | |
| e*r*p*a*f*s*i*a*s*m*i*.com | — | F | Sep 5, 2026 | |
| y*u*o*e.org | — | F | Aug 23, 2026 | |
| p*-*i*e*t.de | — | F | Aug 22, 2026 |
Page 1 of 1