Security snapshot
Across 6 booky 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 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 6 indexed WordPress sites with booky, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 100% versus 82.5% overall (+17.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 booky, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| t*a*h*y*t*l*s*y.com | F | Sep 4, 2026 | |
| j*l*a*k*n*e*e.com | F | Sep 2, 2026 | |
| m*s*c*p*i*a*a.pl | F | Aug 28, 2026 | |
| b*o*y.jp (WP 7.0.2) | F | Aug 2, 2026 | |
| c*n*l*i*s*n*h*n*.com | F | Jul 27, 2026 | |
| d*g*t*l*i*h*h*u*e*t*d*o*.com | F | Jul 22, 2026 |
Page 1 of 1