Security snapshot
Across 5 hinode 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 usernames60%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS80%vs 96.2% avg
What stands out
TLDWP currently associates 5 indexed WordPress sites with hinode, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 60% versus 38.5% overall (+21.5 percentage points).
Header-grade F is 100% vs 82.5% overall (+17.5 pp); HTTPS adoption is 80% vs 96.2% overall (-16.2 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected hinode, 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 |
|---|---|---|---|---|
| h*n*d*h*i*u.com (WP 7.1) | — | F | Sep 9, 2026 | |
| h*n*d*s*o*j*.c*.jp | — | F | Aug 27, 2026 | |
| h*n*d*.o*.jp | — | F | Aug 26, 2026 | |
| h*n*d*-*o*d*n*s.c*.jp (WP 7.1) | — | F | Aug 24, 2026 | |
| h*n*d*-*p.jp (WP 6.8.3) | — | F | Jul 19, 2026 |
Page 1 of 1