WordPress maintenance or security needs? Reach out!
TLDWP

Theme: carshire (Used by 54 domains)

Security snapshot

Across 54 carshire WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 0% Grade D 9% Grade F 91%
Fail the header check (F)91%vs 82.5% avg
Leak usernames44%vs 38.5% avg
Expose a sensitive file1.9%vs 1.8% avg
Use HTTPS100%vs 96.2% avg

What stands out

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

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

Username enumeration is 44.4% vs 38.5% overall (+5.9 pp); HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Sensitive-file exposure is 1.9% vs 1.8% overall (+0.1 pp).

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

Where these sites live — top 9 domain endings
.com 45
.ru 2
.lv 1
.hu 1
.de 1
.net 1
.es 1
.ch 1

carshire 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
h*l*e*g*e*n*a*a*e.com (WP 7.1) F Sep 8, 2026
b*a*e*t*p*n*a*t*r*p*i*.com (WP 7.0.4) D Sep 8, 2026
a*k*r*p*u*e*t.com (WP 6.2.9) F Sep 7, 2026
h*r*d*n*u*o*e*v*c*.com F Sep 7, 2026
m*-*t*.ru (WP 7.1) F Sep 6, 2026
a*a*k*v*s*i*a.com (WP 7.1) F Sep 5, 2026
a*a*a*o*o*a*z*l*e*v*s.com (WP 6.2.11) F Sep 3, 2026
b*k*a*a*e.c*m.tr (WP 7.1) F Sep 3, 2026
r*y*a*m*t*r.com (WP 7.1) F Sep 2, 2026
h*s*y*o*l*s*o*c*n*e*.com (WP 5.6.19) D Sep 2, 2026
b*i*d*b*d*s*g*m*i*e.com (WP 7.1) F Sep 1, 2026
s*u*-*u*a.com (WP 4.7.29) D Sep 1, 2026
x*p*c*l*r.com (WP 6.7.7) F Aug 31, 2026
w*r*d*i*e*u*o*o*y*c.com D Aug 30, 2026
j*h*s*u*o*o*i*e*e*a*r.com (WP 6.8.8) F Aug 30, 2026
b*r*a*o*b*.net (WP 5.8.13) F Aug 29, 2026
g*j*n*.com F Aug 28, 2026
t*c*s*r*v*r*e.com (WP 4.9.31) F Aug 28, 2026
j*g*s*r*i*e.com (WP 6.1.12) F Aug 23, 2026
t*c*r*n*u*o*a*i*n.com (WP 7.1) F Aug 20, 2026
h*n*c*r*u*i*g.de (WP 6.6.2) F Aug 20, 2026
v*n*a*t*o*l*s*o*.com (WP 6.9.7) F Aug 18, 2026
s*r*n*m*b*l.com (WP 6.9.7) F Aug 17, 2026
n*u*a*i*o*m*r*a*o.es (WP 6.4.10) F Aug 17, 2026
g*r*a*a*t*e*p*r*.com (WP 7.0.4) F Aug 17, 2026
a*r*o*o*s.lv (WP 7.0.3) F Aug 9, 2026
v*r*a*u*o*u*e*y.hu (WP 4.5.32) F Aug 1, 2026
a*i*l*a*i*e*t.com (WP 4.4.2) F Aug 1, 2026
c*a*u*d*m*t*r*.com (WP 7.0.2) F Jul 31, 2026
a*t*v*d*i*.com (WP 7.0.2) F Jul 31, 2026
f*p*o*y*h*p.com D Jul 31, 2026
a*t*g*a*s*e*a*r*o*p*n*.com F Jul 31, 2026
a*t*g*a*s*e*a*r*a*m*e*c*.com F Jul 31, 2026
a*t*g*a*s*e*a*r*o*p*n*.com F Jul 31, 2026
a*t*g*a*s*e*a*r*r*w*r*.com F Jul 31, 2026
a*t*g*a*s*e*a*r*o*a*a*o*.com F Jul 31, 2026
a*t*g*a*s*e*a*r*f*.com F Jul 31, 2026
a*t*-*u*g*r.com (WP 6.9.5) F Jul 31, 2026
a*t*-*e*h*n*e.com (WP 6.8.1) F Jul 31, 2026
w*o*y*u*o*o*i*e.com (WP 6.9.1) F Jul 30, 2026
a*c*y.com (WP 6.9.5) F Jul 28, 2026
n*u*a*i*o*m*r*a*o.com (WP 6.4.8) F Jul 27, 2026
c*m*u*o*d*b*i.com (WP 4.8.25) F Jul 26, 2026
h*m*n*o*i*.com (WP 4.8.25) F Jul 24, 2026
u*u*l*r*a*i*a.com (WP 7.0.2) F Jul 22, 2026
o*o*o*i*m*r*t.com (WP 5.8.2) F Jul 22, 2026
l*g*b.ch (WP 6.2.9) F Jul 22, 2026
b*r*e*s*a*t*f*i*a.com (WP 4.8.25) F Jul 22, 2026
s*r*e*l*b*l*t*e*.com (WP 7.0.2) F Jul 21, 2026
m*r*o*o*a*t*k.com (WP 5.4.19) F Jul 21, 2026
a*p*i*n*e*e*a*r*w*i*t*e*.com (WP 6.0.1) F Jul 19, 2026
h*g*d*e*e*p*w*r.com (WP 4.7.3) F Jul 19, 2026
b*l*r*m*.ru F Jul 19, 2026
t*r*o*u*r*.com F Jul 19, 2026