WordPress maintenance or security needs? Reach out!
TLDWP

Theme: AMS (Used by 61 domains)

Security snapshot

Across 61 AMS WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 3% Grade B 2% Grade C 5% Grade D 2% Grade F 89%
Fail the header check (F)89%vs 82.6% avg
Leak usernames20%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS98%vs 96.3% avg

What stands out

TLDWP currently associates 61 indexed WordPress sites with AMS, equivalent to 0% of the current WordPress dataset.

The largest measured difference is username enumeration: 19.7% versus 38.6% overall (-18.9 percentage points).

Header-grade F is 88.5% vs 82.6% overall (+5.9 pp); HTTPS adoption is 98.4% vs 96.3% overall (+2.1 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).

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

Where these sites live — top 14 domain endings
.com 47
.fr 2
.or.jp 1
.pl 1
.co.id 1
.es 1
.pt 1
.org 1
.de 1
.se 1
.ie 1
.jp 1
DomainVersionExposuresHeadersLast Checked
a*s*e*l*n.de (WP 7.1) 1.0· 100% conf. D Sep 9, 2026
a*s*o*d*n*s.com (WP 5.6.19) F Sep 4, 2026
a*s*r*w*h*a*t*e*.com (WP 6.6.2) B Sep 4, 2026
a*s*o*s*l*i*g.com F Sep 4, 2026
a*s*9*3.com F Sep 4, 2026
a*s*y*m*g*t*.com (WP 7.1) F Sep 4, 2026
a*s*s*t*.com (WP 6.4.10) F Sep 4, 2026
a*i*d*s*r*s*m*i*.com F Sep 4, 2026
a*d*t*v*s*r*t*g*e*.com F Sep 4, 2026
a*d*t*v*m*n*f*c*u*i*g*t*a*e*i*s.com F Sep 4, 2026
a*s*e*r*m*e*t*s.es F Aug 30, 2026
a*s*d*o*a*o*.pt F Aug 30, 2026
a*s*i*t.com (WP 7.1) F Aug 29, 2026
a*l*a*c*m*c*.com C Aug 29, 2026
q*a*t*m*e*h*o*o*y*u*m*t.com F Aug 27, 2026
q*a*t*m*e*h*v*n*.com F Aug 27, 2026
q*a*t*m*l*s*i.com F Aug 27, 2026
q*a*t*m*o*p*t*n*s*m*i*.com F Aug 27, 2026
q*a*t*m*o*p*t*n*s*r*t*g*e*.com F Aug 27, 2026
q*a*t*m*o*m*r*c*l*s*t*o*.com F Aug 27, 2026
q*s*m*i*.com F Aug 26, 2026
a*s*t*t*o*i.jp F Aug 25, 2026
3*p*i*t*n*d*s*g*s*o*.com F Aug 24, 2026
3*p*i*t*e*i*n*h*w.com F Aug 24, 2026
3*p*e*i*n*h*w.com F Aug 24, 2026
2*0*a*s.com F Aug 22, 2026
a*r*a*s.com (WP 5.8.15) F Aug 22, 2026
a*s*c*m*c*o.fr (WP 5.8.15) F Aug 20, 2026
c*m*e*c*a*i*i*g*u*n*u*.com F Aug 19, 2026
d*o*t*i*g*l*n*a.se (WP 6.4.3) F Aug 18, 2026
a*r*c*m*b*l*t*s*r*i*e*.com C Aug 18, 2026
a*r*c*n*u*i*s*h*o*.com F Aug 18, 2026
a*v*n*e*m*t*r*a*s*i*n*e.com F Aug 16, 2026
a*v*n*e*m*c*i*i*g*e*v*c*s.com F Aug 16, 2026
a*e*i*a*m*d*t*t*o*s*c*e*y.org F Aug 16, 2026
a*s.o*.jp (WP 7.0) F Aug 6, 2026
a*m*r.pl F Aug 4, 2026
a*i*u*t*s*j*h*e*a.c*.id (WP 6.9) C Jul 31, 2026
a*d*t*y*i*e.com (WP 4.9.26) F Jul 30, 2026
a*s.c*m.pl F Jul 29, 2026
a*l*n*i*m*n*e*s*r*.com (WP 6.8.6) F Jul 29, 2026
i*t*v*n*.com F Jul 28, 2026
i*t*o*f*r*n*e.com F Jul 28, 2026
i*t*o*.com F Jul 28, 2026
a*a*m*-*s.com F Jul 25, 2026
i*s*d*a*d*t*v*m*n*f*c*u*i*g.com F Jul 24, 2026
i*s*d*3*p*i*t*n*.com F Jul 24, 2026
i*s*d*3*p*i*t.com F Jul 24, 2026
t*e*u*s*o*t.com F Jul 23, 2026
a*d*o*a*k*t*n*s*r*i*e*.fr F Jul 22, 2026
a*m*n*a*m*g*s*o*e.com A Jul 22, 2026
p*s*t*v*-*e*h*o*o*i*s.com F Jul 20, 2026
p*s*t*v*-*o*l*.com F Jul 20, 2026
p*s*t*v*-*p*r*t.com F Jul 20, 2026
p*s*t*v*-*u*i*.com F Jul 20, 2026
p*s*t*v*-*a*l*.com F Jul 20, 2026
a*s.ie A Jul 20, 2026
a*a*m*t*s*i.o*g.uk F Jul 20, 2026
h*l*i*g*m*.com F Jul 20, 2026
a*p*e*t*c*s*i*m*n*g*m*n*s*l*t*o*s.com F Jul 20, 2026
a*p*e*t*c*s*i*m*n*g*m*n*s*r*i*e*.com F Jul 20, 2026