Security snapshot
Across 6 induxe-child WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 0%
Grade D 67%
Grade F 33%
Fail the header check (F)33%vs 82.6% avg
Leak usernames0%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 6 indexed WordPress sites with induxe-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 33.3% versus 82.6% overall (-49.3 percentage points).
Username enumeration is 0% vs 38.6% overall (-38.6 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 induxe-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 |
|---|---|---|---|---|
| v*n*i*k*u*t*n*n*i*h*i*g.nl (WP 7.1) | — | D | Sep 7, 2026 | |
| v*n*e*s*l.nl (WP 7.1) | — | D | Aug 26, 2026 | |
| a*n*s*e*l*.com | — | F | Aug 20, 2026 | |
| m*o*w*r*k.nl (WP 7.0.4) | — | D | Aug 16, 2026 | |
| p*r*o*e*.cz (WP 6.9.5) | — | F | Aug 6, 2026 | |
| m*o*w*r*k.com (WP 7.0.2) | — | D | Jul 29, 2026 |
Page 1 of 1