Security snapshot
Across 3 juve-paid-content 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 usernames0%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg
What stands out
TLDWP currently associates 3 indexed WordPress sites with juve-paid-content, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 0% versus 38.5% overall (-38.5 percentage points).
Header-grade F is 100% vs 82.5% overall (+17.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 juve-paid-content, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| j*v*-*t*u*r*a*k*.de | F | Sep 8, 2026 | |
| j*v*-*v.de | F | Sep 1, 2026 | |
| j*v*.de | F | Aug 24, 2026 |
Page 1 of 1