WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: recipe-block (Used by 48 domains)

Security snapshot

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

Grade A 0% Grade B 2% Grade C 2% Grade D 17% Grade F 79%
Fail the header check (F)79%vs 82.5% avg
Leak usernames60%vs 38.5% avg
Expose a sensitive file2.1%vs 1.8% avg
Use HTTPS92%vs 96.2% avg

What stands out

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

The largest measured difference is username enumeration: 60.4% versus 38.5% overall (+21.9 percentage points).

HTTPS adoption is 91.7% vs 96.2% overall (-4.5 pp); Header-grade F is 79.2% vs 82.5% overall (-3.3 pp); Sensitive-file exposure is 2.1% vs 1.8% overall (+0.3 pp).

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

Recipe Block

Organize your quarantine-inspired baking blog with a “Recipe” block! Adding this will insert a template with an image, heading, recipe information (serving size, time, duration), and a section for ingredients and directions. You can add and remove blocks from this container. When in the recipe block, you’ll be able to add extra Recipe Ingredients, Recipe Directions, and Recipe Meta blocks, along with audio, videos, galleries, and more. Note…

Domain Version Exposures Headers Last Checked
t*n*i*w*t*m*l*y.com (WP 6.8.3) F Sep 10, 2026
r*s*a*d*h*n*r*c*p*s.com (WP 7.1) D Sep 9, 2026
k*l*o*g*h*w.com (WP 6.8.8) F Sep 9, 2026
w*n*i*s*a*t*w*r*d.com (WP 7.1) F Sep 7, 2026
u*c*n*e*t*o*a*m*l*e*n*a*.com (WP 7.1) F Sep 4, 2026
m*s*i*a*s.com (WP 7.1) F Sep 3, 2026
j*h*r*n*h.com F Sep 2, 2026
y*u*s*u*d*u*h*t*r*.com F Aug 30, 2026
g*o*f*o*a*t*o*i*y.com F Aug 30, 2026
s*m*l*d*n*a*a*i*.com F Aug 29, 2026
h*i*i*n*a*t*o*o*y.com D Aug 29, 2026
l*v*b*i*h*n*t*i*i*n.com F Aug 28, 2026
j*s*i*a*r*e*w*l*n*s*.com F Aug 28, 2026
t*n*a*e*t*.com F Aug 26, 2026
l*f*a*d*o*e*i*h*h*r*s.com (WP 7.1) F Aug 24, 2026
s*e*l*n*s*o*w*l*n*s*.com (WP 7.1) F Aug 23, 2026
l*v*n*l*f*b*l*l*.com F Aug 23, 2026
m*k*t*h*n*l*t*e*.com (WP 5.9.16) F Aug 22, 2026
i*s*s*v*g*l*f*.com (WP 7.1) F Aug 21, 2026
t*a*h*a*t*c*o*.com (WP 7.1) F Aug 21, 2026
e*t*n*a*e*a*d*.com F Aug 21, 2026
l*m*n*r*v*l*n*.com (WP 6.8.8) D Aug 20, 2026
c*m*a*s*o*m*n*t*l*v*n*.com F Aug 20, 2026
i*p*e*s*o*s*t*o*e.com (WP 7.0.4) F Aug 18, 2026
a*v*n*u*e*i*o*.com (WP 7.0.4) F Aug 18, 2026
a*b*w*l*h.com (WP 7.0.4) F Aug 17, 2026
v*l*e*n*e*t.ca (WP 7.0.4) D Aug 17, 2026
c*l*h*.com F Aug 16, 2026
b*d*s*f*m*l*.com (WP 6.8.6) F Aug 2, 2026
t*e*a*d*r*n*a*r*.com (WP 7.0.2) D Aug 1, 2026
s*l*a*d*e*e*i*y.com (WP 7.0.2) F Jul 31, 2026
a*y*r*s*e*g*h.com (WP 7.0.2) F Jul 29, 2026
f*o*o*f*f*h.com F Jul 29, 2026
f*o*i*v*s*a.com (WP 7.0.1) D Jul 29, 2026
h*n*r*g*n*.com (WP 7.0.2) F Jul 29, 2026
a*s*k*n*t*i*i*n.com (WP 5.8.13) F Jul 29, 2026
f*o*r*s*k*d*i*t*g*a*i*e.com C Jul 28, 2026
t*e*l*m*y*u*s*.com (WP 7.0.2) F Jul 27, 2026
t*e*h*m*s*a*l*.com (WP 7.0.2) F Jul 27, 2026
k*t*k*o*l*s*o*e.com F Jul 26, 2026
j*u*n*y*o*a*l*.com (WP 7.0.2) F Jul 26, 2026
i*t*g*a*i*e*u*r*t*o*m*c*i*a*.com (WP 7.0.2) D Jul 25, 2026
t*e*b*l*n*e*-*l*t*.com (WP 7.0.2) B Jul 25, 2026
c*r*s*m*s*a*k*t*s*.com D Jul 25, 2026
t*e*u*n*s*d*u*r*c*p*s.com F Jul 24, 2026
b*r*n*a*b*t*.com (WP 7.0.2) F Jul 23, 2026
s*e*s*n*f*r*s.com F Jul 23, 2026
s*r*t*l*v*r*.com F Jul 20, 2026
f*r*a*i*t*c*b*o*.com (WP 7.0.2) F Jul 19, 2026