Security snapshot
Across 5 cwi-custom-filter WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 20%
Grade B 20%
Grade C 40%
Grade D 0%
Grade F 20%
Fail the header check (F)20%vs 82.6% avg
Leak usernames20%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 5 indexed WordPress sites with cwi-custom-filter, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 20% versus 82.6% overall (-62.6 percentage points).
Username enumeration is 20% vs 38.6% overall (-18.6 pp); HTTPS adoption is 100% vs 96.3% overall (+3.7 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).
These are observational associations among sites where TLDWP detected cwi-custom-filter, 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*b*e*s*o*t*.com (WP 7.1) | — | C | Sep 5, 2026 | |
| s*a*e*o*s*l*i*g.com (WP 7.1) | — | F | Aug 28, 2026 | |
| s*c*i*c.com (WP 7.1) | — | A | Aug 23, 2026 | |
| s*a*e*c*m*u*i*y.com (WP 7.0.2) | — | B | Jul 23, 2026 | |
| a*g*m*.com (WP 6.9.5) | — | C | Jul 20, 2026 |
Page 1 of 1