WordPress maintenance or security needs? Reach out!
TLDWP

Theme: vip-restaurant (Used by 55 domains)

Security snapshot

Across 55 vip-restaurant WordPress sites indexed by TLDWP, compared to the all-WordPress average.

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

What stands out

TLDWP currently associates 55 indexed WordPress sites with vip-restaurant, equivalent to 0% of the current WordPress dataset.

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

Username enumeration is 43.6% vs 38.5% overall (+5.1 pp); HTTPS adoption is 98.2% vs 96.2% overall (+2 pp); Sensitive-file exposure is 1.8% vs 1.8% overall (0 pp).

These are observational associations among sites where TLDWP detected vip-restaurant, 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 33
.fr 6
.de 3
.co.uk 2
.it 2
.at 2
.hk 2
.gr 2
.pl 1
.ro 1

vip-restaurant 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
p*a*a*a*e.gr (WP 6.9.7) F Sep 9, 2026
d*a*a*o*s*e*b*r.com (WP 7.0.4) F Sep 9, 2026
b*a*o*e*h*f.com (WP 4.8.30) F Sep 8, 2026
a*b*t*o*-*e*t*u*a*t.fr (WP 5.8.3) F Sep 8, 2026
l*r*e*e*l*c*r*e.it F Sep 8, 2026
s*m*a*s*y*s*r*t.com (WP 6.8.8) F Sep 8, 2026
o*a*-*e*t*u*a*t.com (WP 7.1) F Sep 8, 2026
b*u*a*g*r*e*l*-*r*m*n*i*r*.com (WP 6.2.11) F Sep 7, 2026
b*t*m*r*.com (WP 7.1) F Sep 7, 2026
r*s*a*r*n*e*o*r*m*d*r*s.com F Sep 6, 2026
s*a*k*i*m*.com (WP 7.0.2) D Sep 5, 2026
l*b*n*u*e.fr (WP 6.0.14) D Sep 4, 2026
j*r*c*a.com (WP 4.9.26) F Sep 3, 2026
o*f*h*h*o*s*s*i.com F Sep 2, 2026
a*t*n*l*k*a*a*c*s*.com (WP 7.1) F Sep 1, 2026
a*o*a*k*r*s*u*e.de (WP 5.2.26) F Aug 31, 2026
l*n*o*t*o*i*t*r*n*e.it (WP 6.5.10) F Aug 29, 2026
r*s*a*r*n*-*o*m*t*c*s.fr (WP 4.8.30) F Aug 29, 2026
n*m*y*a*l.com (WP 5.5.15) F Aug 29, 2026
n*s*u*d*r*a.restaurant (WP 7.1) F Aug 26, 2026
r*s*a*r*n*-*o*a*o.de (WP 4.9.26) F Aug 26, 2026
g*u*t*a*i.com (WP 6.5.5) F Aug 25, 2026
b*l*o*.hk (WP 4.9.26) F Aug 24, 2026
p*o*i*i*i*n.hk (WP 7.0.2) F Aug 23, 2026
a*r*s*e*o*a*a.com (WP 7.0.4) F Aug 22, 2026
b*a*i*.com (WP 5.4.21) F Aug 20, 2026
l*d*a*a*.com (WP 6.9.7) F Aug 19, 2026
l*c*f*c*s*e*t*.com (WP 7.0.2) F Aug 19, 2026
m*s*b*e*r*o*.fr (WP 4.9.26) F Aug 16, 2026
p*s*n*n*e*i.com (WP 7.0.4) F Aug 14, 2026
b*l*b*a*s*r*e.c*.uk (WP 5.9.13) F Aug 7, 2026
n*w*s*p*c*a.pl (WP 7.0.2) F Aug 5, 2026
o*o*m*n.com (WP 5.2.24) F Aug 2, 2026
b*r*s*o*r*i*e*r.fr (WP 6.7.5) F Aug 2, 2026
b*m*a*r*n*e*.fr (WP 5.8.13) F Aug 2, 2026
b*o*a*o*k.at (WP 6.3.1) F Aug 2, 2026
b*e*k*r*i*t*s*h*r.de (WP 6.7.5) F Aug 2, 2026
f*e*c*s*u*u*.com F Aug 1, 2026
i*o*h*i*e*z*.com (WP 5.3.21) C Jul 31, 2026
m*c*i*c*f*.at (WP 6.9.5) F Jul 30, 2026
g*o*g*s*i*h*r*e*.ro (WP 6.7.1) F Jul 30, 2026
d*a*t*i*e*.com D Jul 29, 2026
l*s*u*v*s*e*d*q*e.com (WP 7.0.2) F Jul 28, 2026
l*r*t*n*e*t*o*o*e.com F Jul 28, 2026
l*p*m*r*d*.com (WP 6.1.10) F Jul 28, 2026
l*g*a*r*.com (WP 6.0.12) F Jul 26, 2026
l*b*t*g*g*r*e*.com (WP 7.0.2) F Jul 25, 2026
c*k*d*p*r*i*.com (WP 6.2.6) F Jul 25, 2026
c*f*l*c*t*d*a*.com (WP 6.2.2) F Jul 24, 2026
c*f*c*s*e*t*.com (WP 6.6.5) F Jul 24, 2026
r*i*o*s*a*e.gr (WP 7.0.2) F Jul 24, 2026
t*x*r*s*o*o*f*e.com (WP 7.0.2) F Jul 22, 2026
g*f*c*f*.c*.uk (WP 7.0.2) F Jul 22, 2026
m*n*u*e*.com (WP 7.0.2) F Jul 20, 2026
r*s*o*a*t*n*s*u*d*r*a.com (WP 7.0.2) F Jul 19, 2026