WordPress maintenance or security needs? Reach out!
TLDWP

Theme: weddingindustry (Used by 51 domains)

Security snapshot

Across 51 weddingindustry WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 2% Grade B 0% Grade C 8% Grade D 8% Grade F 82%
Fail the header check (F)82%vs 82.5% avg
Leak usernames35%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS96%vs 96.2% avg

What stands out

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

The largest measured difference is username enumeration: 35.3% versus 38.5% overall (-3.2 percentage points).

Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp); Header-grade F is 82.4% vs 82.5% overall (-0.1 pp); HTTPS adoption is 96.1% vs 96.2% overall (-0.1 pp).

These are observational associations among sites where TLDWP detected weddingindustry, 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 36
.hu 1
.ru 1
.pl 1
.nl 1
.info 1
.be 1
.fr 1
.es 1
.it 1
.pt 1
.koeln 1

weddingindustry 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
h*-*l*s.com (WP 5.9.16) F Sep 7, 2026
d*s*l*a*o*i*s.com (WP 6.9.7) F Sep 7, 2026
b*r*s*y*n*s*u*o*s*a*o*.com (WP 6.8.3) F Sep 6, 2026
e*e*t*b*d*n*s*.com (WP 7.1) D Sep 6, 2026
b*d*s*a*o*a*i*a.com (WP 6.0.14) F Sep 4, 2026
d*r*y*c*t*a*e.com (WP 7.1) F Sep 2, 2026
t*s*d*r*-*a*h*o*-*e*i*n.com (WP 6.5.2) F Sep 1, 2026
r*m*n*a*i*a*i*e.com (WP 5.9.16) F Aug 31, 2026
t*e*s*n*e*e*t*.com (WP 6.8.8) F Aug 30, 2026
l*c*t*o*a*a*i*.com (WP 7.1) F Aug 30, 2026
t*r*e*o*c*.es (WP 5.5.3) F Aug 30, 2026
w*r*d*e*d*n*g*o*p.com C Aug 30, 2026
s*l*y*9*0.be (WP 7.1) F Aug 30, 2026
c*e*t*y*u*l*v*s*o*y.com (WP 7.0.4) F Aug 28, 2026
d*s*l*a*o*i*s.c*m.mx (WP 6.9.7) F Aug 27, 2026
c*u*t*y*p*a*d*a*d*n*.com (WP 7.0.4) C Aug 26, 2026
c*u*t*y*p*a*d*a*d*n.com (WP 7.0.4) C Aug 26, 2026
c*u*t*y*f*o*a*.com (WP 7.0.4) C Aug 26, 2026
a*a*f*w*d*i*g*.it (WP 5.9.16) F Aug 26, 2026
c*r*e*e*m*l*n*.com (WP 7.0.4) F Aug 25, 2026
p*l*n*t*e.com (WP 5.2.18) F Aug 24, 2026
e*i*e*b*i*a*.com F Aug 24, 2026
v*t*r*e*q*e*r*.pt (WP 6.9.4) F Aug 23, 2026
s*b*e*-*a*o*.com (WP 5.5.20) F Aug 22, 2026
l*s*t*a.pl (WP 7.0.2) F Aug 22, 2026
1*-*u*n*2*1*.com (WP 4.6.30) F Aug 21, 2026
s*r*v*i*.com (WP 7.0.2) F Aug 21, 2026
v*r*n*t*l*e*e*.com (WP 6.8.8) F Aug 21, 2026
e*s*z*o*w*d*i*g.com (WP 7.1) F Aug 21, 2026
v*l*r*e*o*t*.com (WP 6.2.11) F Aug 17, 2026
i*a*i*e*h*t*e*d*n*s.com (WP 7.0.4) F Aug 16, 2026
f*e*u*j*u*.fr (WP 7.0.4) F Aug 14, 2026
e*k*v*n*o*d*.hu (WP 4.9.26) F Aug 8, 2026
a*i*e*r*s*.ru (WP 5.2.24) F Aug 1, 2026
t*e*a*t*c*n*e*t*o*n*.com (WP 7.0.2) D Jul 31, 2026
k*i*c*a*n*a.c*m.pl (WP 7.0.2) F Jul 31, 2026
a*a*o*i*.c*m.pl (WP 7.0.2) F Jul 31, 2026
b*k*e*i*r*.c*m.pl (WP 7.0.2) F Jul 31, 2026
i*a*e*d*n*s.com (WP 7.0.2) F Jul 31, 2026
e*e*a*t*r*z*l.com (WP 6.8.6) F Jul 31, 2026
s*l*n*o*g*r*s*l*s.com (WP 7.0.2) F Jul 30, 2026
z*e*e*.nl A Jul 29, 2026
m*n*m*r*e*i*n.com (WP 5.8.13) F Jul 28, 2026
p*e*e*e*c*c*u*u*e.com (WP 6.2.9) F Jul 27, 2026
q*i*t*c*r*l*n*e*e*t*s.com (WP 7.0.2) F Jul 26, 2026
g*a*u*c*o*e*v*z*u*z.com (WP 6.5.8) F Jul 25, 2026
k*r*s*h*u*e.koeln (WP 5.2.21) F Jul 23, 2026
w*d*t*r*e*i*s.com D Jul 22, 2026
w*d*i*g*a*d*u*n*e*n*r*s*a.com (WP 6.9.5) F Jul 22, 2026
s*k*e*a*k*.info F Jul 21, 2026
f*n*y*l*n*s*m*h*.com (WP 7.0.2) D Jul 19, 2026