WordPress maintenance or security needs? Reach out!
TLDWP

Theme: digicove (Used by 63 domains)

Security snapshot

Across 63 digicove WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 5% Grade D 5% Grade F 90%
Fail the header check (F)90%vs 82.6% avg
Leak usernames38%vs 38.6% avg
Expose a sensitive file6.3%vs 1.8% avg
Use HTTPS98%vs 96.3% avg

What stands out

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

The largest measured difference is header-grade F: 90.5% versus 82.6% overall (+7.9 percentage points).

Sensitive-file exposure is 6.3% vs 1.8% overall (+4.5 pp); HTTPS adoption is 98.4% vs 96.3% overall (+2.1 pp); Username enumeration is 38.1% vs 38.6% overall (-0.5 pp).

These are observational associations among sites where TLDWP detected digicove, 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 49
.co 2
.ru 1
.hu 1
.de 1
.fr 1
.net 1
.ba 1
.in 1
.mx 1
.it 1

digicove 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
k*n*c*o.com (WP 6.6.7) 1.0.5· 100% conf. F Sep 9, 2026
r*v*n*e*i*e*s.com (WP 6.7.2) F Sep 7, 2026
t*a*e*a*s*r*.com (WP 7.0.4) F Sep 4, 2026
s*u*m*r*e*e*m.com (WP 7.1) F Sep 3, 2026
j*r*x*.com (WP 7.1) F Sep 3, 2026
k*y*e*u*.com (WP 7.0) F Sep 3, 2026
s*a*a*.com (WP 6.9.4) F Sep 3, 2026
t*c*n*m*d*x.com (WP 7.0.3) F Sep 1, 2026
s*i*t*n*i*.com F Sep 1, 2026
b*z*o*a.com (WP 7.1) F Aug 31, 2026
l*c*h.com F Aug 29, 2026
g*i*i*.co (WP 7.1) F Aug 29, 2026
s*o*o*e*o*m*r*e.com (WP 7.1) F Aug 28, 2026
w*n*s*e*.com (WP 7.1) F Aug 27, 2026
s*e*h*n.com (WP 6.9.7) F Aug 26, 2026
p*b*i*e*o*l*n*.it (WP 7.1) F Aug 25, 2026
j*p*n*l*x.com (WP 6.8.8) F Aug 24, 2026
s*l*c*a*g*n*y.com (WP 7.0.4) F Aug 24, 2026
w*t*e*s*u*s*m*d*a.com (WP 6.9.7) D Aug 24, 2026
a*a*a*e*i*.com (WP 7.1) F Aug 23, 2026
a*a*k*s.com (WP 7.1) F Aug 23, 2026
a*w*s*g*o*p.com (WP 7.1) F Aug 23, 2026
b*l*e*e*d.com (WP 7.0.4) F Aug 23, 2026
w*b*w*y*s.com (WP 7.1) F Aug 21, 2026
t*e*i*i*a*v*l*e*.com (WP 7.0.3) F Aug 21, 2026
i*e*p*r*-*r*u*.com (WP 7.1) F Aug 21, 2026
p*o*o*i*e*o*e*u.com (WP 7.1) C Aug 21, 2026
h*s*i*s.c*m.bd (WP 7.0.4) F Aug 20, 2026
a*h*e*i.com (WP 6.6.7) F Aug 20, 2026
a*5*t*a.com (WP 7.0.4) F Aug 19, 2026
j*-*a*k*t*n*.co F Aug 17, 2026
u*s*r*a*i*e.com (WP 7.0.4) F Aug 16, 2026
s*a*a*s*l*t*o*s.com (WP 6.9.4) F Aug 16, 2026
j*g*o*t*m*d*a.com (WP 7.0.4) F Aug 16, 2026
a*s*j*s*.com (WP 7.0.4) F Aug 16, 2026
a*s*f*y.com F Aug 16, 2026
m*s*k*.mx D Aug 15, 2026
p*s*i*e*o*m*r*e*.com (WP 7.0.4) F Aug 15, 2026
d*n*i*i*a*.com F Aug 15, 2026
p*t*k*a*e*c*.hu (WP 7.0.3) D Aug 7, 2026
v*l*o*k*e*i*.com (WP 7.0.2) F Aug 4, 2026
g*j*c*m.com (WP 7.0.2) C Aug 3, 2026
m*o*m*d*a.de (WP 7.0.2) F Aug 2, 2026
a*i*n*w*r*d.com (WP 7.0.2) F Aug 1, 2026
h*p*g*o*l*b*.com (WP 7.0.2) C Jul 30, 2026
n*t*y*i*g*o*a*.com (WP 7.0.2) F Jul 27, 2026
p*o*n*x*e*d*v*l*p*r*.in (WP 7.0.2) F Jul 24, 2026
p*n*m*p.com (WP 7.0.2) F Jul 24, 2026
t*z*i*d*e*i*.com (WP 7.0.2) F Jul 24, 2026
e*t*h.ba (WP 7.0.2) F Jul 24, 2026
p*p*c*e*t*v*.com (WP 7.0.2) F Jul 24, 2026
m*o*m*d*a.com (WP 7.0.2) F Jul 23, 2026
t*s*p*r*e*q*e*a*.online (WP 7.0.2) F Jul 23, 2026
a*v*r*i*i*g*n*i*.net F Jul 22, 2026
d*g*t*l*i*e*m*r*e*i*g.com (WP 7.0.2) F Jul 22, 2026
d*g*t*l*i*e*b*.com (WP 7.0.2) F Jul 22, 2026
d*g*t*l*e*a*.com (WP 7.0) F Jul 22, 2026
s*g*e*m*r*c.com (WP 7.0.2) F Jul 22, 2026
w*b*a*t*r*s.ru (WP 6.9.5) F Jul 22, 2026
e*o*s*l*t*o*.fr F Jul 22, 2026
p*y*e*c*l*.agency (WP 6.4.3) F Jul 21, 2026
m*s*c*e*t*v*s*l.com (WP 7.0.2) F Jul 21, 2026
a*a*e*w*b.com (WP 6.9.5) F Jul 20, 2026