WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: auto-thickbox-plus (Used by 257 domains)

Security snapshot

Across 257 auto-thickbox-plus WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 2% Grade C 4% Grade D 4% Grade F 89%
Fail the header check (F)89%vs 82.5% avg
Leak usernames46%vs 38.5% avg
Expose a sensitive file3.1%vs 1.8% avg
Use HTTPS94%vs 96.2% avg

What stands out

TLDWP currently associates 257 indexed WordPress sites with auto-thickbox-plus, equivalent to 0% of the current WordPress dataset.

The largest measured difference is username enumeration: 46.3% versus 38.5% overall (+7.8 percentage points).

Header-grade F is 89.5% vs 82.5% overall (+7 pp); HTTPS adoption is 94.2% vs 96.2% overall (-2 pp); Sensitive-file exposure is 3.1% vs 1.8% overall (+1.3 pp).

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

Infrastructure patterns

Infrastructure detected alongside auto-thickbox-plus. Percentages are within sites where that specific signal was detectable; the baseline compares the same signal across detected WordPress sites overall.

Co-occurrence describes technologies observed on the same sites. Detection coverage varies by signal, and an association does not imply that one technology caused or selected another.

auto-thickbox-plus 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 Version Exposures Headers Last Checked
s*a*n*u*t*r*s*f*r*i.com (WP 7.0.2) 1.9· 85% conf. F Sep 9, 2026
s*a*e*e*t*r.com (WP 7.0.4) 1.6· 85% conf. F Sep 9, 2026
k*i*k*b*e*.com (WP 6.1.12) 1.9· 85% conf. F Sep 9, 2026
t*u*k*e*a*r*e*i*n.com (WP 7.1) F Sep 8, 2026
r*x*o*h*u*.com F Sep 8, 2026
b*a*n*c*n*i*r*e.com (WP 6.7.7) F Sep 8, 2026
e*p*d*t*o*-*d*e*t*r*s.com (WP 7.0.4) F Sep 7, 2026
h*d*n*m*s*o*m*r*s*r*a*.com (WP 6.9.7) F Sep 7, 2026
k*r*l*e*d*e*r*w*r*s.com (WP 7.0.4) F Sep 7, 2026
p*k*c*.si (WP 5.1.19) F Sep 7, 2026
k*r*d*-*m*l*.com (WP 6.8.8) F Sep 7, 2026
i*h*k*w*m*i.com (WP 4.7.29) F Sep 7, 2026
e*t*t*k*i*l*r.com (WP 4.6.29) F Sep 7, 2026
d*s*g*s*m*r*t*n.com (WP 7.0.4) F Sep 7, 2026
m*l*n*e*.com (WP 7.0.4) F Sep 6, 2026
h*r*s*y*h*n*e.com (WP 4.1) F Sep 6, 2026
k*n*m*n*-*e*z*i.com (WP 5.1.19) F Sep 6, 2026
g*z*n*t*t*a*.nl (WP 6.8.8) D Sep 6, 2026
b*r*e*u*w*n*a*a*d*.com (WP 7.1) F Sep 6, 2026
b*r*e*u*-*i*e*a*a*d*.com (WP 7.1) F Sep 6, 2026
s*f*a*e*d*r.com (WP 7.1) F Sep 6, 2026
t*r*n.c*.jp (WP 7.1) D Sep 6, 2026
r*f*e*t*o*s*y*w.com (WP 7.0.4) F Sep 5, 2026
s*r*h*o*l*e*.de (WP 4.4.34) F Sep 5, 2026
d*n*a*a*s*c*a*e*c*.com (WP 7.1) B Sep 5, 2026
t*b*c*f*.com (WP 5.0.22) F Sep 5, 2026
t*a*e*t*b*i.com (WP 7.1) F Sep 5, 2026
a*y*n*p*l*.com F Sep 5, 2026
s*a*b*o*n*d*t*i*w*l*o*.com (WP 6.9.7) F Sep 5, 2026
s*b*b*u*r*.ch (WP 5.2.26) F Sep 5, 2026
n*k*g*j*n*o.com (WP 6.9.4) F Sep 4, 2026
b*r*o*l*d*c*b*n*s.org F Sep 4, 2026
h*a*t*h*l*.com (WP 6.0.14) F Sep 4, 2026
b*r*b*i*h*.c*m.au (WP 7.0.4) F Sep 4, 2026
r*c*p*f*r*u*i*e*s*u*c*s*.com F Sep 4, 2026
h*a*v*t.com (WP 7.0.4) F Sep 4, 2026
z*o*a*k*n*.com F Sep 4, 2026
p*a*d*n*o*e*.gr F Sep 4, 2026
c*y*t*k*n*l*.com (WP 7.1) F Sep 4, 2026
v*l*s*a*k.nl F Sep 3, 2026
z*g*a*o*.com F Sep 3, 2026
e*p*c*-*r*s*m*g*z*n*.com (WP 5.1.24) F Sep 3, 2026
a*t*v*t*a*u*n*.com (WP 7.0.4) D Sep 3, 2026
o*a*h*-*p.com (WP 4.7.29) F Sep 3, 2026
s*o*e*i*-*r*v*t*-*o*r*.com (WP 5.2.21) F Sep 2, 2026
n*r*h*n*i*s*u*y*o*r*.com (WP 7.0.2) F Sep 1, 2026
t*n*h*n*r*n*o.com (WP 5.1.19) F Sep 1, 2026
j*u*n*y*o*a*b*.com F Aug 31, 2026
v*r*h*a*e*.de (WP 5.8.15) F Aug 31, 2026
y*m*b*t*i.com (WP 7.1) F Aug 31, 2026
t*o*s*n*.com (WP 5.1.6) F Aug 30, 2026
m*i*e*o*s*e*p*t*i*.com F Aug 30, 2026
j*h*w*r*h*m*l*s*i*a*o*t*o*a*h*.com F Aug 30, 2026
r*b*i*a*k*n*.com (WP 7.0.4) F Aug 29, 2026
h*l*a*t*.com (WP 7.1) F Aug 29, 2026
b*m*a*.com (WP 6.6.2) F Aug 29, 2026
m*n*r*d*r*n*s*s*e*s.com C Aug 28, 2026
m*n*r*d*r*n*h*n*e.com C Aug 28, 2026
m*n*r*d*r*n*.com C Aug 28, 2026
b*l*i*n*i*k*.com F Aug 28, 2026
s*o*a*-*a*o*-*o*p*n*.com F Aug 28, 2026
n*d*r*a*d*e*h*p*e*c*u*.nl (WP 7.1) F Aug 28, 2026
a*i*e*e*-*a*i*.com F Aug 28, 2026
t*h*.com (WP 4.0.38) F Aug 27, 2026
g*c*a*n*l*n*.com (WP 4.4.25) F Aug 27, 2026
g*h*n*s.com F Aug 27, 2026
s*a*t*e*.net (WP 7.0.4) F Aug 27, 2026
s*i*a*a*o*f.com (WP 5.7.17) F Aug 27, 2026
s*i*i*a*-*a*a*o.com (WP 5.8.15) F Aug 26, 2026
b*u*s*r*h*n*.com (WP 7.1) F Aug 26, 2026
w*l*e*e*t*o*i*s.com F Aug 26, 2026
a*t*a*e*t.ru (WP 4.0) F Aug 26, 2026
e*o*i*i*p*r*s.com (WP 6.6.7) F Aug 26, 2026
c*n*e*n*d*o*w*r*i*g*h*l*r*n.org (WP 7.1) F Aug 26, 2026
a*r*d*s.es F Aug 26, 2026
w*c*m*c*f*r*e.com F Aug 25, 2026
p*r*u*t*o*i*t*c*.com F Aug 25, 2026
m*h*n*y*c*.com F Aug 25, 2026
s*e*c*l*b*n*.o*g.ua (WP 5.6.19) F Aug 25, 2026
e*y.es (WP 7.1) F Aug 25, 2026
p*r*h*s*n*.com (WP 4.8.11) F Aug 25, 2026
d*d*s*g*.org (WP 7.0.4) F Aug 24, 2026
l*f*s*y*e*a*u*p*c*.com F Aug 24, 2026
l*f*s*y*e*o*k*t*a*e*.com F Aug 24, 2026
c*n*p*e*s.ir (WP 7.1) F Aug 24, 2026
a*c*l*r*e*o*t*v*.c*m.mx (WP 7.1) F Aug 24, 2026
d*p*.si (WP 4.7.29) F Aug 24, 2026
c*l*r*v*r*r*.com F Aug 24, 2026
p*d*c*c*e*n*n*.com (WP 7.1) F Aug 23, 2026
2*r*.com (WP 6.5.10) F Aug 23, 2026
s*i*t*c*o*s*i.com (WP 7.1) F Aug 23, 2026
w*p*l*s*m*l*s.com F Aug 23, 2026
2*4*r*.com (WP 6.5.10) F Aug 23, 2026
p*e*s*s*b*c*i*e*i*m.com (WP 3.4.1) F Aug 22, 2026
2*0*c*u*c*.com (WP 5.4.21) F Aug 22, 2026
m*y*z*k*-*e*t*i.jp (WP 6.7.7) F Aug 22, 2026
o*m*w*.o*.jp (WP 5.1) F Aug 22, 2026
w*b*u*g*o*d*s*g*s.com (WP 7.1) F Aug 22, 2026
b*l*i*n*i*k*.it F Aug 21, 2026
e*c*e*i*e*a*d*u*.com (WP 4.7.35) F Aug 21, 2026