WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: bulgarisation-for-woocommerce-pro (Used by 69 domains)

Security snapshot

Across 69 bulgarisation-for-woocommerce-pro WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 4% Grade D 17% Grade F 78%
Fail the header check (F)78%vs 82.5% avg
Leak usernames45%vs 38.5% avg
Expose a sensitive file2.9%vs 1.8% avg
Use HTTPS100%vs 96.2% avg

What stands out

TLDWP currently associates 69 indexed WordPress sites with bulgarisation-for-woocommerce-pro, equivalent to 0% of the current WordPress dataset.

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

Header-grade F is 78.3% vs 82.5% overall (-4.2 pp); HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Sensitive-file exposure is 2.9% vs 1.8% overall (+1.1 pp).

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

bulgarisation-for-woocommerce-pro 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
b*s*i*i.net F Sep 9, 2026
g*f*l*b.bg (WP 7.1) F Sep 7, 2026
k*p*i*a*h.com F Sep 7, 2026
r*t*x*b*.com (WP 7.1) F Sep 7, 2026
k*k*s*v*v*d*.bg (WP 7.1) F Sep 7, 2026
e*r*c*m*a*d*e*.com F Sep 6, 2026
p*z*l*-*o*e.bg (WP 7.0) F Sep 6, 2026
v*t*i*a.bg F Sep 6, 2026
l*d*r*t*o.bg F Sep 6, 2026
s*f*a*l*c*r*c*r*w*n*.com F Sep 6, 2026
d*n*m*g.com (WP 7.1) F Sep 5, 2026
u*i*e*u*y.com F Sep 5, 2026
b*h*s*b*a*d.com (WP 7.0.4) F Sep 4, 2026
p*a*a*o*.bg F Sep 4, 2026
a*d*c*-*o*t*q*e.com (WP 6.9.7) F Sep 4, 2026
i*o*i*a.bg (WP 7.1) F Sep 3, 2026
m*r*e*l*k*d*.com (WP 7.1) F Sep 2, 2026
b*a*o*a*.com (WP 7.1) F Aug 31, 2026
b*o*i*e*o*m*t*c*.com (WP 7.0.4) F Aug 29, 2026
e*e.fit (WP 7.0.4) F Aug 29, 2026
c*f*i*a*y.bg F Aug 29, 2026
s*o*i*r*.com (WP 7.0.4) D Aug 28, 2026
s*o*i*r*.bg (WP 7.0.4) D Aug 27, 2026
b*l*i*e*.com C Aug 27, 2026
p*i*t*l*c*.bg (WP 6.7.2) F Aug 25, 2026
t*a*d*v*t*.com F Aug 25, 2026
t*a*d*-*l.com F Aug 25, 2026
a*r*r*d*c*m*a*y.com (WP 7.1) D Aug 22, 2026
g*v*b*l*a*i*.com (WP 7.1) D Aug 21, 2026
v*a*o.bg F Aug 20, 2026
a*r*i*g*x*r*c*.com (WP 7.0.4) F Aug 20, 2026
e*s*c*e*n.bg F Aug 20, 2026
e*g*e*b*s*e*b*l*.com F Aug 19, 2026
g*r*a.bg (WP 7.0.3) F Aug 19, 2026
m*g*z*n*r*b*t*o*b*e*l*.com F Aug 17, 2026
c*t*s*o*t.ro F Aug 16, 2026
p*n*l*g.com (WP 7.0.4) F Aug 16, 2026
a*w*a*.bg (WP 6.7.2) F Aug 15, 2026
w*o*l*n*.bg F Aug 5, 2026
u*i*u*s*o*.store F Aug 3, 2026
g*z*r*.com F Aug 1, 2026
s*l*a*a*k.com (WP 7.0.2) F Jul 31, 2026
s*l*e*e*o.com (WP 7.0.2) F Jul 30, 2026
e*z*.bg D Jul 30, 2026
e*e*i*a.eu F Jul 30, 2026
e*d*r*.bg (WP 7.0.2) F Jul 29, 2026
s*o*i*a*d*o.bg F Jul 29, 2026
l*v*i*.bg (WP 7.0.2) D Jul 29, 2026
c*s*r*.bg (WP 7.0.2) D Jul 29, 2026
j*m*y.bg (WP 7.0.2) D Jul 29, 2026
c*r*o*b*.com F Jul 28, 2026
p*t*t*t*o*.bg F Jul 26, 2026
g*s*.bg D Jul 25, 2026
t*i*h*g*a*m*.bg D Jul 24, 2026
p*s*i*n.bg F Jul 24, 2026
m*s*l*e*a*.com (WP 6.9.5) F Jul 24, 2026
c*t*s*o*t*b*.com F Jul 23, 2026
a*r*r*d*.bg (WP 7.0.2) D Jul 22, 2026
b*s*.bg F Jul 22, 2026
t*p*h*-*n*i*e.bg (WP 6.9) F Jul 22, 2026
b*m*e*w*a*.com F Jul 21, 2026
h*n*m*n*.com (WP 7.0.2) F Jul 21, 2026
v*a*o.bg (WP 7.0.2) C Jul 21, 2026
k*l*b*b*.bg F Jul 21, 2026
f*a*e*k*.bg F Jul 21, 2026
u*i*a*n*t*.com (WP 7.0.2) C Jul 20, 2026
b*l*a*n*.eu (WP 7.0.2) F Jul 20, 2026
d*c*i*a.com (WP 7.0.2) D Jul 19, 2026
h*t*f*r*i.com (WP 7.0.2) F Jul 19, 2026