WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: comment-images (Used by 64 domains)

Security snapshot

Across 64 comment-images WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 2% Grade C 0% Grade D 3% Grade F 95%
Fail the header check (F)95%vs 82.5% avg
Leak usernames41%vs 38.5% avg
Expose a sensitive file7.8%vs 1.8% avg
Use HTTPS97%vs 96.2% avg

What stands out

TLDWP currently associates 64 indexed WordPress sites with comment-images, equivalent to 0% of the current WordPress dataset.

The largest measured difference is header-grade F: 95.3% versus 82.5% overall (+12.8 percentage points).

Sensitive-file exposure is 7.8% vs 1.8% overall (+6 pp); Username enumeration is 40.6% vs 38.5% overall (+2.1 pp); HTTPS adoption is 96.9% vs 96.2% overall (+0.7 pp).

These are observational associations among sites where TLDWP detected comment-images, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.

comment-images Premium / Custom

This plugin is not available on WordPress.org. It may be a premium plugin, a custom plugin, or a plugin from a third-party marketplace.

Domain Exposures Headers Last Checked
p*a*u*t*c*o*l.org (WP 7.0.4) F Sep 8, 2026
j*s*i*a*o*m*t*c*.c*.uk (WP 7.1) F Sep 7, 2026
t*e*u*t*a.com F Sep 5, 2026
v*l*n*i*a*i*i*e*k*.com (WP 5.7) F Sep 5, 2026
t*a*e*b*b*o.com F Sep 4, 2026
m*k*h*u*e.org (WP 5.9.16) F Sep 4, 2026
h*l*l*.com (WP 6.8.3) F Sep 3, 2026
k*o*e*m*s*e*i*s.com B Sep 3, 2026
n*r*a*d*a*a*a*t*.com F Sep 1, 2026
s*e*c*b*o*e*y.com F Aug 31, 2026
a*g*e*s*n*s.com (WP 7.0) F Aug 30, 2026
j*l*a*o*-*r*.com (WP 4.9.10) D Aug 30, 2026
s*m*l*s*b*d*e*.com F Aug 29, 2026
e*-*o*d*n.com (WP 4.5.1) F Aug 28, 2026
h*c*a*h*m*.com F Aug 28, 2026
n*t*l*v*a*.com (WP 7.1) F Aug 27, 2026
e*i*i*-*p*r*m*n*s.com F Aug 27, 2026
t*k*y*u*k*d*e*e*y*h*r*.com F Aug 27, 2026
s*e*l*p*a*t*n.com (WP 7.0.4) F Aug 26, 2026
m*h*o*g*r*a*u*e*.com (WP 7.1) F Aug 25, 2026
b*b*e*m*a.ru F Aug 24, 2026
i*s*s*g*.com (WP 6.8.8) F Aug 21, 2026
c*r*g*o*l.com (WP 4.9.26) F Aug 21, 2026
y*c.org (WP 7.0.4) F Aug 20, 2026
p*r*u*e*0*s*m*l*s.com (WP 5.9.13) F Aug 20, 2026
a*e*c*-*i*e*t*.com (WP 4.7.35) F Aug 19, 2026
a*f*r*a*i*e*c*i*n*l*i*n*e.com (WP 7.0.3) F Aug 18, 2026
v*l*t*o*v*r*.ovh F Aug 17, 2026
p*l*e*k*.at (WP 6.7.7) F Aug 15, 2026
i*r*r*v*d*r*.com (WP 7.0) F Aug 15, 2026
i*r*x*a*.com (WP 7.0) F Aug 15, 2026
i*r*e*t*n*.com (WP 7.0) F Aug 15, 2026
s*i*k*n*n*s*.com (WP 4.9.31) F Aug 14, 2026
m*m*a*t.com (WP 4.9.31) F Aug 13, 2026
o*-*y*b*o*.de (WP 6.2.9) F Aug 3, 2026
b*g*h*w*a*a*k*.com F Aug 2, 2026
f*a*t*o*p*o*i*k.com (WP 4.1.9) F Jul 31, 2026
v*a*d*n*e.eu (WP 4.1.40) F Jul 29, 2026
c*l*a*u*1*7*.nl (WP 3.5.1) F Jul 28, 2026
b*t*i*l*-*e*-*i*r*s.ch (WP 6.2.9) F Jul 28, 2026
v*s*t*o*u*b*a*i*e*g*r*e.com F Jul 27, 2026
i*t*r*a*i*n*l*r*e*t*n*.com (WP 7.0) F Jul 26, 2026
v*l*n*i*a*i*i*e*k*.net (WP 5.7) F Jul 26, 2026
p*a*o*k*-*l*b.com (WP 6.1.10) F Jul 25, 2026
g*y*m*a*e*t*.com F Jul 25, 2026
t*a*l*t*e*y*0*4.com (WP 4.8.25) F Jul 24, 2026
h*u*t*d*l*c*s.org F Jul 24, 2026
c*o*o*e*u*.com (WP 6.7.5) F Jul 24, 2026
m*i*-*o*l*a*t.de (WP 6.9.4) D Jul 24, 2026
b*r*n*m*y*.com F Jul 23, 2026
c*i*l*s*n.com F Jul 23, 2026
r*d*n*o*d.com F Jul 22, 2026
c*e*t*v*b*n*t*r*.org F Jul 22, 2026
f*a*i*g*a*h*s*o*y.org (WP 7.0.2) F Jul 22, 2026
o*i*o*n*w*.com (WP 4.7.33) F Jul 22, 2026
p*w*r*e*v*c*r*b*t*.com F Jul 21, 2026
y*r*e*r*.am F Jul 20, 2026
e*f*c*i*e*e*f*r*a*c*e*g*n*e*i*g.com F Jul 20, 2026
j*s*i*a*o*m*t*c*.com (WP 7.0.2) F Jul 20, 2026
u*d*r*t*n*i*g*a*r*c*m*r*s*o*s.com (WP 6.0.12) F Jul 19, 2026
g*r*f*r*e*s.com (WP 7.0.2) F Jul 19, 2026
k*n*a*t*n*.com (WP 7.0.2) F Jul 18, 2026
d*-*o*d*n.com (WP 4.5.31) F Jul 18, 2026
v*l*c*t*-*o*t*e*l*e*.fr (WP 4.7.3) F Jul 18, 2026