WordPress maintenance or security needs? Reach out!
TLDWP

Theme: amax (Used by 57 domains)

Security snapshot

Across 57 amax WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Security metrics currently cover 56 matching records in the cached metrics snapshot.

Grade A 0% Grade B 0% Grade C 5% Grade D 5% Grade F 89%
Fail the header check (F)89%vs 82.5% avg
Leak usernames41%vs 38.5% avg
Expose a sensitive file1.8%vs 1.8% avg
Use HTTPS96%vs 96.2% avg

What stands out

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

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

Username enumeration is 41.1% vs 38.5% overall (+2.6 pp); HTTPS adoption is 96.4% vs 96.2% overall (+0.2 pp); Sensitive-file exposure is 1.8% vs 1.8% overall (0 pp).

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

Where these sites live — top 11 domain endings
.com 39
.pl 4
.nl 3
.de 2
.ru 2
.fr 1
.co.at 1
.ir 1
.co.jp 1
.cn 1
.net 1

amax Premium / Custom

This theme is not available on WordPress.org. It may be a premium theme, a custom theme, or a theme from a third-party marketplace.

DomainExposuresHeadersLast Checked
b*t*i*k*e*l*y.com F Sep 7, 2026
m*l*t*m*r*n*g*o*p.net (WP 6.6.7) F Sep 6, 2026
d*s*r*l*b.com (WP 5.1.24) F Sep 6, 2026
r*i*s*p*o*i*e*a*s*i*d*n*.de F Sep 5, 2026
a*a*i*g*l*x*a*k*h*o*g*s.com (WP 7.1) F Sep 2, 2026
b*o*m*o*s*p*r*i*g.com (WP 4.9.26) F Sep 2, 2026
e*i*c*c*e.com (WP 4.7) F Sep 1, 2026
x*-*1*-*l*l*a*6*j*s*i*6*.com (WP 5.5.3) F Sep 1, 2026
c*n*e*s*r*b*.com (WP 5.4.21) F Sep 1, 2026
m*r*n*b*a*m*l*a.com F Aug 31, 2026
s*-*s*o*i*s.com (WP 6.9.7) F Aug 31, 2026
n*m*t*i*t*r*a*i*n*l.com F Aug 26, 2026
g*l*h*d.c*.jp (WP 5.5.20) F Aug 26, 2026
p*j*a*r*.ru (WP 4.7.29) F Aug 24, 2026
d*s*d*e*d*n*.ir (WP 4.9.20) D Aug 23, 2026
c*y*r*t*l*.com (WP 5.6.19) F Aug 21, 2026
g*y*e*o*t*h*t*l.com (WP 5.8.12) F Aug 21, 2026
a*p*e*l*h*b*a*t*.com (WP 7.0.2) F Aug 20, 2026
c*c*o*r*t.fr F Aug 19, 2026
s*l*n*a*k*w*.pl F Aug 19, 2026
s*i*t*e*n*t*l*g*i.pl F Aug 19, 2026
i*d*a*h*n*u*s*r*l*g*r.com (WP 6.4.10) F Aug 19, 2026
p*j*i*t*r*a*i*n*l.com (WP 4.4.33) F Aug 18, 2026
p*j*a*r*.com (WP 4.7.29) F Aug 18, 2026
p*j*-*g*o.com (WP 4.7.29) F Aug 18, 2026
p*j*.ru (WP 4.4.33) F Aug 18, 2026
n*d*i*e*.nl (WP 5.3.23) C Aug 17, 2026
s*s*l*b*u*d*a*e*i*r.nl (WP 7.0.4) D Aug 16, 2026
c*d*r*h*t*c*s.com F Aug 16, 2026
d*o*o*o*a.com (WP 6.8.8) F Aug 15, 2026
c*i.c*.at F Aug 14, 2026
z*s*o*y*e*e*n*.pl F Aug 13, 2026
a*a*l*g.pl (WP 6.7.6) F Aug 7, 2026
s*l*m*a*a*i.com (WP 7.0) F Jul 30, 2026
h*d*a*a*c*u*e*r*s*a*r*n*.com (WP 5.5.18) F Jul 30, 2026
h*l*-*n*u*t*i*s.com F Jul 29, 2026
n*w*e*e*a*i*n*r*v*r.com (WP 5.3.21) C Jul 28, 2026
m*n*r*l*o*i*g.com (WP 6.2.9) F Jul 28, 2026
p*n*c*s*r*z*o*i.com (WP 7.0.2) F Jul 26, 2026
v*n*m*5.com F Jul 26, 2026
g*a*i*a*v*r*s*y.com (WP 7.0.2) F Jul 25, 2026
p*o*n*x*i*e*t*r*g*.com F Jul 24, 2026
r*t*b*.com (WP 4.6.29) F Jul 24, 2026
s*e*b*s*l.com F Jul 23, 2026
s*e*k*t*a*t*e.com (WP 6.7.5) F Jul 23, 2026
j*l*u*-*h*e.de (WP 4.1.41) F Jul 23, 2026
d*g*i*i*d*r.com F Jul 22, 2026
y*p*e*t*c*n*l*g*.com (WP 6.6.5) D Jul 22, 2026
u*v*h*d*c*r*.com (WP 7.0.2) F Jul 21, 2026
t*c*v*z.cn F Jul 21, 2026
s*l*s*v*.nl (WP 6.4.8) F Jul 20, 2026
g*l*a*o*p*e*.com (WP 4.3.32) F Jul 20, 2026
g*t*s*a*e*r*n.com (WP 5.7.15) F Jul 19, 2026
h*h*r*m*.com (WP 6.6.5) F Jul 19, 2026
a*t*n*v*c*-*r*u*.com (WP 7.0.2) C Jul 18, 2026
m*d*t*r*a*e*n*a*h*r*f*t.com F Jul 18, 2026
d*n*a*a*r*s*t*.com (WP 6.2.9) F Jul 15, 2026