WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: t42-content-protector (Used by 65 domains)

Security snapshot

Across 65 t42-content-protector WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 8% Grade C 2% Grade D 17% Grade F 74%
Fail the header check (F)74%vs 82.5% avg
Leak usernames34%vs 38.5% avg
Expose a sensitive file1.5%vs 1.8% avg
Use HTTPS92%vs 96.2% avg

What stands out

TLDWP currently associates 65 indexed WordPress sites with t42-content-protector, equivalent to 0% of the current WordPress dataset.

The largest measured difference is header-grade F: 73.8% versus 82.5% overall (-8.7 percentage points).

Username enumeration is 33.8% vs 38.5% overall (-4.7 pp); HTTPS adoption is 92.3% vs 96.2% overall (-3.9 pp); Sensitive-file exposure is 1.5% vs 1.8% overall (-0.3 pp).

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

t42-content-protector 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
s*u*c*a.ir F Sep 8, 2026
m*d*c*l*t*d*z*n*.com (WP 7.1) F Sep 8, 2026
f*l*e*p*r*d*s*.com (WP 7.1) D Sep 7, 2026
e*m*r*n*g*o.com F Sep 7, 2026
r*s*v*r.com (WP 7.0.4) F Sep 7, 2026
h*n*a*v*d*.com F Sep 6, 2026
t*i*u*a*e*t*p*r*.com (WP 7.1) F Sep 6, 2026
e*s*o*i*s*l*b*l.com (WP 7.1) F Sep 6, 2026
k*l*v*x.com B Sep 6, 2026
l*s*u*d*e*e*.at F Sep 6, 2026
k*k*a*o*v*.com (WP 7.1) F Sep 5, 2026
e*s*o*i*s.com (WP 7.1) F Sep 5, 2026
t*i*u*a*e*t*p*r*.c*m.br (WP 7.1) F Sep 5, 2026
h*a*t*t*p*f*r*o*d*i*y.com (WP 6.8.3) F Sep 4, 2026
z*r*s*u*i*s.com (WP 7.1) D Sep 4, 2026
a*l*a*c*u*e*t*n*o.com (WP 6.7.7) F Sep 4, 2026
d*r*t*b*p*o*o*r*p*e*.com (WP 7.1) D Sep 2, 2026
z*i*a*r*i.com (WP 7.1) F Sep 1, 2026
h*r*r*c*t*n*.com F Sep 1, 2026
s*x*y*o*r*e*w*r*s.com F Aug 31, 2026
b*k*s*o*t*h*g*e*d.com (WP 6.8.8) F Aug 31, 2026
q*i*e*r*.com D Aug 29, 2026
l*t*l*h*n*a*.com D Aug 28, 2026
s*m*e*n*c*l*.de F Aug 27, 2026
k*r*n*i*s*m*n*.de F Aug 27, 2026
e*o*a*i.com B Aug 26, 2026
e*o*a*i.com F Aug 26, 2026
m*g*s*e*i*l*g*l.com (WP 7.1) F Aug 24, 2026
j*m*b*k*t*e*.com D Aug 23, 2026
g*o*p*-*l*t*n*m.com D Aug 23, 2026
p*i*e*a*i*e*.mx (WP 7.0.4) F Aug 23, 2026
a*t*o*l*u*e*u*d*r*o*d.com (WP 7.1) F Aug 22, 2026
c*f*d*r*.ir (WP 6.7.7) C Aug 22, 2026
c*a*h*r*b*.com (WP 7.1) F Aug 22, 2026
a*c*g*t*o*l*n*.com F Aug 21, 2026
t*h*a*-*l*m*e*.com F Aug 21, 2026
i*d*a*w*t*r*r*s*s.com (WP 7.0.3) F Aug 19, 2026
v*n*s*e*a*.com (WP 7.0.4) F Aug 18, 2026
b*n*k*r*s*l.com (WP 6.8.2) F Aug 16, 2026
h*i*m*n*-*o*t*f*r.de F Aug 16, 2026
d*s*f*l*.com (WP 7.0.3) F Aug 15, 2026
j*n*l*e*a*.com D Aug 15, 2026
p*t*r*y.com B Aug 15, 2026
p*s*i*n*p*.com D Aug 15, 2026
o*c*r*t*.com (WP 6.1.11) F Aug 7, 2026
z*i*o*n.c*m.pk F Aug 4, 2026
m*l*y*.com B Jul 31, 2026
t*e*o*e*l*n*c*.com (WP 7.0.2) F Jul 31, 2026
t*l*g*c*b*r*r*y.in (WP 7.0.2) F Jul 30, 2026
f*r*n*i*s*e*i*.com (WP 7.0.2) F Jul 30, 2026
i*s*m*e*l*.com F Jul 29, 2026
h*i*s*l.com (WP 7.0.2) F Jul 29, 2026
g*o*g*a*j*u*n*l.com (WP 7.0.2) F Jul 29, 2026
l*u*e*u*d*r*o*d*u*h*r.com (WP 7.0.2) F Jul 29, 2026
l*u*e*u*d*r*o*d.com (WP 7.0.2) F Jul 29, 2026
a*k*l*s*e*.com (WP 7.0.2) F Jul 26, 2026
i*s*i*u*o*e*d*m*e*t*e*p*e*a*i*l.com B Jul 25, 2026
h*p*s*a*.com (WP 7.0.2) F Jul 22, 2026
b*r*e*s*m*.com (WP 7.0.2) D Jul 21, 2026
h*m*r*h*n.com (WP 7.0.2) F Jul 21, 2026
a*-*h.de F Jul 20, 2026
a*p*m*m*n*.com F Jul 20, 2026
m*n*s*i*.gr (WP 7.0.2) F Jul 20, 2026
m*m*r*o*a*t.com (WP 7.0.2) D Jul 19, 2026
f*r*d*a*a*i.com (WP 7.0.2) F Jul 19, 2026