Security snapshot
Across 4 anvogue-child WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 0%
Grade D 50%
Grade F 50%
Fail the header check (F)50%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 4 indexed WordPress sites with anvogue-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 0% versus 38.6% overall (-38.6 percentage points).
Header-grade F is 50% vs 82.6% overall (-32.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 anvogue-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 |
|---|---|---|---|---|
| d*k*h*m*.com (WP 6.9.4) | — | F | Aug 30, 2026 | |
| b*-*p*r*.co | — | D | Aug 25, 2026 | |
| p*a*n*x*l*s*v*.com (WP 7.0.2) | — | F | Aug 24, 2026 | |
| s*n*o*e.com (WP 7.0.4) | — | D | Aug 18, 2026 |
Page 1 of 1