WordPress maintenance or security needs? Reach out!
TLDWP

Theme: i (Used by 82 domains)

Security snapshot

Across 82 i WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 9% Grade B 2% Grade C 1% Grade D 2% Grade F 85%
Fail the header check (F)85%vs 82.5% avg
Leak usernames30%vs 38.5% avg
Expose a sensitive file1.2%vs 1.8% avg
Use HTTPS94%vs 96.2% avg

What stands out

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

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

Header-grade F is 85.4% vs 82.5% overall (+2.9 pp); HTTPS adoption is 93.9% vs 96.2% overall (-2.3 pp); Sensitive-file exposure is 1.2% vs 1.8% overall (-0.6 pp).

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

Where these sites live — top 12 domain endings
.com 68
.ir 3
.cn 2
.co.uk 1
.de 1
.pl 1
.kg 1
.ru 1
.jp 1
.org 1

i 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.

DomainExposuresHeadersLast Checked
a*r*s*a*-*s*.ru F Sep 9, 2026
o*e*e*e*a*o*.com (WP 7.1) F Sep 7, 2026
y*h*l*e*.com F Sep 6, 2026
y*n*t*i*1*.com (WP 6.7.1) F Sep 6, 2026
i*a*b*e*t*h*r.de F Sep 5, 2026
r*d*u*p*m*s.com (WP 6.9.4) F Sep 5, 2026
y*g*.com A Sep 5, 2026
b*d*-*a*.com F Sep 4, 2026
b*-*h*n*.com (WP 6.9.4) F Sep 4, 2026
z*e*y*.com (WP 6.9.7) F Sep 3, 2026
i*e*a*a*q.org F Sep 3, 2026
z*s*g*.com (WP 7.0.2) F Sep 3, 2026
z*z*x*l.com A Sep 3, 2026
z*t*y*.com F Sep 3, 2026
z*p*n*.com F Sep 3, 2026
z*f*u*s*a*.com (WP 7.1) F Sep 3, 2026
z*l*n*e*.com (WP 7.1) F Sep 3, 2026
z*g*z*.com F Sep 3, 2026
z*e*i*n*h*y*.com (WP 7.1) F Sep 3, 2026
x*a*j*y*.com A Sep 1, 2026
l*n*t*i*e*.com A Aug 31, 2026
r*g*w*n*c*u*.com (WP 7.1) F Aug 29, 2026
g*i*o*f*c*.com (WP 7.0) F Aug 27, 2026
g*i*m*r*e*.com (WP 7.0) F Aug 27, 2026
q*m*n*c*s*i*g.com (WP 7.0.2) F Aug 26, 2026
b*s*o*e*c*r*.com (WP 7.0.2) F Aug 26, 2026
w*a*o*l.com (WP 7.1) F Aug 24, 2026
l*c*f*t*e*s.com (WP 7.1) F Aug 24, 2026
t*k*u*d*.com F Aug 23, 2026
m*j*n.com A Aug 22, 2026
g*w*r*o*t*n*r*i*e*.com (WP 7.0.2) F Aug 21, 2026
c*c*f*r*.com A Aug 21, 2026
t*m*h*h*c*.ir F Aug 21, 2026
m*s*u*.cn F Aug 21, 2026
t*n*e*t*r*s*.com F Aug 21, 2026
i*e*d*o*d*e*s*o*a*.com F Aug 20, 2026
e*f*h*n*i*a*n*i*e.ir F Aug 17, 2026
j*v*s*o*.com (WP 7.0.4) F Aug 17, 2026
i*a*g.com (WP 6.8.8) F Aug 17, 2026
s*n*o*t*c*.com F Aug 16, 2026
o*e*.c*.uk (WP 7.0.4) F Aug 16, 2026
i*l*s*p*o*t*r*t*c*.com (WP 7.0.4) F Aug 16, 2026
i*i*e*o*e*e.com F Aug 16, 2026
j*n*i*-*b.com B Aug 15, 2026
u*f*l*.com D Aug 15, 2026
j*n*o*a*.com F Aug 15, 2026
s*a*m*h*t*c*.com D Aug 14, 2026
b*i*i*m*c*i*e.com F Aug 14, 2026
s*i*a*f*b*e*g*e*n*o*s*s.com (WP 7.0) F Aug 14, 2026
h*2*4*.com F Aug 14, 2026
t*g*v*.com F Aug 6, 2026
o*e*i*t.com (WP 7.0.2) F Aug 2, 2026
f*j*h*.com F Aug 1, 2026
m*n*e*m*l*.com (WP 7.0.2) F Aug 1, 2026
m*g*a*i*a.com (WP 7.0.2) F Jul 31, 2026
m*g*a*i*.com (WP 7.0.2) F Jul 31, 2026
m*n*e*a*w*b.com B Jul 31, 2026
i*t*e*t*e*i*.com F Jul 31, 2026
r*n*h*g*o*a*.com (WP 7.0.2) F Jul 29, 2026
k*l*d*i*h*i*g.com F Jul 28, 2026
o*e*i*c.com (WP 7.0.2) F Jul 27, 2026
z*r*.pl F Jul 27, 2026
i*t*r*o*o*o*i*s.com (WP 7.0.2) F Jul 26, 2026
j*a*h*e*c*c.com F Jul 25, 2026
j*x*n*q*u.com F Jul 25, 2026
n*a*m*m*d*c.com (WP 6.9.4) F Jul 25, 2026
l*b*l*e*e*r*4*.com F Jul 25, 2026
p*c*c*t.com F Jul 24, 2026
i*f*h*n*i*a.ir F Jul 24, 2026
p*l*o*.com A Jul 24, 2026
c*i*a*u*o*g.com (WP 6.9.4) F Jul 23, 2026
i*g*i*e*.com (WP 7.0) F Jul 23, 2026
i*h*m*r*h*m*n*.jp F Jul 23, 2026
s*k*i*h*n.com F Jul 23, 2026
i*v*s*o*.c*m.pk F Jul 23, 2026
c*w*n*e*d*n*.c*m.cn F Jul 23, 2026
g*d*o*t*a*f*c.com F Jul 20, 2026
j*t*x.cn (WP 7.0.2) F Jul 20, 2026
f*n*i*l*c*r*c*l.com (WP 6.9.5) F Jul 19, 2026
i*f*r*e*.kg F Jul 19, 2026
a*l*j*e.com (WP 6.9.4) C Jul 18, 2026
3*8*m*.com F Jul 18, 2026