WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: fb-messenger (Used by 66 domains)

Security snapshot

Across 66 fb-messenger WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 9% Grade B 0% Grade C 2% Grade D 5% Grade F 85%
Fail the header check (F)85%vs 82.5% avg
Leak usernames42%vs 38.5% avg
Expose a sensitive file1.5%vs 1.8% avg
Use HTTPS94%vs 96.2% avg

What stands out

TLDWP currently associates 66 indexed WordPress sites with fb-messenger, equivalent to 0% of the current WordPress dataset.

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

Header-grade F is 84.8% vs 82.5% overall (+2.3 pp); HTTPS adoption is 93.9% vs 96.2% overall (-2.3 pp); Sensitive-file exposure is 1.5% vs 1.8% overall (-0.3 pp).

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

fb-messenger 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
b*v*a*g*y*n*a*.com (WP 5.3.2) A Sep 7, 2026
e*i*.c*m.tw (WP 6.9.7) F Sep 6, 2026
m*x*m*n*l*a*n*n*.com (WP 7.0.4) F Sep 6, 2026
d*n*r*o*u*n*c*o*a*.com D Sep 5, 2026
t*a*c*a*i*.com (WP 7.0.4) F Sep 4, 2026
o*i*a*a*1*9.com F Sep 3, 2026
m*r*i*s*.com (WP 4.9.26) F Sep 2, 2026
m*r*-*a*g*a*.com (WP 7.1) F Sep 1, 2026
e*i*w*v*s*o*t*g*l.com (WP 5.2.21) F Aug 31, 2026
a*a*o*s*.c*m.vn (WP 5.4.4) A Aug 31, 2026
a*i*l*c.com F Aug 30, 2026
e*e.c*m.vn (WP 4.9.12) F Aug 28, 2026
9*1*r*n*s.com (WP 7.0.4) F Aug 28, 2026
e*i*y*a*l*a*o*.com F Aug 27, 2026
s*e*a*s*g*t*e*a*y.com (WP 7.1) F Aug 26, 2026
m*i*h*l*i*g.com (WP 5.2.3) F Aug 26, 2026
s*l*i*a*e*.com (WP 5.7.17) F Aug 24, 2026
l*c*a*o*e*a*.com (WP 6.9.7) F Aug 24, 2026
g*o*g*h*y*a*7*.com (WP 4.9.8) A Aug 23, 2026
b*l*a*i*a*i*n*r*l*e.com F Aug 23, 2026
m*p*a*t*.com (WP 4.9.15) F Aug 23, 2026
s*a*n*u*t*r*c*r*e*c*e*n*n*.us (WP 7.0.2) F Aug 23, 2026
l*v*t*e*o*n*r.com A Aug 23, 2026
e*u*d*r*i*m*r*.com (WP 6.0.14) F Aug 23, 2026
p*o*e*a*r*n*.com (WP 6.9.7) C Aug 22, 2026
m*j*o*l*p*a*e.com (WP 5.2.4) F Aug 22, 2026
n*a*h*a*i*t*u*d*.vn (WP 6.9.7) F Aug 17, 2026
c*b*-*e*.net (WP 5.2.4) F Aug 17, 2026
i*m*h*n*e*.org (WP 4.5.15) F Aug 16, 2026
m*x*e*t*a*.ca F Aug 16, 2026
m*x*m*n*.ca F Aug 16, 2026
e*s*i*e.vn (WP 5.0.16) F Aug 9, 2026
o*e*m*g*z*n*.net (WP 5.2.4) F Aug 3, 2026
t*j*o*d*.c*m.au F Aug 2, 2026
a*h*t*.c*m.ua F Aug 2, 2026
h*i*e*t*n*i*n*v*o*d*e*.nl (WP 7.0.2) D Aug 1, 2026
m*c*o*i*o*x*r*u*i*n.com F Jul 31, 2026
s*l*n*r*n*s.com (WP 7.0.2) F Jul 30, 2026
n*a*h*a*i*t*u*d*.com (WP 6.9.5) F Jul 30, 2026
l*c*m*r*i*t*r*a*i*n*l.com (WP 7.0.2) F Jul 30, 2026
p*i*m*-*e*l*s*a*e.com (WP 7.0.2) F Jul 29, 2026
t*e*r*a*o*t*o*.net (WP 7.0.2) F Jul 29, 2026
v*h*a*p*o*e*.com (WP 7.0.2) F Jul 29, 2026
p*i*e*m*t*h.com (WP 6.9.5) F Jul 29, 2026
c*r*b*n*k*k.com (WP 7.0.2) F Jul 28, 2026
l*s*r*s*s*o*e*c*.com (WP 5.6.17) F Jul 28, 2026
b*t*n*v*i.vn (WP 4.7.11) A Jul 27, 2026
i*t*r*o*m*t*c*s*a.com (WP 7.0.2) F Jul 26, 2026
s*r*e*r*o*t*a*e*.com (WP 6.9.5) F Jul 25, 2026
a*c*n*o*g*t*.com (WP 6.3.8) F Jul 25, 2026
t*a*h*g*a*t*.com (WP 6.8.6) F Jul 25, 2026
c*o*o*a*e*p*a*.com (WP 5.5.18) F Jul 24, 2026
k*r*n*e*b*r*i*e*.net (WP 7.0.2) D Jul 24, 2026
s*r*n*b*r*-*i*s*i*g.de (WP 6.8.1) F Jul 23, 2026
r*m*w*.com (WP 5.3.21) F Jul 23, 2026
r*l*n*f*a*i*r*n*i*e.com F Jul 22, 2026
r*l*n*f*a*i*r.com F Jul 22, 2026
h*s*a*r*y.com (WP 5.5.18) F Jul 22, 2026
s*e*b*a*c*a*o*.com (WP 6.0.12) F Jul 21, 2026
u*t*w*b*y*i*y.com (WP 7.0.2) F Jul 21, 2026
s*c*e*e*.com (WP 7.0.2) F Jul 21, 2026
o*o*a*.com (WP 5.8.2) F Jul 21, 2026
b*g*e*p*o*e*t.com (WP 5.0.7) F Jul 21, 2026
t*e*f*h*i*h*w*n*s.com (WP 7.0.2) F Jul 20, 2026
e*g*.com F Jul 20, 2026
k*t*a*f*t*.com (WP 5.4.4) A Jul 19, 2026