Security snapshot
Across 7 wp-spinnr-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.5% avg
Leak usernames14%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS71%vs 96.2% avg
What stands out
TLDWP currently associates 7 indexed WordPress sites with wp-spinnr-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is HTTPS adoption: 71.4% versus 96.2% overall (-24.8 percentage points).
Username enumeration is 14.3% vs 38.5% overall (-24.2 pp); Header-grade F is 100% vs 82.5% overall (+17.5 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected wp-spinnr-child, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| g*o*l*d*e*.c*m.au (WP 7.1) | F | Aug 25, 2026 | |
| b*b*l*.c*m.au (WP 7.1) | F | Aug 22, 2026 | |
| v*r*u*l*l*e*h*b.ph (WP 7.0.2) | F | Aug 1, 2026 | |
| b*i*l*a*c*r*m*v*l*s*s*e*t*.c*m.au (WP 7.0.2) | F | Jul 31, 2026 | |
| b*l*a*d*o*g*t*.c*m.au (WP 7.0.2) | F | Jul 28, 2026 | |
| c*m*u*i*y*i*s*.c*m.au | F | Jul 24, 2026 | |
| k*n*.c*m.au | F | Jul 17, 2026 |
Page 1 of 1