Security snapshot
Across 8 wp-file-bin 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 usernames38%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 8 indexed WordPress sites with wp-file-bin, 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).
HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp); Username enumeration is 37.5% vs 38.5% overall (-1 pp).
These are observational associations among sites where TLDWP detected wp-file-bin, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| k*j*k*b*o*.com (WP 6.1.12) | F | Sep 5, 2026 | |
| t*y*-*c.com (WP 6.3.10) | F | Sep 2, 2026 | |
| n*w*e*g*.jp | F | Aug 31, 2026 | |
| k*o*l*d*e*o*d*r.jp (WP 5.4.21) | F | Aug 19, 2026 | |
| w*k*y*m*-*c.net | F | Aug 17, 2026 | |
| p*u*i*u*.c*.jp | F | Aug 3, 2026 | |
| m*j*p*r*.com (WP 6.4.8) | F | Jul 27, 2026 | |
| s*k*o.jp (WP 7.0.2) | F | Jul 24, 2026 |
Page 1 of 1