WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: bazz-callback-widget (Used by 382 domains)

Security snapshot

Across 382 bazz-callback-widget WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 7% Grade B 0% Grade C 1% Grade D 4% Grade F 87%
Fail the header check (F)87%vs 82.5% avg
Leak usernames50%vs 38.5% avg
Expose a sensitive file2.6%vs 1.8% avg
Use HTTPS97%vs 96.2% avg

What stands out

TLDWP currently associates 382 indexed WordPress sites with bazz-callback-widget, equivalent to 0% of the current WordPress dataset.

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

Header-grade F is 87.4% vs 82.5% overall (+4.9 pp); Sensitive-file exposure is 2.6% vs 1.8% overall (+0.8 pp); HTTPS adoption is 96.6% vs 96.2% overall (+0.4 pp).

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

Infrastructure patterns

Infrastructure detected alongside bazz-callback-widget. 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.

Bazz CallBack widget

The plugin is intended for easy creating a widget on your website. The widget will be performing “call-back function”. That is, you will be recieving client’s phone which the client will have specified in the widget by your e-mail. Features: * RTL ready Supported languages: * 🇺🇸 English * 🇷🇺 Russian * 🇺🇦 Ukrainian * 🇫🇷 French * 🇮🇹 Italian * 🇪🇸 Spanish (Spain) * 🇲🇽 Spanish (Mexico) * 🇩🇪 German * 🇸🇪 Swedish * 🇷🇴 Romanian * 🇵🇱 Polish * 🇳🇱 Dutch * 🇬🇷 Greek * 🇮🇷 Persian * 🇨🇳 Chinese

Domain Exposures Headers Last Checked
f*u*l*a*u*.com (WP 6.8.8) A Sep 8, 2026
u*a*i*.fr D Sep 8, 2026
k*r*i*a*a*l*m*a*a*i.com (WP 7.1) F Sep 8, 2026
w*y*i*.com (WP 6.3.10) F Sep 7, 2026
d*v*l*p*i*u*.com (WP 5.6.2) F Sep 7, 2026
s*l*t*a*s*a*i*n.com (WP 6.4.10) F Sep 7, 2026
v*l*e*.es (WP 6.4.10) F Sep 7, 2026
m*s*l*a.c*m.ua (WP 7.1) F Sep 7, 2026
b*u*a*g*r*e*r*m*m*t*i*u*r*a*n*.com A Sep 7, 2026
d*a*o*d*r*s*o*b*l*e*.ru (WP 7.1) D Sep 7, 2026
d*s*g*-*u*o.com (WP 7.1) F Sep 6, 2026
s*r*e*k*.ru F Sep 6, 2026
v*p*a*k.com (WP 6.1.12) F Sep 6, 2026
s*c*n*e*h*r*u*.com (WP 5.1.24) F Sep 6, 2026
s*c*n*e*h.com (WP 5.1.24) F Sep 6, 2026
m*-*t*.ru (WP 7.1) F Sep 6, 2026
k*r*l*a*e*e*.ru (WP 6.7.2) F Sep 6, 2026
p*r*p*k*y*y*i*n*s*.pl (WP 6.9.7) F Sep 5, 2026
e*e*i*-*v*n*.com (WP 5.2.21) F Sep 5, 2026
p*a*l*n*-*r*u*.ru (WP 5.3.23) F Sep 5, 2026
b*m*a*n*t*.com (WP 7.1) F Sep 5, 2026
r*m*-*h*c*l*t*e*.com A Sep 5, 2026
r*m*n*t*h*i*i.com (WP 4.9.31) F Sep 5, 2026
r*m*n*p*l*v*p*.com (WP 6.0.14) F Sep 5, 2026
r*m*n*-*e*l*.com (WP 5.5.20) F Sep 5, 2026
p*e*o.pl (WP 7.1) F Sep 5, 2026
r*c*c*e*o*r*l*u*.com (WP 7.1) F Sep 5, 2026
e*l*l*b*l*o*s*l*i*g.com F Sep 4, 2026
b*h*n*c*.com (WP 5.3.23) F Sep 4, 2026
z*a*k*.com F Sep 4, 2026
k*l*n*g*o*p.com F Sep 4, 2026
t*a*s*o*t*r*u*a*e*x*r*s*.com A Sep 4, 2026
x*e*s*l*w.com F Sep 3, 2026
b*b*e*l*.com F Sep 3, 2026
c*n*s*a*.com F Sep 3, 2026
p*z*c*k*-*f*.pl F Sep 3, 2026
t*a*e*z*l.com (WP 4.8.25) F Sep 3, 2026
r*a*i*i*a*i*.com (WP 5.3) F Sep 3, 2026
j*m*p*r*o*m*n*e.com (WP 6.2.11) F Sep 3, 2026
e*k*a*u.ru F Sep 3, 2026
e*p*c*-*o*c*i*g*l*o*4.com A Sep 3, 2026
s*p*r*l*g*e*m*s*a*e.com (WP 7.1) F Sep 3, 2026
h*i*s*i*u*e.pl F Sep 3, 2026
h*t*l*e*m*t*g*.com D Sep 2, 2026
m*r*e*l*-*i*g*r*e.com (WP 6.9.7) F Sep 2, 2026
n*t*r*u*-*i*v*.com (WP 6.8.8) F Sep 2, 2026
n*t*r*u*-*e*t*r.com (WP 6.8.8) F Sep 2, 2026
e*c*l*b*c*l*r*.com F Sep 2, 2026
t*r*e*t*e*h*t*l*e*i*.com F Sep 1, 2026
g*c*i.fr D Sep 1, 2026
r*p*d*s*t*-*e*.com (WP 5.0.27) F Sep 1, 2026
t*r*n*d*m.com (WP 7.0) F Sep 1, 2026
c*b*e*t*s*e*r*.com F Sep 1, 2026
a*t*u*.com (WP 7.1) F Sep 1, 2026
t*r*o*o*o*o*u*o*a*i*.com (WP 6.0.14) F Sep 1, 2026
e*k*r*-*s*u*i*k*a*n*d*r.ru (WP 5.4.21) F Sep 1, 2026
s*i*a*i*.com (WP 5.3.23) F Sep 1, 2026
r*n*i.ru F Sep 1, 2026
a*t*e*a*l.ru (WP 7.1) F Sep 1, 2026
t*m*l*d*r*e*i*s.com A Aug 31, 2026
h*d*o*p*o.c*m.ua (WP 6.4.10) F Aug 31, 2026
w*t*c*.eu D Aug 31, 2026
e*t*e*r*s*c*z*l*t.com A Aug 31, 2026
n*c*n*r.c*m.ua (WP 6.9.7) F Aug 30, 2026
b*t*t*n*p*o.com (WP 6.9) F Aug 30, 2026
a*m*d*g*t*c*.com (WP 7.1) F Aug 30, 2026
f*e*h*c*e*n.ru (WP 7.1) F Aug 30, 2026
v*t*m*d.ru (WP 6.6.2) F Aug 30, 2026
a*r*n*e*p*c*s.c*.uk F Aug 30, 2026
c*i*e*-*u*.com (WP 5.7.12) F Aug 29, 2026
a*l*-*e*r*r*e*-*a*n*s.com (WP 5.5.20) F Aug 29, 2026
e*g*a*a.com (WP 7.1) F Aug 29, 2026
a*l*g*t.com (WP 6.0) F Aug 29, 2026
t*b*i*e*p*o.pl (WP 7.0.4) F Aug 29, 2026
t*b*i*z*i*4.pl F Aug 29, 2026
t*b*i*e*-*r*.pl (WP 7.0.4) F Aug 29, 2026
t*r*g*o*p.by F Aug 29, 2026
e*a*p*g*o*p.com F Aug 29, 2026
v*r*e*.in (WP 6.9.7) F Aug 28, 2026
a*p*l*n*a.com (WP 6.0.14) F Aug 28, 2026
n*t*r*l*e*l*h*a*e*o*l*g*.com F Aug 28, 2026
k*c*e*k*.c*m.ua (WP 5.7.17) F Aug 28, 2026
t*s*m*r*.com F Aug 27, 2026
q*a*t*-*l*m*t*.com (WP 5.1.24) F Aug 27, 2026
r*l*y*a*k*r.fr F Aug 27, 2026
n*s*s*l*s.com (WP 5.2.21) F Aug 27, 2026
r*i*f*i*e*-*a*e*.uz (WP 6.9) A Aug 27, 2026
s*-*r*n.ru F Aug 27, 2026
b*t*h*p*t*c*s.com F Aug 27, 2026
e*c*h*m*c*r*.com (WP 6.7.7) F Aug 27, 2026
g*-*a*e*i*.com F Aug 27, 2026
v*v*z*m*s*r*-*-*n*g*.ru F Aug 27, 2026
g*n*s*y*l*.com (WP 6.9.7) F Aug 26, 2026
n*n*t*o*o*.com (WP 7.1) F Aug 26, 2026
j*r*u*e*a*s.com (WP 7.1) F Aug 26, 2026
t*m*s*r*v*l.com (WP 7.0.4) F Aug 26, 2026
k*s*o*i*s*.ru (WP 6.8.8) F Aug 26, 2026
s*o*3*.ru (WP 6.5.10) C Aug 26, 2026
p*r*s*i*l.com (WP 6.8.8) F Aug 26, 2026
k*i*a*y*a*j*-*o*n*w*e*.pl F Aug 26, 2026