WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: hubbli-newsletter (Used by 52 domains)

Security snapshot

Across 52 hubbli-newsletter WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 0% Grade D 0% Grade F 100%
Fail the header check (F)100%vs 82.5% avg
Leak usernames8%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg

What stands out

TLDWP currently associates 52 indexed WordPress sites with hubbli-newsletter, equivalent to 0% of the current WordPress dataset.

The largest measured difference is username enumeration: 7.7% versus 38.5% overall (-30.8 percentage points).

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

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

hubbli-newsletter 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
f*c*i*d*.com (WP 6.5.3) F Sep 8, 2026
m*g*f*e*-*o*t*s*o*i.com (WP 6.5.3) F Sep 7, 2026
k*n*e*h*u*m*n*e*s*r*.com (WP 6.5.3) F Sep 7, 2026
r*n*i*l*g*.com (WP 6.5.3) F Sep 5, 2026
d*n*z*o*a*c*r*.com (WP 6.5.3) F Sep 5, 2026
a*p*e*c*o*l.com (WP 6.5.3) F Sep 4, 2026
s*a*t*o*k*d*c*t*o*.com (WP 6.5.3) F Sep 4, 2026
n*v*w*o*s*o*t*s*o*i.com (WP 6.5.3) F Sep 3, 2026
n*v*w*o*s.com (WP 6.5.3) F Sep 3, 2026
l*s*a*r*d*e.com (WP 6.5.3) F Sep 1, 2026
a*a*e*i*-*o*t*s*o*i.com (WP 6.5.3) F Aug 31, 2026
b*r*i*g*a*b*o*m*i*l*m*n*e*s*r*.com (WP 6.5.3) F Aug 30, 2026
t*c*i*g*o*p*n*.com (WP 6.5.3) F Aug 26, 2026
e*i*o*m*n*e*s*r*p*e*c*o*l.com (WP 6.5.3) F Aug 23, 2026
s*w*n*e*o*t*s*o*i.com (WP 6.5.3) F Aug 22, 2026
g*t*y*b*r*m*n*e*s*r*c*a*t*r.com (WP 6.5.3) F Aug 21, 2026
s*a*a*a*e*y.ca (WP 6.5.3) F Aug 21, 2026
h*b*l*.com (WP 6.5.3) F Aug 20, 2026
b*-*o*t*s*o*i.com (WP 6.5.3) F Aug 20, 2026
e*g*e*i*g*i*t*r*a*i*n*l.com (WP 6.5.3) F Aug 19, 2026
i*c*u*i*e*o*t*s*o*i.com (WP 6.5.3) F Aug 19, 2026
i*c*u*i*e*o*e*a*e*j.com (WP 6.5.3) F Aug 19, 2026
s*p*u*s*o*t*s*o*i.org (WP 6.5.3) F Aug 18, 2026
s*g*r*i*l*o*t*s*o*i.com (WP 6.5.3) F Aug 17, 2026
m*n*e*s*r*h*b*t*t*c*o*l.org (WP 6.5.3) F Aug 16, 2026
p*p*l*o*-*o*t*s*o*i.com (WP 6.5.3) F Aug 16, 2026
l*s*a*r*d*e.org (WP 6.5.3) F Aug 13, 2026
c*n*d*a*d*u*l*n*a*s*c*a*i*n.org (WP 6.5.3) F Aug 4, 2026
m*g*t*s*r*u*s*j.com (WP 6.5.3) F Jul 31, 2026
t*e*e*r*i*g*t.com (WP 6.5.3) F Jul 30, 2026
g*t*y*b*r*m*n*e*s*r*c*a*t*r.org (WP 6.5.3) F Jul 29, 2026
m*n*y*c*o*l.com (WP 6.5.3) F Jul 29, 2026
m*n*e*s*r*u*b*n*c*a*p*i*n.com (WP 6.5.3) F Jul 29, 2026
m*n*e*s*r*u*b*n*.com (WP 6.5.3) F Jul 29, 2026
m*n*e*s*r*c*a*p*i*n.com (WP 6.5.3) F Jul 29, 2026
m*n*e*s*r*h*b*t*t*f*u.com (WP 6.5.3) F Jul 29, 2026
m*n*e*s*r*-*a.com (WP 6.5.3) F Jul 29, 2026
v*s*h*o*.com (WP 6.5.3) F Jul 29, 2026
p*e*i*r*c*d*m*f*.com (WP 6.5.3) F Jul 27, 2026
c*n*r*m*i*e.com (WP 6.5.3) F Jul 27, 2026
f*r*f*u*d*t*o*c*i*d*a*e*.com (WP 6.5.3) F Jul 25, 2026
c*r*s*i*n*o*t*s*o*i*c*d*m*.com (WP 6.5.3) F Jul 24, 2026
c*r*s*i*n*m*n*e*s*r*.com (WP 6.5.3) F Jul 24, 2026
t*l*d*j*n*o*a*a*e*y.org (WP 6.5.3) F Jul 24, 2026
e*g*e*i*g*c*r*s*i*n.org (WP 6.5.3) F Jul 24, 2026
s*e*p*n*s*o*e*o*t*s*o*i.com (WP 6.5.3) F Jul 23, 2026
s*c*n*.org (WP 6.5.3) F Jul 21, 2026
c*o*l*r*-*n*a*b*r.org (WP 6.5.3) F Jul 20, 2026
n*w*p*i*g*s*h*o*s.org (WP 6.5.3) F Jul 20, 2026
s*r*n*h*l*d*y*c*o*l.com (WP 6.5.3) F Jul 20, 2026
r*s*n*h*i*t*c*d*m*.com (WP 6.5.3) F Jul 18, 2026
s*a*i*h*m*n*e*s*r*.com (WP 6.5.3) F Jul 18, 2026