WordPress maintenance or security needs? Reach out!
TLDWP

Theme: affluent (Used by 52 domains)

Security snapshot

Across 52 affluent WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 0% Grade D 0% Grade F 100%
Fail the header check (F)100%vs 82.6% avg
Leak usernames67%vs 38.6% avg
Expose a sensitive file3.8%vs 1.8% avg
Use HTTPS96%vs 96.3% avg

What stands out

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

The largest measured difference is username enumeration: 67.3% versus 38.6% overall (+28.7 percentage points).

Header-grade F is 100% vs 82.6% overall (+17.4 pp); Sensitive-file exposure is 3.8% vs 1.8% overall (+2 pp); HTTPS adoption is 96.2% vs 96.3% overall (-0.1 pp).

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

Where these sites live — top 7 domain endings
.com 33
.org 6
.id 5
.net 4
.pl 2
.co.tt 1
.co.in 1

Affluent

๐Ÿ‘ค WP Chill CPOThemes ๐Ÿ”— Theme Homepage

Affluent is a free corporate WordPress theme perfect for creating professional looking websites with minimal effort. You can turn Affluent into a portfolio WordPress theme easily thanks to CPO Content Types, as well as adding a homepage slider, featured blocks, or even a testimonial rotator. This free theme also provides complete integration with popular WordPress plugins like WooCommerce, Yoast SEO, WPML, and Contact Form 7.

DomainVersionExposuresHeadersLast Checked
e*h*n*e*.com (WP 6.7.1) F Sep 8, 2026
r*d*i*a*g*n*y.com (WP 5.8.2) F Sep 7, 2026
r*s*n*n*p*g*e*t*.c*.in (WP 5.8.2) F Sep 7, 2026
t*m*r*o*a*.id (WP 7.1) F Sep 7, 2026
k*r*d*i*y*a*e.com (WP 7.1) F Sep 7, 2026
k*o*u*-*n.com (WP 7.1) F Sep 7, 2026
v*t*l*a*e*h*o*o*y.com (WP 7.1) F Sep 6, 2026
v*t*l*c*n*e*-*e*l*n*i*c*e*.com (WP 7.1) F Sep 6, 2026
e*e*g*e*n*r*u*-*g.com (WP 7.0.4) F Sep 6, 2026
s*c*t*s*e*.com (WP 7.1) F Sep 5, 2026
m*g*c*a*p*t*i*t*.com (WP 6.8.8) F Sep 5, 2026
b*d*-*a*a*s*n*.com (WP 4.9.7) F Sep 4, 2026
d*e*a*l*p*c*a*i*t.com (WP 7.1) F Sep 4, 2026
e*t*g*m.com F Sep 2, 2026
t*w*.c*.tt (WP 6.6.7) F Sep 2, 2026
x*1*1*.com (WP 7.1) F Aug 31, 2026
a*3*8.com (WP 7.1) F Aug 29, 2026
c*a*a*t*n*r*.com (WP 7.1) F Aug 28, 2026
8*8*2*4.com (WP 7.1) F Aug 27, 2026
g*m*1.com (WP 7.1) F Aug 25, 2026
g*m*s*a*e.id (WP 6.7.7) F Aug 24, 2026
2*o*l*a*s.com (WP 7.1) F Aug 23, 2026
2*u*h*o*.com (WP 7.1) F Aug 23, 2026
s*s*u*a.com (WP 7.1) F Aug 21, 2026
c*u*d*r*m*g*.com (WP 7.0.4) F Aug 21, 2026
b*c*i*k*n*e*t*r*r*c*n*r*v*e*.com (WP 7.0.4) F Aug 20, 2026
d*t*h*p*t*e*n*.com (WP 7.0.4) F Aug 18, 2026
w*s*c*r*p*a*e*.org (WP 7.0.4) F Aug 18, 2026
l*i*f*r*a*d*i*f*.org (WP 7.0.4) F Aug 18, 2026
s*t*-*r.org (WP 7.0.4) F Aug 18, 2026
d*s*c*k*d*.id (WP 7.0.4) F Aug 18, 2026
c*s*i*n.id (WP 7.0.4) F Aug 18, 2026
d*a*a*l*.id (WP 7.0.4) F Aug 18, 2026
a*f*u*n*s*f*.com (WP 7.0.4) F Aug 18, 2026
4*5*3*6.com (WP 7.0.4) F Aug 16, 2026
h*k*n*y*e*i*.net (WP 7.0.4) F Aug 14, 2026
h*t*l*i*o*z*n.pl (WP 6.4.9) F Aug 8, 2026
u*b*n*s*i*o*s*y.pl (WP 6.4.3) F Aug 6, 2026
f*e*f*e*.net (WP 7.0.2) F Aug 3, 2026
w*t*h*p*s.org (WP 7.0.2) F Aug 3, 2026
d*p*o*o*l*e*t.net (WP 7.0.2) F Aug 3, 2026
c*o*a*h*m*m*g*z*n*.org (WP 7.0.2) F Aug 3, 2026
e*e*t*o*i*a*i*e*.com (WP 6.4.1) F Jul 31, 2026
s*f*t*s*h*d*l*r.com (WP 6.9.5) F Jul 29, 2026
n*w*n*u*e*i*c.com (WP 5.8.2) F Jul 28, 2026
f*a*h*f*e*t.net (WP 7.0.2) F Jul 27, 2026
l*n*e*p*1.com (WP 7.0.2) F Jul 27, 2026
i*t*r*i*k*d*m*i*s.com (WP 7.0.2) F Jul 26, 2026
n*o*y*i.com (WP 7.0.2) F Jul 25, 2026
d*y*a*e*o*s.com (WP 7.0.2) F Jul 25, 2026
d*p*o*g*r*y*.com (WP 7.0.2) F Jul 23, 2026
c*u*d*r*m*g*.org (WP 6.9.5) F Jul 22, 2026