WordPress maintenance or security needs? Reach out!
TLDWP

Theme: couture (Used by 47 domains)

Security snapshot

Across 47 couture WordPress sites indexed by TLDWP, compared to the all-WordPress average.

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

Grade A 0% Grade B 0% Grade C 2% Grade D 48% Grade F 50%
Fail the header check (F)50%vs 82.5% avg
Leak usernames89%vs 38.5% avg
Expose a sensitive file2.2%vs 1.8% avg
Use HTTPS98%vs 96.2% avg

What stands out

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

The largest measured difference is username enumeration: 89.1% versus 38.5% overall (+50.6 percentage points).

Header-grade F is 50% vs 82.5% overall (-32.5 pp); HTTPS adoption is 97.8% vs 96.2% overall (+1.6 pp); Sensitive-file exposure is 2.2% vs 1.8% overall (+0.4 pp).

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

Where these sites live — top 4 domain endings
.com 42
.fr 2
.info 1
.jp 1

couture

๐Ÿ‘ค Denis B ๐Ÿ”— Theme Homepage

Couture is simple, modern, responsive WordPress theme built for bloggers, photographer, designer, illustrators, portfolios and curator of all things digital. Build beautiful portfolio sites for your projects or freelance website, simple 1 minute installation. You want more? check out the pro version for a dedicated WordPress portfolio plugin and tech support.

DomainVersionExposuresHeadersLast Checked
k*v*n*r*v*d*.com (WP 7.0.4) 1.0.18· 100% conf. F Sep 10, 2026
f*k*i*d*-*o*p*n.jp (WP 7.1) 1.0.18· 100% conf. F Sep 9, 2026
k*r*a*a*2*0*.com (WP 5.4.2) D Sep 7, 2026
d*n*e*-*n*b*o*k*i*e.com (WP 5.5.1) D Sep 6, 2026
e*e*s*r*.com (WP 5.5.1) D Sep 6, 2026
n*e*t*a*h*s*o*i*.com (WP 6.9.7) F Sep 4, 2026
s*e*c*e*b*o*s.com (WP 5.5.1) D Aug 31, 2026
s*r*a*s.com (WP 6.2.11) F Aug 31, 2026
h*i*-*o*f*e*.com (WP 5.4.2) D Aug 28, 2026
m*s*q*e*l*o*i*h*i*u*.fr (WP 5.1.24) F Aug 28, 2026
9*n*t*r*l.com (WP 7.0.4) F Aug 28, 2026
t*n*k*-*1*2*.com (WP 5.5.1) D Aug 28, 2026
l*v*c*i*e*e*a*s.com (WP 6.5.10) F Aug 28, 2026
t*m*g*w*-*g*e*t*y.com (WP 7.1) F Aug 28, 2026
c*u*u*e*a*d*c*p*s.com (WP 7) D Aug 26, 2026
6*8*e*i*n.com (WP 7.1) F Aug 26, 2026
n*g*y*-*o*h*n*v*.com (WP 5.4.2) D Aug 25, 2026
m*g*e*v*s*a*s.com (WP 5.4.2) D Aug 24, 2026
p*b*r*b*n*.com (WP 5.4.2) D Aug 24, 2026
j*m*s*w*s*.com (WP 7.1) F Aug 23, 2026
l*b*e*r*n*a.com (WP 7.1) C Aug 23, 2026
p*a*a*l*m.com (WP 5.8.15) F Aug 22, 2026
a*c*i*k*r*o*e.com (WP 5.4.2) D Aug 21, 2026
s*p*r*i*d*w*r*j*c*.com (WP 6.6.7) F Aug 21, 2026
s*y*e*o*e*o*t*r*.com (WP 5.9.16) F Aug 19, 2026
b*r*d*b.com (WP 5.4.2) D Aug 17, 2026
p*t*o*c*u*u*e.info F Aug 16, 2026
s*n*a*k*m*t*n.com (WP 5.5.1) D Aug 16, 2026
p*r*i*e*d*s*g*.fr (WP 4.9.31) F Aug 16, 2026
c*a*k*a*l*i*j*r*-*t*o*n*y.com (WP 5.5.1) D Aug 16, 2026
m*c*o*u*.com (WP 7.0.4) F Aug 16, 2026
j*t*u*e*s*m*r*i.com (WP 5.4.2) D Aug 15, 2026
n*c*j*n*d*r.com (WP 7.0.2) F Aug 2, 2026
v*v*i*a*g*r*.com (WP 5.4.2) D Jul 28, 2026
l*n*s*a*i*g*f*r*-*o*l*n*.com F Jul 27, 2026
s*r*a*-*a*e*d*r.com (WP 6.8.6) F Jul 25, 2026
k*o*o*w*l*e*.com (WP 5.4.2) D Jul 24, 2026
d*s*-*u*c*i*n*l*f*o*i*.com (WP 6.3.8) F Jul 24, 2026
o*t*m*r*2*1*.com (WP 5.4.2) D Jul 23, 2026
h*t*l*l*o*.com (WP 5.4.2) D Jul 22, 2026
i*e*o*t*e*s.com (WP 5.4.2) D Jul 22, 2026
l*j*p*a*e*.com (WP 5.5.18) F Jul 22, 2026
e*y*o*e*e*.com (WP 4.7.29) F Jul 20, 2026
r*b*i*l*o*t.com (WP 5.5.1) D Jul 20, 2026
s*o*t*v*l*a*o*.com (WP 5.5.1) D Jul 19, 2026
o*b*i*.com (WP 7.0.2) F Jul 17, 2026