WordPress maintenance or security needs? Reach out!
TLDWP

Theme: majesty (Used by 66 domains)

Security snapshot

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

Grade A 2% Grade B 0% Grade C 8% Grade D 3% Grade F 88%
Fail the header check (F)88%vs 82.6% avg
Leak usernames30%vs 38.6% avg
Expose a sensitive file3%vs 1.8% avg
Use HTTPS97%vs 96.3% avg

What stands out

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

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

Header-grade F is 87.9% vs 82.6% overall (+5.3 pp); Sensitive-file exposure is 3% vs 1.8% overall (+1.2 pp); HTTPS adoption is 97% vs 96.3% overall (+0.7 pp).

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

Where these sites live — top 20 domain endings
.com 35
.es 3
.rs 2
.pl 2
.fr 2
.ca 2
.ro 2
.de 2
.eu 1
.at 1
.lu 1
.cz 1
.pt 1
.co.uk 1
.net 1
.io 1

majesty 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.

DomainVersionExposuresHeadersLast Checked
e*q*i*i*e*a*e*i*g*y*o*e*t.com (WP 6.8.8) F Sep 8, 2026
e*q*i*i*e*a*e*i*g.com F Sep 8, 2026
d*z*l*w*n*c*.com (WP 5.4.21) F Sep 8, 2026
r*s*o*a*b*k*l*a.com F Sep 7, 2026
r*s*a*r*n*c*n*r*v*l*e.com (WP 4.6.29) F Sep 6, 2026
n*t*i*m*a*s.com (WP 7.1) F Sep 5, 2026
c*b*i*p*a*z*.com (WP 4.4.1) F Sep 3, 2026
k*v*k*t.com (WP 5.8.15) F Sep 2, 2026
r*t*s*o*i.c*.uk (WP 6.9) F Sep 1, 2026
j*y*o*h*n*s*f*o*.com F Sep 1, 2026
e*n*r*s*o*a*m*r*v*c*.rs A Aug 30, 2026
m*j*s*y.de (WP 7.1) C Aug 30, 2026
m*n*u*t*r.com (WP 7.0.4) F Aug 29, 2026
w*l*e*o*k*t*h*n.com F Aug 29, 2026
m*n*h*s.com (WP 5.1.1) D Aug 28, 2026
t*n*a*a*o*s*f.com (WP 7.1) D Aug 26, 2026
t*n*h*t*.com (WP 7.0.4) F Aug 26, 2026
r*s*o*a*b*k*l*a.rs F Aug 26, 2026
r*s*a*r*n*c*n*r*v*l*e.ca (WP 4.6.29) F Aug 26, 2026
e*m*n*o*e*o*a*g*l*s.com (WP 6.9.7) F Aug 26, 2026
4*r*i*e*c*f*.com (WP 7.1) F Aug 26, 2026
4*a*n*d*m*n*-*a*p*n.com (WP 7.1) F Aug 25, 2026
4*a*n*d*m*n*-*r*n*n*e*.com (WP 7.0.4) F Aug 25, 2026
m*r*h*d*i*k*n*d*n*.c*m.au F Aug 24, 2026
3*r*s*e*r*b*u*y.com (WP 6.9.7) F Aug 24, 2026
l*r*a*a*a*a*o*.es (WP 6.1.12) F Aug 24, 2026
c*r*z*n*n*o.com (WP 6.9.7) F Aug 24, 2026
p*p*n*r*.cz (WP 7.1) F Aug 24, 2026
m*s*e*k*r*e*d*.com F Aug 23, 2026
m*i*s*a*t*o*i*y.com F Aug 22, 2026
l*s*b*a*s*u*s*r*a*.com (WP 6.9.7) F Aug 21, 2026
i*a*y*o*d*r*.com (WP 4.9.31) F Aug 21, 2026
b*i*i*d*.c*m.br (WP 6.0.14) F Aug 21, 2026
t*c*n*k*a*t*n*i*.com F Aug 20, 2026
r*i*v*n*y*u*s*l*.pt (WP 5.6.19) F Aug 20, 2026
d*v*s*a*e*y.net (WP 6.9.7) F Aug 19, 2026
l*b*e*g*e*.com (WP 6.4.10) F Aug 19, 2026
f*o*a*e*i*-*u*o*x.fr C Aug 18, 2026
v*n*a*h*c*l*t*.com (WP 7.0.4) F Aug 18, 2026
e*c*r*o*o*a*a*.es F Aug 17, 2026
p*r*m*u*i*a*d*r*s.com (WP 7.0.4) C Aug 17, 2026
p*i*e*u*.pl F Aug 16, 2026
l*p*r*t*d*l*v*l.ca (WP 7.0.4) F Aug 15, 2026
o*l*-*r*e*e*n*.ro (WP 7.0.2) F Aug 14, 2026
f*e*h*a*e*i*g.at (WP 5.8.2) F Aug 6, 2026
m*j*k*m*a*i*.pl (WP 5.8.2) F Aug 6, 2026
r*s*a*r*n*f*t*m*.sk (WP 6.7.5) F Aug 3, 2026
p*c*n*a*e*c.c*m.br (WP 7.0.2) F Aug 3, 2026
k*a*k*-*r*u*.eu F Aug 3, 2026
a*f*r*o*a*t*o*s*.c*m.sg (WP 7.0.2) F Aug 2, 2026
e*s*c*o*i*g.lu (WP 7.0.2) F Aug 2, 2026
g*a*b*r*a*z*n.c*m.ar (WP 6.2.9) F Aug 1, 2026
a*a*s*s*i.com F Aug 1, 2026
m*s*b*e*t*u*a*t*u*a*.com (WP 6.7.5) F Jul 31, 2026
m*d*i*a*o*n*e.es F Jul 31, 2026
f*r*u*e*c*.com (WP 7.0.2) F Jul 30, 2026
f*o*-*e*o.com (WP 7.0) F Jul 29, 2026
u*-*o*t*a*e.de (WP 6.9.5) C Jul 29, 2026
a*a*u*h*.fr F Jul 27, 2026
l*j*y*h*s*e*.com (WP 6.4.8) F Jul 26, 2026
b*s*b*r.c*m.ar (WP 6.8.6) F Jul 26, 2026
g*a*d*a*e.c*m.ar (WP 5.5.18) F Jul 25, 2026
c*a*a*v*c*e.ro (WP 4.8.28) F Jul 24, 2026
b*r*o*t*o*.io (WP 7.0.2) F Jul 23, 2026
c*e*k*r*t*n.com (WP 7.0.2) F Jul 21, 2026
u*-*o*t*a*e.com (WP 6.9.5) C Jul 21, 2026