Security snapshot
Across 13 wp-comment-validation WordPress sites indexed by TLDWP, compared to the all-WordPress average.
What stands out
TLDWP currently associates 13 indexed WordPress sites with wp-comment-validation, equivalent to 0% of the current WordPress dataset.
The largest measured difference is header-grade F: 100% versus 82.5% overall (+17.5 percentage points).
Sensitive-file exposure is 7.7% vs 1.8% overall (+5.9 pp); HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Username enumeration is 38.5% vs 38.5% overall (0 pp).
These are observational associations among sites where TLDWP detected wp-comment-validation, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.
wp comment validation
wp-comment-validation can adds custom message for wordpress default comment submission form validation. It is easy to use , just install plugin and validation will be there on the comment submission form on whole site also can be set your own message to display on error just go to setting page of wp comment validation at left panel in wordpress.
| Domain | Version | Exposures | Headers | Last Checked |
|---|---|---|---|---|
| e*i*e*g*b*e*.com (WP 6.0.14) | — | F | Sep 5, 2026 | |
| r*d*o*g*y.net | — | F | Sep 4, 2026 | |
| w*i*e*d*a*.com (WP 7.1) | — | F | Aug 30, 2026 | |
| r*d*o*g*y.com | — | F | Aug 30, 2026 | |
| j*b*-*r*c.com | — | F | Aug 29, 2026 | |
| b*n*a*s*.com | — | F | Aug 24, 2026 | |
| t*o*e*a*h*l*c*e*.com | — | F | Aug 24, 2026 | |
| c*n*e*t*e*a*k*t*n*.com | — | F | Aug 23, 2026 | |
| b*w*r*l*n*.c*m.au (WP 5.3.21) | — | F | Aug 20, 2026 | |
| j*c*a*d*e*v*c*s.com | — | F | Aug 16, 2026 | |
| s*u*e*t*d*s*i*a*i*n.com (WP 6.2.9) | — | F | Jul 26, 2026 | |
| t*e*b*a*k*l*o*.com (WP 6.6.5) | — | F | Jul 25, 2026 | |
| c*n*m*e*c*i*o.com (WP 6.9.5) | — | F | Jul 22, 2026 |