WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: lock-my-bp (Used by 52 domains)

Security snapshot

Across 52 lock-my-bp WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 2% Grade C 0% Grade D 10% Grade F 88%
Fail the header check (F)88%vs 82.6% avg
Leak usernames29%vs 38.6% avg
Expose a sensitive file3.8%vs 1.8% avg
Use HTTPS92%vs 96.3% avg

What stands out

TLDWP currently associates 52 indexed WordPress sites with lock-my-bp, equivalent to 0% of the current WordPress dataset.

The largest measured difference is username enumeration: 28.8% versus 38.6% overall (-9.8 percentage points).

Header-grade F is 88.5% vs 82.6% overall (+5.9 pp); HTTPS adoption is 92.3% vs 96.3% overall (-4 pp); Sensitive-file exposure is 3.8% vs 1.8% overall (+2 pp).

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

Wbcom Designs

πŸ‘€ wbcomdesigns πŸ”— Plugin Homepage

Turn your BuddyPress site into an exclusive private community in minutes! Private Community 2.0 helps you create members-only areas on your WordPress site. Whether you’re building a company intranet, paid membership site, or exclusive community, this plugin gives you complete control over who can access your content. 🎯 Perfect For: β€’ Company intranets and team portals β€’ Paid membership communities β€’ Private family or group websites β€’ Educational course platforms β€’ Exclusive member networks ✨ What’s New in Version 2.…

Domain Version Exposures Headers Last Checked
e*u*s*s.com (WP 7.0.2) 1.9.0· 60% conf. F Sep 10, 2026
p*r*n*r*e*r*h*c*n*r*l*a*t*c.eu (WP 7.0.2) 2.1.2· 85% conf. F Sep 9, 2026
r*d*e*u*i*i*i*s.coop (WP 7.1) 2.1.2· 85% conf. F Sep 9, 2026
t*m*g*n.de 2.1.2· 85% conf. F Sep 9, 2026
o*e*s*.com (WP 7.1) 2.1.2· 85% conf. F Sep 9, 2026
b*o*b*p*a*i*n.com F Sep 6, 2026
y*l*7*.com F Sep 4, 2026
c*e*h*i.com (WP 7.1) F Sep 4, 2026
a*u*c*n*e*t.com F Sep 3, 2026
a*s*c*a*e*l*g*e*s.com F Sep 2, 2026
n*t*e*t*o*r.com (WP 7.0.4) F Sep 2, 2026
t*n*i*m*f*a.com (WP 6.8.8) D Sep 1, 2026
k*l*w*r*.ch (WP 6.9.7) D Aug 31, 2026
l*n*s*a*h*m*s*h*o*.com (WP 7.1) F Aug 31, 2026
y*l*7*.org F Aug 30, 2026
c*e*t*o*d*o*s.com F Aug 28, 2026
e*c*.network F Aug 27, 2026
b*a*k*i*e*u*.com F Aug 26, 2026
c*r*o*e*e*w*r*.com (WP 7.1) F Aug 25, 2026
a*a*a*r*s*a*e.com (WP 7.1) F Aug 25, 2026
l*f*u*v*r*i*i*.com F Aug 25, 2026
e*s*e*u*d.org F Aug 24, 2026
w*a*s*a*p*n*n*t*d*y.com (WP 7.1) F Aug 24, 2026
s*c*e*c*r*h*l*o*.com (WP 7.1) F Aug 22, 2026
t*u*d*r*o*t*h*l*e*g*.com (WP 7.1) F Aug 22, 2026
m*e*e*t*u*d*e*.com (WP 7.1) F Aug 21, 2026
s*p*r*y*s*k*i.tokyo F Aug 21, 2026
s*p*r*a*i*t*e*r*n*e*g*.com (WP 7.0.4) F Aug 20, 2026
c*a*r*i*l*d.com (WP 6.0.14) F Aug 20, 2026
l*a*e*a*.com F Aug 18, 2026
m*i*-*o*i*-*i.de F Aug 17, 2026
w*n*e*v*n*o*v*r.com (WP 7.0.4) F Aug 16, 2026
b*l*i*n*a*a.be D Aug 16, 2026
p*m*e*e*p*t*t*.com (WP 7.0.3) F Aug 15, 2026
m*d*a.o*g.hk (WP 4.5.2) F Aug 13, 2026
m*f*c.org D Aug 6, 2026
h*g*.de (WP 6.9.5) F Aug 4, 2026
i*e*f*r*a*i*n.com (WP 6.8.6) F Jul 31, 2026
m*g*e*d*c*t*o*.com B Jul 29, 2026
l*r*k*o*n*c*n*u*t*n*.com F Jul 28, 2026
f*e*n*e*k*e*s*w*s*.de F Jul 27, 2026
b*o*a*t*s*s.de (WP 7.0.2) F Jul 26, 2026
f*t*e*l*b.com (WP 7.0.2) F Jul 25, 2026
f*n*e*a*t*r*a*.com (WP 7.0.2) F Jul 24, 2026
l*f*u*v*r*i*i*.org F Jul 24, 2026
a*v*c*c*-*i*k*.net (WP 7.0.2) F Jul 22, 2026
v*p*r*.o*g.uk (WP 6.3.8) D Jul 21, 2026
a*c*t*e*l.com (WP 7.0.2) F Jul 21, 2026
h*m*v*v*y*s*y.com (WP 6.8.6) F Jul 21, 2026
t*o*r*e*r*a*s.com (WP 7.0.2) F Jul 20, 2026
b*a*k*i*e*u*.org F Jul 20, 2026
p*r*a*s.com (WP 7.0.2) F Jul 19, 2026