WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: spider-random-post (Used by 7 domains)

Security snapshot

Across 7 spider-random-post WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 43% Grade D 0% Grade F 57%
Fail the header check (F)57%vs 82.5% avg
Leak usernames71%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS57%vs 96.2% avg

What stands out

TLDWP currently associates 7 indexed WordPress sites with spider-random-post, equivalent to 0% of the current WordPress dataset.

The largest measured difference is HTTPS adoption: 57.1% versus 96.2% overall (-39.1 percentage points).

Username enumeration is 71.4% vs 38.5% overall (+32.9 pp); Header-grade F is 57.1% vs 82.5% overall (-25.4 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).

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

spider-random-post Premium / Custom

This plugin is not available on WordPress.org. It may be a premium plugin, a custom plugin, or a plugin from a third-party marketplace.

Domain Exposures Headers Last Checked
t*p*o*l*n*-*u*h*.de (WP 3.5.2) F Aug 29, 2026
w*b*t*l*.de (WP 3.4.2) F Aug 29, 2026
t*p*r*i*e*o*t*l*.de F Aug 29, 2026
m*u*h*s*d*-*e*h*.com (WP 7.0.4) C Aug 14, 2026
n*c*l*s*a*l*s.com (WP 7.0.2) C Jul 31, 2026
l*-*e*h*-*-*a*m*u*h*.com C Jul 25, 2026
v*i*r*.com (WP 4.4.33) F Jul 21, 2026