WordPress maintenance or security needs? Reach out!
TLDWP

Theme: agrikon-child (Used by 65 domains)

Security snapshot

Across 65 agrikon-child WordPress sites indexed by TLDWP, compared to the all-WordPress average.

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

Grade A 3% Grade B 0% Grade C 2% Grade D 5% Grade F 91%
Fail the header check (F)91%vs 82.5% avg
Leak usernames44%vs 38.5% avg
Expose a sensitive file4.7%vs 1.8% avg
Use HTTPS98%vs 96.2% avg

What stands out

TLDWP currently associates 65 indexed WordPress sites with agrikon-child, equivalent to 0% of the current WordPress dataset.

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

Username enumeration is 43.8% vs 38.5% overall (+5.3 pp); Sensitive-file exposure is 4.7% vs 1.8% overall (+2.9 pp); HTTPS adoption is 98.4% vs 96.2% overall (+2.2 pp).

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

Where these sites live — top 15 domain endings
.com 45
.de 3
.pt 2
.org 2
.fr 2
.hu 1
.pl 1
.co.in 1
.ir 1
.ru 1
.gr 1
.eu 1
.sn 1

agrikon-child 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*k*a*a.ru F Sep 7, 2026
n*t*i*a*m*.com (WP 6.7.2) F Sep 5, 2026
r*b*l*e*r*s*i*u*.com F Sep 4, 2026
m*r*s*v*d*.com (WP 6.8.2) F Sep 1, 2026
f*n*a*j*m*c*r*t.pl (WP 6.9.7) F Aug 30, 2026
b*s*n*u*s*r*.com (WP 6.2.11) F Aug 30, 2026
g*c*e*t*r*m.com (WP 7.0.2) F Aug 27, 2026
q*a*i*y*o*s*i*g.com (WP 7.1) F Aug 27, 2026
a*f*f*o*.com (WP 6.9.7) F Aug 27, 2026
b*r*y*a*c*f*r*.com (WP 7.1) C Aug 25, 2026
s*n*f*o*s.c*m.mx (WP 6.9.4) A Aug 24, 2026
s*i*a*e*.c*.in (WP 7.1) F Aug 24, 2026
j*m*a*e*.com (WP 7.0.2) F Aug 24, 2026
j*m*a*v*t.com (WP 7.0.2) F Aug 24, 2026
a*a*i*-*g*i*u*t*r*.com (WP 7.1) F Aug 23, 2026
c*o*d*g*u*f.com F Aug 23, 2026
s*h*e*m*e*l*.de (WP 7.1) F Aug 23, 2026
e*o*e*l*t*u*a.com (WP 7.1) F Aug 22, 2026
s*z*l*u*.com (WP 7.1) F Aug 22, 2026
e*c*.e*u.gt F Aug 22, 2026
i*t*r*o*p.org (WP 7.1) F Aug 21, 2026
p*a*t*s*e*e*.com (WP 7.1) F Aug 21, 2026
a*i*t*i*s*e*.com (WP 7.0.4) F Aug 21, 2026
a*r*c*n*.com (WP 6.8.1) F Aug 20, 2026
a*r*m*a*i*s*i*n*e.com (WP 7.1) F Aug 20, 2026
a*r*c*l*p*c*f*c*s*r.com (WP 7.1) F Aug 20, 2026
a*r*a*z.com (WP 7.0.4) F Aug 20, 2026
l*b*n*f*t*e*m*t*e*.com (WP 7.0.4) F Aug 19, 2026
n*t*r*m.gr (WP 7.0.4) F Aug 18, 2026
a*r*-*a*k*e*.com (WP 7.0.4) F Aug 18, 2026
a*t*b*g*r*a*.com (WP 7.0.4) F Aug 18, 2026
o*s*h*f*h*i*e*g*r.de (WP 6.9.4) F Aug 15, 2026
g*m*r*h*a*t*.com F Aug 15, 2026
s*r*u*h*a*a*.ir F Aug 14, 2026
l*v*s*p*t*n*i*i*o*s*g*k.hu (WP 7.0.2) D Aug 6, 2026
a*o*o*o.pt (WP 7.0.2) F Aug 4, 2026
b*b*e*h.com F Aug 1, 2026
c*a*c*r*a.com F Jul 31, 2026
l*m*n*a*k*t.com (WP 7.0.2) F Jul 30, 2026
s*l*g*i*r*i*.com (WP 7.0.2) F Jul 30, 2026
n*t*v*w*k*.pt (WP 6.7.1) F Jul 29, 2026
k*a*t*e*t.com (WP 7.0.2) D Jul 28, 2026
r*c*e*i*e*l*a*m*.com (WP 7.0.2) F Jul 27, 2026
l*s*t*t*r*c*.fr (WP 6.9.5) F Jul 27, 2026
d*g*a*k*e*c*n*.com F Jul 26, 2026
l*i*f*l*n*.com F Jul 26, 2026
s*s*a*r*.eu A Jul 26, 2026
r*d*a*e*l*n*u*t*i*s.com (WP 7.0.2) F Jul 26, 2026
t*a*g*e*n*g*o.com (WP 7.0.2) F Jul 24, 2026
l*r*e*a*u*a*s*l*t*o*s.com (WP 7.0.2) F Jul 22, 2026
b*r*a*-*t*d*s*n*t.fr (WP 7.0.2) F Jul 22, 2026
k*h*t*r*l*f*s*a*e*.com F Jul 21, 2026
k*h*t*r*g*o*p.com F Jul 21, 2026
k*h*t*r*f*r*s.com F Jul 21, 2026
i*f*c*.org (WP 7.0.2) F Jul 20, 2026
k*s*o*g*o.com (WP 6.0.2) F Jul 20, 2026
k*a*t*e*t.de (WP 7.0) D Jul 19, 2026
g*s*i*f*o*.com (WP 6.8.2) F Jul 19, 2026
f*d*s*.sn (WP 6.6.5) F Jul 19, 2026
g*n*a*c*s*e*c*u*t*r.com (WP 7.0.2) F Jul 19, 2026
r*m*f*o*a.com (WP 7.0.2) F Jul 18, 2026
h*m*y*f*r*.com (WP 6.9.5) F Jul 18, 2026
f*a*h*e*r*e*.com (WP 7.0.2) F Jul 18, 2026
a*a*e*r*p*.com B Jul 17, 2026
h*g*m*u*t*i*p*o*e*s*n*.com (WP 7.0.1) F Jul 17, 2026