Security snapshot
Across 7 screen-stay-awake WordPress sites indexed by TLDWP, compared to the all-WordPress average.
What stands out
TLDWP currently associates 7 indexed WordPress sites with screen-stay-awake, equivalent to 0% of the current WordPress dataset.
The largest measured difference is sensitive-file exposure: 14.3% versus 1.8% overall (+12.5 percentage points).
Username enumeration is 42.9% vs 38.5% overall (+4.4 pp); HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Header-grade F is 85.7% vs 82.5% overall (+3.2 pp).
These are observational associations among sites where TLDWP detected screen-stay-awake, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
Screen Stay Awake
Screen Stay Awake sends a request to your visitor’s browser asking it to keep their device’s screen on and prevent locking. This happens in the background and no user prompt is required. Screen Stay Awake is important for recipe websites and other how-to, informational websites. In these cases a visitor may go long periods without interacting with your site but still want to be able to read your content. To accomplish this, Screen Stay Awake uses the Screen Wake Lock browser API. The request is sent on page load. So…
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| x*e*h*.com | C | Sep 1, 2026 | |
| k*e*h*n*i*c*e*.de | F | Aug 29, 2026 | |
| w*r*p*e*n*i*e.com | F | Aug 29, 2026 | |
| g*s*i*c*e*.com (WP 7.1) | F | Aug 22, 2026 | |
| s*o*k*l*n*.com (WP 6.9.4) | F | Jul 25, 2026 | |
| g*s*i*c*e*.net (WP 7.0.2) | F | Jul 23, 2026 | |
| o*h*a*o*r*.com (WP 7.0.2) | F | Jul 19, 2026 |