Security snapshot
Across 6 uplift-child WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 17%
Grade D 0%
Grade F 83%
Fail the header check (F)83%vs 82.5% avg
Leak usernames33%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 6 indexed WordPress sites with uplift-child, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 33.3% versus 38.5% overall (-5.2 percentage points).
HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp); Header-grade F is 83.3% vs 82.5% overall (+0.8 pp).
These are observational associations among sites where TLDWP detected uplift-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 |
|---|---|---|---|---|
| k*y*v*r.it (WP 5.5.20) | — | F | Sep 5, 2026 | |
| k*o*c*o*d.com (WP 6.1.10) | — | F | Jul 20, 2026 | |
| s*o*t*a*s*i*i*v*s*.com (WP 6.1.10) | — | F | Jul 20, 2026 | |
| s*o*t*a*s*i*.com (WP 6.1.10) | — | F | Jul 20, 2026 | |
| s*y*i*g.c*m.au | — | C | Jul 19, 2026 | |
| a*e*p*x.com (WP 7.0.2) | — | F | Jul 19, 2026 |
Page 1 of 1