Security snapshot
Across 2 cup_o_java 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.6% avg
Leak usernames50%vs 38.6% avg
Expose a sensitive file50%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 2 indexed WordPress sites with cup_o_java, equivalent to 0% of the current WordPress dataset.
The largest measured difference is sensitive-file exposure: 50% versus 1.8% overall (+48.2 percentage points).
Header-grade F is 100% vs 82.6% overall (+17.4 pp); Username enumeration is 50% vs 38.6% overall (+11.4 pp); HTTPS adoption is 100% vs 96.3% overall (+3.7 pp).
These are observational associations among sites where TLDWP detected cup_o_java, 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 |
|---|---|---|---|---|
| m*e*e*p*a*e.com | — | F | Aug 17, 2026 | |
| p*z*a*n*s.c*m.ua (WP 5.8.13) | — | F | Aug 4, 2026 |
Page 1 of 1