Security snapshot
Across 4 custom-comment-block WordPress sites indexed by TLDWP, compared to the all-WordPress average.
Grade A 0%
Grade B 0%
Grade C 0%
Grade D 25%
Grade F 75%
Fail the header check (F)75%vs 82.6% avg
Leak usernames0%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.3% avg
What stands out
TLDWP currently associates 4 indexed WordPress sites with custom-comment-block, equivalent to 0% of the current WordPress dataset.
The largest measured difference is username enumeration: 0% versus 38.6% overall (-38.6 percentage points).
Header-grade F is 75% vs 82.6% overall (-7.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 custom-comment-block, 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 |
|---|---|---|---|---|
| c*s*n*-*i*z.c*m.ua | — | F | Aug 17, 2026 | |
| n*n*s*a*y.org | — | F | Aug 15, 2026 | |
| a*i*t*r*g*m*-*p*.in | — | F | Jul 27, 2026 | |
| a*i*t*r*u*.net | — | D | Jul 22, 2026 |
Page 1 of 1