WordPress maintenance or security needs? Reach out!
TLDWP

Theme: recipe-blogger (Used by 48 domains)

Security snapshot

Across 48 recipe-blogger WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 6% Grade B 0% Grade C 4% Grade D 23% Grade F 67%
Fail the header check (F)67%vs 82.6% avg
Leak usernames54%vs 38.7% avg
Expose a sensitive file2.1%vs 1.8% avg
Use HTTPS98%vs 96.3% avg

What stands out

TLDWP currently associates 48 indexed WordPress sites with recipe-blogger, equivalent to 0% of the current WordPress dataset.

The largest measured difference is header-grade F: 66.7% versus 82.6% overall (-15.9 percentage points).

Username enumeration is 54.2% vs 38.7% overall (+15.5 pp); HTTPS adoption is 97.9% vs 96.3% overall (+1.6 pp); Sensitive-file exposure is 2.1% vs 1.8% overall (+0.3 pp).

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

Where these sites live — top 2 domain endings
.com 47
.net 1

recipe-blogger 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
d*l*a*r*a*e*.com (WP 6.8.8) 1.3.8· 100% conf. C Sep 11, 2026
a*l*a*a*t*i*t*e*i*c*e*.com (WP 7.1) 1.0.0· 100% conf. D Sep 10, 2026
d*s*e*t*a*d*r*n*s.com (WP 7.1) F Sep 7, 2026
d*n*t*a*s*w*e*.com (WP 7.1) D Sep 6, 2026
t*c*n*i*l*a*o.net (WP 7.1) D Sep 6, 2026
d*e*o*e*a*i*.com (WP 7.1) F Sep 4, 2026
b*e*s*d*e*o*d*r*z*.com (WP 7.1) A Sep 1, 2026
w*i*e*l*l*f*s*y*e.com (WP 7.1) D Aug 30, 2026
a*l*h*n*s*a*p*b*y.com (WP 7.1) F Aug 30, 2026
s*m*l*u*b*e*a*l*.com F Aug 29, 2026
l*v*l*u*h*o*e.com F Aug 28, 2026
n*t*r*l*o*f*r*k*t*h*n.com (WP 6.4.10) F Aug 28, 2026
m*j*r*r*b*a*e.com (WP 7.1) C Aug 26, 2026
c*u*t*l*n*t*x*s.com F Aug 26, 2026
c*u*t*n*f*n*e*s*n*t*e*.com F Aug 26, 2026
m*r*s*i*c*e*l*g*c*.com (WP 7.1) A Aug 23, 2026
b*l*i*n*o*d*e.com F Aug 23, 2026
t*e*e*c*h*m*a*e*t.com (WP 7.1) F Aug 21, 2026
c*m*o*n*m*d*.com (WP 7.0.4) F Aug 20, 2026
s*n*u*n*a*a*.com D Aug 15, 2026
m*h*m*l*o*b*o*.com F Aug 9, 2026
t*e*c*u*i*n.com (WP 7.0.2) F Aug 1, 2026
t*e*o*n*a*n*i*c*e*.com F Jul 31, 2026
f*r*n*a*a*e.com (WP 7.0.2) F Jul 30, 2026
m*s*s*a*e*o.com (WP 7.0.2) F Jul 30, 2026
f*e*c*g*r*c*i*i*e.com (WP 7.0.2) D Jul 30, 2026
f*o*n*p*r*.com D Jul 29, 2026
f*o*c*u*h*s.com (WP 6.8.6) D Jul 29, 2026
t*e*r*g*l*p*n*t*r.com (WP 7.0.2) F Jul 29, 2026
n*w*t*r*f*r*e.com (WP 7.0.1) F Jul 29, 2026
m*n*g*m*r*v*s*a*r*u*.com (WP 7.0.2) F Jul 29, 2026
t*e*a*c*r*l*b.com (WP 7.0.2) D Jul 28, 2026
t*e*a*l*s*e*h*l.com (WP 6.9.5) A Jul 28, 2026
l*r*c*t*m*m*.com (WP 7.0.2) F Jul 28, 2026
g*i*l*n*g*a*d*a.com (WP 7.0.2) F Jul 28, 2026
t*e*l*g*e*p.com F Jul 27, 2026
m*d*s*m*r*e*s.com (WP 7.0.2) F Jul 26, 2026
p*n*c*e*m*i*.com (WP 6.8.6) F Jul 26, 2026
n*l*o*r*a*g*r*e*.com (WP 7.0.2) F Jul 26, 2026
k*m*a*r*t*e*s.com (WP 7.0.2) F Jul 26, 2026
t*e*s*i*k*-*i*c*e*.com F Jul 25, 2026
s*r*w*e*r*s*o*t*a*e*.com F Jul 25, 2026
v*c*o*y*n*i*i*e*s*o*.com (WP 7.0.2) F Jul 24, 2026
c*o*o*a*e*h*c*l*t*a*d*o*e.com (WP 7.0) F Jul 24, 2026
o*n*a*t*r*c*p*s.com (WP 7.0.2) D Jul 23, 2026
h*w*o*s*h*.com (WP 7.0.2) F Jul 23, 2026
b*o*o*e*i*e*.com F Jul 21, 2026
f*a*t*n*o*f*u*t.com (WP 6.8.6) D Jul 21, 2026