WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: simple-blog-card (Used by 466 domains)

Security snapshot

Across 466 simple-blog-card WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 1% Grade B 1% Grade C 4% Grade D 10% Grade F 84%
Fail the header check (F)84%vs 82.5% avg
Leak usernames52%vs 38.5% avg
Expose a sensitive file1.5%vs 1.8% avg
Use HTTPS96%vs 96.2% avg

What stands out

TLDWP currently associates 466 indexed WordPress sites with simple-blog-card, equivalent to 0% of the current WordPress dataset.

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

Header-grade F is 83.7% vs 82.5% overall (+1.2 pp); Sensitive-file exposure is 1.5% vs 1.8% overall (-0.3 pp); HTTPS adoption is 95.9% vs 96.2% overall (-0.3 pp).

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

Infrastructure patterns

Infrastructure detected alongside simple-blog-card. Percentages are within sites where that specific signal was detectable; the baseline compares the same signal across detected WordPress sites overall.

Co-occurrence describes technologies observed on the same sites. Detection coverage varies by signal, and an association does not imply that one technology caused or selected another.

Simple Blog Card

Blog card Generated with shortcode Generated with block Can specify the number of characters displayed in the description. Displays an ogp image. Can specify the size of the displayed ogp image. Can change the title and description. Warning A redirect loop occurs when all three of the following factors are met: * When two sites with different domains embed “Simple Blog Card” for each other on their top pages. * When two sites with different domains are on the same server (same IP address). * Whe…

Domain Exposures Headers Last Checked
f*b*l*e*s*f*i*a.com (WP 7.1) F Sep 9, 2026
o*e*i*h*s*a*d*l*v*.com F Sep 9, 2026
f*l*n*e.com (WP 6.9.7) F Sep 9, 2026
k*k*o*s*o*y.com (WP 6.9.7) F Sep 9, 2026
b*e*t*-*.com F Sep 9, 2026
o*e*i*h*o*c*.com (WP 6.8.1) F Sep 9, 2026
o*e*a*e*s*p*o*o*i*o*a.com F Sep 9, 2026
h*l*s*m*.com (WP 7.1) F Sep 8, 2026
s*u*h*e*k*e*o*t.com (WP 6.7.5) F Sep 8, 2026
h*k*t*-*a.com (WP 7.1) F Sep 8, 2026
m*b*.academy (WP 7.1) F Sep 8, 2026
k*o*s*i.clinic (WP 6.7.7) F Sep 8, 2026
o*o*c*i*f*s*e*y.org F Sep 8, 2026
o*d*o*d.com (WP 6.2.11) F Sep 8, 2026
h*d*m*s*l*n.com (WP 7.1) F Sep 8, 2026
a*j*a*n.com (WP 5.4.21) F Sep 7, 2026
w*d*i*g*e*i*w.net (WP 7.0.4) F Sep 7, 2026
k*n*i*u*d*.com (WP 6.2.11) F Sep 7, 2026
e*p*t*l*f*-*n*i*r*e*.com (WP 7.1) F Sep 7, 2026
k*n*o*n*o*o.com (WP 7.1) F Sep 7, 2026
d*s*u*5*.com F Sep 7, 2026
a*e*c*g*o*p*o*n*a*i*n*s.org (WP 6.4.10) D Sep 7, 2026
y*s*i*-*y*k*.com D Sep 7, 2026
k*n*-*i.com F Sep 7, 2026
k*n*k*-*a*i*y.com F Sep 7, 2026
e*p*c*o*d*n*m*c*s.com F Sep 7, 2026
k*m*r*c*i*o.com (WP 7.1) F Sep 7, 2026
s*l*r*s*n*w*e*o*a*.com (WP 7.1) F Sep 7, 2026
s*l*r*s*e*v*c*.com (WP 7.1) F Sep 7, 2026
s*l*r*s*a*d*c*p*n*.com (WP 7.1) F Sep 7, 2026
b*t*n*c*l*s*u*y.com (WP 6.8.8) F Sep 7, 2026
k*m*e*g*o*t.com F Sep 6, 2026
k*i*s*y*a*k.com (WP 7.1) F Sep 6, 2026
r*s*i*l*n*.com (WP 7.1) F Sep 6, 2026
s*y*e*t.c*.jp F Sep 6, 2026
k*m*f*r*.com (WP 6.9.7) F Sep 6, 2026
s*f*a*i*a*.com (WP 6.8.8) F Sep 6, 2026
t*e*d*o*k*.com F Sep 6, 2026
s*c*a*m*d*a*n*v*r*e.com (WP 7.1) F Sep 6, 2026
g*b*.net (WP 7.0.4) D Sep 5, 2026
d*l*a*a*i*a*u*g*n*c*r*.com (WP 7.1) F Sep 5, 2026
d*k*t*m*p*o*u*t*o*s.com (WP 7.1) F Sep 5, 2026
s*p*l*.c*.jp F Sep 5, 2026
a*s*h*t*c.expert F Sep 5, 2026
m*t*u*o*o*u*e.com (WP 7.1) F Sep 5, 2026
p*a*s*.jp F Sep 5, 2026
y*n*g*k*b*.com (WP 7.1) F Sep 5, 2026
m*t*-*o*t*a*l.com (WP 7.1) F Sep 5, 2026
t*a*e*d*d*.com F Sep 4, 2026
h*a*t*a*d*o*m.com (WP 7.0.4) D Sep 4, 2026
z*t*r*b*.com (WP 7.1) F Sep 4, 2026
r*l*n*l*s*p*y*h.com (WP 7.0.4) F Sep 4, 2026
y*j*m*c*i*o.com (WP 7.0.4) F Sep 4, 2026
s*i*e*b*d*m.com (WP 7.1) F Sep 4, 2026
r*k*s*i*m*g*r*.com F Sep 4, 2026
h*r*k*u*t*k*o.o*.jp F Sep 4, 2026
j*a*i*c*l*s*a*.com (WP 7.0.2) C Sep 4, 2026
a*d*s*n*o*s.com (WP 7.0.4) D Sep 4, 2026
s*n*l*n*i*g.com F Sep 4, 2026
t*a*y*s*g*t*a.com F Sep 4, 2026
f*m*l*a*-*a*r.com F Sep 3, 2026
k*g*y*m*-*b*.com (WP 7.1) F Sep 3, 2026
d*f*n*c*a*e.c*m.cn C Sep 3, 2026
k*z*-*a*.com (WP 7.1) F Sep 3, 2026
n*v*s*o*s*s.com (WP 7.1) F Sep 3, 2026
k*y*a*l*i*.com (WP 6.8.8) F Sep 3, 2026
b*u*i*k*.com F Sep 3, 2026
k*w*b*r*y.com B Sep 2, 2026
n*t*r*c*y*h*r*.com F Sep 2, 2026
h*u*o*-*u*.com F Sep 2, 2026
b*o*s*m*a*p*l*f*.com (WP 7.1) D Sep 2, 2026
a*a*e*e*-*w*k*.com (WP 6.9.7) F Sep 2, 2026
e*c*p*w*e*l*.com (WP 7.1) F Sep 2, 2026
a*a*i*m*i*e*.com (WP 7.0.4) F Sep 2, 2026
t*s*i*g*h*.com F Sep 2, 2026
h*t*r*k*-*i*s.com F Sep 2, 2026
n*s*a*g*c*v*d*o*g*m*s.com F Sep 2, 2026
l*a*-*r*u*.c*.jp F Sep 2, 2026
t*s*n*i*e*r*n*.com (WP 7.0.4) D Sep 2, 2026
d*g*t*l*e*e*g*.ru (WP 5.7.17) D Sep 1, 2026
c*l*u*e*b*o*h.com F Sep 1, 2026
w*s*o*u*.jp D Sep 1, 2026
j*c*w*b.com F Sep 1, 2026
b*e*t*a*a*.com D Sep 1, 2026
n*o*n*t*r*w*r*s.net (WP 6.6.7) F Sep 1, 2026
e*i*u*c*a*h*n*.de (WP 7.1) F Sep 1, 2026
n*r*h*a*e*e*t*o*o*y.com (WP 7.1) F Sep 1, 2026
n*n*r*n.com F Aug 31, 2026
y*z*-*q*0.com (WP 7.1) F Aug 31, 2026
b*a*k*p*c*n*u*t*n*y.com (WP 7.1) F Aug 31, 2026
r*k*e*-*t*d*s*a*e.com (WP 6.9.7) F Aug 31, 2026
b*a*k*i*c*n*r*c*o*s.com (WP 6.8.8) F Aug 31, 2026
a*o*t*o*i*.com F Aug 31, 2026
y*l*a*c*k*s.com (WP 7.1) F Aug 31, 2026
j*r*e*a*a*c*n.com (WP 7.1) F Aug 31, 2026
n*n.mk (WP 7.1) F Aug 31, 2026
c*c*n*-*e*.com F Aug 31, 2026
h*p*o*o*l*.nl D Aug 31, 2026
t*k*m*n*i.com (WP 7.1) F Aug 31, 2026
m*r*o*g*e*e*s.com F Aug 30, 2026