Security snapshot
Across 4 hctv-custom-header 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 usernames25%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 4 indexed WordPress sites with hctv-custom-header, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 100% versus 82.5% overall (+17.5 percentage points).
Username enumeration is 25% vs 38.5% overall (-13.5 pp); HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected hctv-custom-header, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| h*t*1.com (WP 7.0.2) | F | Jul 21, 2026 | |
| h*m*l*o*c*u*t*t*.com (WP 7.0.2) | F | Jul 21, 2026 | |
| h*m*l*o*c*u*t*t*l*v*s*o*.com (WP 7.0.2) | F | Jul 21, 2026 | |
| h*m*l*o*c*u*t*r*d*o.com (WP 7.0.2) | F | Jul 21, 2026 |
Page 1 of 1