Security snapshot
Across 6 css-selector-scheduler 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 usernames17%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS83%vs 96.2% avg
What stands out
TLDWP currently associates 6 indexed WordPress sites with css-selector-scheduler, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 16.7% versus 38.5% overall (-21.8 percentage points).
Header-grade F is 100% vs 82.5% overall (+17.5 pp); HTTPS adoption is 83.3% vs 96.2% overall (-12.9 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected css-selector-scheduler, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| m*s*m*r*e*.com | F | Sep 3, 2026 | |
| c*e*t*o*-*i*d*a*b*-*o*a*o.com | F | Aug 28, 2026 | |
| b*c*m*n*a*i*t*e*.fr | F | Aug 20, 2026 | |
| l*-*-*i*e*.fr | F | Aug 15, 2026 | |
| p*t*s*e*i*-*i*e.fr | F | Jul 31, 2026 | |
| c*n*y*b*a.com | F | Jul 26, 2026 |
Page 1 of 1