WordPress maintenance or security needs? Reach out!
TLDWP

Theme: hotel-luxury (Used by 38 domains)

Security snapshot

Across 38 hotel-luxury WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 5% Grade D 3% Grade F 92%
Fail the header check (F)92%vs 82.5% avg
Leak usernames42%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS100%vs 96.2% avg

What stands out

TLDWP currently associates 38 indexed WordPress sites with hotel-luxury, equivalent to 0% of the current WordPress dataset.

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

HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Username enumeration is 42.1% vs 38.5% overall (+3.6 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).

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

Where these sites live — top 10 domain endings
.com 29
.ru 1
.be 1
.fr 1
.se 1
.nl 1
.de 1
.gr 1
.jp 1

Hotel Luxury

๐Ÿ‘ค FilaThemes ๐Ÿ”— Theme Homepage

Hotel Luxury is the most charming, luxurious and powerful WordPress theme for your spa, resort, hotel business, vacation room/apartment rental services. Its original goal is to help you easier manage your rooms listings, customer bookings and reservations online. With its beautiful design, and high coding quality, this theme can showcase your unique accommodations to the world and attract more visitors to your website. See our demo: and documentation:

DomainExposuresHeadersLast Checked
o*d*o*n*a*m*o*s*.com (WP 5.7.17) F Sep 7, 2026
w*e*l*o*s*a*a*t*e*t*.c*m.au (WP 7.1) F Sep 7, 2026
s*f*w*r*-*r*h*t*c*u*e*c*m*.com (WP 7.1) F Sep 6, 2026
m*y*r*h*p*o.com (WP 7.1) F Sep 6, 2026
s*i*h*k*r*.com (WP 6.9.7) F Sep 4, 2026
s*l*d*i*g.com (WP 7.0.4) F Sep 1, 2026
c*o*n*a*e.com (WP 6.6.7) F Aug 30, 2026
l*c*t*o*l*s*a*d*n*d*c*b*.com (WP 7.1) F Aug 30, 2026
b*s*b*a*h*o*d*4*.com (WP 7.1) F Aug 25, 2026
b*r*r*n*l*c*t*o*s.com (WP 7.1) F Aug 25, 2026
b*r*i*-*e*t*a*-*p*r*m*n*.com (WP 5.9.16) F Aug 25, 2026
g*t*i*b*r*s*e*t*i*w*.com (WP 6.9.7) F Aug 21, 2026
a*f*u*n*l*v*n*a*.com (WP 6.4.10) F Aug 18, 2026
c*l*b*a*e*w*n*.com (WP 6.9.4) F Aug 17, 2026
c*l*b*a*e*o*l*c*i*e.com (WP 7.0.4) F Aug 17, 2026
v*k*n*i*h*i*j*s*e*g*n*a*.be (WP 6.2.10) F Aug 8, 2026
b*z*a*m*r*l.ru (WP 5.7.15) F Aug 6, 2026
c*r*m*a*e*a*e*e*t.fr (WP 6.9.5) C Aug 2, 2026
p*l*c*h*t*l*a*g*o*l*e.com (WP 7.0.2) F Jul 31, 2026
v*n*r*r*e*o*t*a*m*r.se (WP 4.8.3) D Jul 31, 2026
c*s*e*l*g*n*.com (WP 5.1.19) F Jul 30, 2026
h*r*n*h*r*s*a*i*s.com (WP 7.0.2) F Jul 29, 2026
v*i*s*n*e*b*u*e*a*d.com (WP 7.0.2) F Jul 29, 2026
c*-*y*t*m.jp (WP 6.9.5) F Jul 28, 2026
t*e*o*p*s*r*n*s.com (WP 7.0.2) F Jul 27, 2026
t*x*d*l*u*.com (WP 6.9.5) F Jul 27, 2026
r*s*o*a*e*.com (WP 6.9.5) F Jul 25, 2026
v*i*s*n*e*b*u*e*a*d.nl (WP 7.0.2) F Jul 25, 2026
f*n*a*a*d*l*c*a.com (WP 5.9.1) F Jul 24, 2026
r*s*a*r*g.com (WP 5.7.15) F Jul 23, 2026
m*n*-*o*m.com (WP 7.0.2) F Jul 23, 2026
h*t*l*n*t*a*e*i*g.com (WP 5.8.13) F Jul 22, 2026
h*t*l*k*i*p.com C Jul 22, 2026
f*r*e*w*h*u*g*h*e*e*.com (WP 6.4.8) F Jul 22, 2026
s*f*w*r*-*r*h*t*c*u*e*c*m*.de (WP 6.9.5) F Jul 22, 2026
e*a*o*i*o*i*l*n*.com (WP 7.0.2) F Jul 21, 2026
a*a*t*a*i*e*i*a.com (WP 7.0.2) F Jul 19, 2026
a*a*a*i*o*e*.gr (WP 5.9.13) F Jul 18, 2026