WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: wp-armour-extended_1 (Used by 12 domains)

Security snapshot

Across 12 wp-armour-extended_1 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 usernames67%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS92%vs 96.2% avg

What stands out

TLDWP currently associates 12 indexed WordPress sites with wp-armour-extended_1, equivalent to 0% of the current WordPress dataset.

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

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

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

Domain Exposures Headers Last Checked
a*d*z*l*e.com (WP 7.1) F Sep 6, 2026
t*e*t*r*r*u*d*-*u*s*u*g.de (WP 7.1) F Sep 5, 2026
v*r*o*g*n*s*h*t*-*a*h*o*g*.de (WP 7.1) F Aug 31, 2026
g*u*o*m*r*.com (WP 6.8.8) F Aug 26, 2026
v*r*o*g*n*s*h*t*-*a*h*o*g*.com (WP 7.1) F Aug 21, 2026
p*n*a*s*s*.com (WP 6.8.8) F Aug 19, 2026
w*-*u*s*e*h*l*e.de (WP 7.0.2) F Aug 4, 2026
o*i*e*-*o*t.com (WP 7.0.2) F Aug 2, 2026
d*-*o*d*v*n.de (WP 7.0.2) F Aug 1, 2026
g*s*h*r*.eu (WP 7.0.2) F Jul 30, 2026
g*s*h*r*.com (WP 7.0.2) F Jul 25, 2026
g*s*w*e*e.com (WP 7.0.2) F Jul 25, 2026