WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: woocommerce-speedy (Used by 70 domains)

Security snapshot

Across 70 woocommerce-speedy WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Security metrics currently cover 69 matching records in the cached metrics snapshot.

Grade A 1% Grade B 0% Grade C 1% Grade D 9% Grade F 88%
Fail the header check (F)88%vs 82.6% avg
Leak usernames41%vs 38.6% avg
Expose a sensitive file11.6%vs 1.8% avg
Use HTTPS97%vs 96.3% avg

What stands out

TLDWP currently associates 70 indexed WordPress sites with woocommerce-speedy, equivalent to 0% of the current WordPress dataset.

The largest measured difference is sensitive-file exposure: 11.6% versus 1.8% overall (+9.8 percentage points).

Header-grade F is 88.4% vs 82.6% overall (+5.8 pp); Username enumeration is 40.6% vs 38.6% overall (+2 pp); HTTPS adoption is 97.1% vs 96.3% overall (+0.8 pp).

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

woocommerce-speedy 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
a*a*t*.bg (WP 7.1) 1.6.1· 85% conf. F Sep 10, 2026
h*p*y*r*e*.bg F Sep 10, 2026
k*t*-*g.com (WP 7.0.4) 1.6.1· 85% conf. F Sep 9, 2026
d*g*8*.com (WP 7.1) F Sep 9, 2026
s*a*t*h*r*s.com 1.6.1· 85% conf. D Sep 9, 2026
k*r*h*r*h*p.bg (WP 7.1) 1.6.1· 85% conf. F Sep 8, 2026
m*c*f*e*.bg (WP 7.1) F Sep 8, 2026
a*n*2*0*.com (WP 6.8.2) F Sep 8, 2026
e*p*e*s*u*l*s*i*g*g.com F Sep 7, 2026
d*t*i*i*g*g.com (WP 7.0.4) F Sep 7, 2026
e*c*s*w*a*.com (WP 6.7.2) F Sep 7, 2026
a*g*l*v*i*i*a*.com (WP 7.0.4) F Sep 7, 2026
b*b*o*i*.bg (WP 7.1) D Sep 6, 2026
y*a*a*a*c*e*a.com (WP 6.7.7) F Sep 6, 2026
m*m*i*s.bg (WP 7.1) F Sep 6, 2026
d*m*a*y*k*v.com (WP 7.1) F Sep 5, 2026
h*a*t*y*i*e.bg F Sep 5, 2026
p*a*e*.bg F Sep 5, 2026
k*b*l*o*e*s.com F Sep 4, 2026
s*t*.bg F Sep 4, 2026
b*d*g*a*s*l*b.com (WP 6.7.7) F Sep 4, 2026
z*o*a*d*v*r*a.com D Sep 4, 2026
z*o*o*a*k*.com F Sep 4, 2026
t*c*i*i.bg F Sep 3, 2026
s*a*t*i*t*c*.com F Sep 3, 2026
s*a*c*o*l*d.com F Sep 2, 2026
z*n*i*s*i*e.com (WP 7.1) F Sep 1, 2026
e*e*t*d*t*r*.com (WP 7.1) C Sep 1, 2026
w*o*e*s*o*n.eu (WP 7.1) F Aug 30, 2026
m*r*g.com F Aug 30, 2026
m*r*b*.com F Aug 30, 2026
m*r*g*.com F Aug 30, 2026
m*r*r*.com F Aug 30, 2026
b*o*t*r*b*.com F Aug 29, 2026
i*g*r*m*z*i*i*e.com F Aug 29, 2026
v*i*h*i*a*l*.bg F Aug 29, 2026
r*b*c*m.bg (WP 6.9.7) F Aug 28, 2026
b*t*e*a*o*k*.com D Aug 28, 2026
m*d*k*.bg F Aug 26, 2026
a*m*e*c*r*.com F Aug 22, 2026
p*a*e*1*4*.com F Aug 22, 2026
v*r*e*i*i*a.com (WP 7.1) D Aug 21, 2026
v*m*h*r*.com F Aug 20, 2026
c*b*e*o*m*r*e.bg F Aug 18, 2026
p*d*g*g.com (WP 7.0.4) F Aug 18, 2026
m*g*e*b*.com F Aug 17, 2026
s*p*i*a*t.com F Aug 16, 2026
b*m*u*i*a*i*y.com (WP 7.0.4) F Aug 16, 2026
p*t*e*n*.bg F Aug 15, 2026
g*f*2*o*.bg F Aug 5, 2026
k*k*o*a*m.bg (WP 6.9) F Aug 4, 2026
w*r*d*r*d*.bg (WP 7.0.2) F Aug 3, 2026
k*n*o*.eu F Jul 30, 2026
d*e*m*t*l*-*g.com A Jul 30, 2026
p*i*a*e*h*p*b*.com (WP 7.0.2) F Jul 30, 2026
t*a*e*m*b*l*a*i*.com (WP 6.7.5) F Jul 29, 2026
t*e*r*e*b*a*.eu (WP 7.0.2) F Jul 29, 2026
c*r*b*a*b*.com (WP 7.0.2) F Jul 29, 2026
i*i*v*r*2*.com (WP 7.0.2) F Jul 29, 2026
g*r*n.bg F Jul 28, 2026
v*s*e*o.com F Jul 27, 2026
n*v*t*a*e.bg F Jul 26, 2026
p*c*t*l*r.com (WP 6.7.5) F Jul 25, 2026
g*t*p*i*t*h*p.com (WP 6.9.1) D Jul 25, 2026
t*c*n*m*n*.bg F Jul 24, 2026
w*d*-*a*e.com F Jul 22, 2026
m*-*u*g*r*a.com F Jul 22, 2026
s*g*a*r*v*d*a.com (WP 6.9.5) F Jul 22, 2026
b*r*i*p*d*r*c*.com F Jul 22, 2026
u*i*m*p.com (WP 7.0) F Jul 20, 2026