Security snapshot
Across 4 neobeat-child WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 25%
Grade D 25%
Grade F 50%
Fail the header check (F)50%vs 82.5% avg
Leak usernames50%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 neobeat-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 50% versus 82.5% overall (-32.5 percentage points).
Username enumeration is 50% vs 38.5% overall (+11.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 neobeat-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 |
|---|---|---|---|---|
| m*i*-*t*g*p*o*u*t*o*s.com (WP 7.1) | — | F | Aug 25, 2026 | |
| d*t*k*f*s*.com (WP 7.0.3) | — | C | Aug 16, 2026 | |
| p*y*a*j*v*n*a*d.com | — | D | Jul 23, 2026 | |
| c*l*r*e*t*v*l.fr (WP 7.0.2) | — | F | Jul 23, 2026 |
Page 1 of 1