WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: wpml-flag-in-menu-extended (Used by 51 domains)

Security snapshot

Across 51 wpml-flag-in-menu-extended WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 4% Grade C 0% Grade D 2% Grade F 94%
Fail the header check (F)94%vs 82.5% avg
Leak usernames31%vs 38.5% avg
Expose a sensitive file3.9%vs 1.8% avg
Use HTTPS94%vs 96.2% avg

What stands out

TLDWP currently associates 51 indexed WordPress sites with wpml-flag-in-menu-extended, equivalent to 0% of the current WordPress dataset.

The largest measured difference is header-grade F: 94.1% versus 82.5% overall (+11.6 percentage points).

Username enumeration is 31.4% vs 38.5% overall (-7.1 pp); Sensitive-file exposure is 3.9% vs 1.8% overall (+2.1 pp); HTTPS adoption is 94.1% vs 96.2% overall (-2.1 pp).

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

WPML flag in menu Extended

๐Ÿ‘ค johanvandemerwe ๐Ÿ”— Plugin Homepage

Shows translated flags (for every language except current viewing lang) in any selected menu in the plugin settings LTR support In addition to the plugin from Ramon Fincken, this plugin let you select on which menu you want to add the language flags. You can even make an empty menu and make it dedicated for your language flags and put it as a custom menu in the sidebar. To make the flags appear on a translated menu, you go in the settings of the plugin and add the translated menu to the selection you made.โ€ฆ

Domain Exposures Headers Last Checked
f*l*u*e*t*d*s.org F Sep 6, 2026
a*d*e*s*a*a*o*s*s.com (WP 6.8.8) F Sep 6, 2026
b*o*t*y*o*.com (WP 5.0.22) F Sep 6, 2026
b*o*t*a*o*.com (WP 5.0.22) F Sep 6, 2026
z*o*m*d*o*p*.com (WP 7.0.4) F Sep 4, 2026
d*b*a*s*c*a*e*.com (WP 7.1) F Sep 4, 2026
d*m*t*i*n*i*i*c*.com (WP 7.1) F Sep 3, 2026
a*e*m*k*a*.com (WP 4.2.39) F Sep 3, 2026
r*m*i*e*r*.com F Sep 3, 2026
b*i*s.org F Sep 2, 2026
x*a*g*o*p.com F Sep 1, 2026
x*a*-*r*u*.com F Sep 1, 2026
l*d*p*o*e*s*o*a*s.de (WP 6.8.8) F Sep 1, 2026
t*p*c*o*l*n*p*i*.com F Aug 31, 2026
t*e*e*r*p*l*t*u*h*e*.vn (WP 5.8.15) F Aug 30, 2026
t*c*p*g*l*a.com (WP 4.9.26) F Aug 29, 2026
k*a*s*n.com (WP 5.1) F Aug 28, 2026
h*i*i*e*b*r*-*u*e*h*i*.de (WP 6.9.7) F Aug 28, 2026
a*a*e*e*s.pt (WP 6.5.8) F Aug 26, 2026
s*a*i*a.com F Aug 24, 2026
k*k*e*.c*m.pl (WP 6.8.8) F Aug 24, 2026
l*c*g*t*i*r.com (WP 6.7.7) F Aug 24, 2026
s*o*t*v*l*a*e.gr (WP 6.0.14) F Aug 24, 2026
a*f*g*o*p.cl (WP 6.8.5) F Aug 22, 2026
l*t*-*o*d.com F Aug 22, 2026
e*i*k*y*k*.com (WP 4.8.25) F Aug 21, 2026
m*z*j*o*o*.com (WP 4.7.29) F Aug 20, 2026
p*o*i*a*-*n*.com F Aug 19, 2026
e*l*g*o*.com (WP 7.0.4) F Aug 19, 2026
g*c*i.it F Aug 18, 2026
j*m*m*c*a*i*a.pl F Aug 18, 2026
e*o*e*.fi (WP 5.0.2) F Aug 17, 2026
f*n*a*i*n*o*e*i*o*.com F Aug 16, 2026
m*c*i*e*a*r*e*-*e*r*a*r*.com F Aug 15, 2026
m*r*n*a*e.pt F Aug 15, 2026
p*s*e*o*t*o*r*e*o*d*.com (WP 5.7.17) F Aug 15, 2026
d*-*a*.de (WP 5.9.13) F Aug 6, 2026
z*o*m*d.com (WP 7.0.2) F Aug 4, 2026
m*c*o*n*r*p*e*d*e*h*.com (WP 7.0.2) F Jul 31, 2026
c*s*d*t*l*s.com D Jul 30, 2026
p*h*a*a*n*n*a*t*i*i*a*i*t*o.fi (WP 6.6.5) F Jul 27, 2026
d*m*i*e*l*c*e*e*u*.com F Jul 27, 2026
3*t*p*.de F Jul 25, 2026
p*o*o*i*e*h.com (WP 7.0.2) F Jul 25, 2026
i*d*s*u*i*e*s*d*i*o*s.com F Jul 24, 2026
f*l*p*l*.com (WP 5.7.15) F Jul 23, 2026
f*l*p*t*.com (WP 5.7.15) F Jul 23, 2026
l*x*a*.com (WP 6.1.10) F Jul 23, 2026
m*t*z*m*i*t*k*n.com B Jul 21, 2026
c*e*p*a*i*a*e*c*a.com (WP 6.7.5) F Jul 21, 2026
a*t*f*r*s*a*e.com B Jul 18, 2026