WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: jpnp_bot_stop (Used by 6 domains)

Security snapshot

Across 6 jpnp_bot_stop WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 0% Grade D 17% Grade F 83%
Fail the header check (F)83%vs 82.5% avg
Leak usernames0%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS83%vs 96.2% avg

What stands out

TLDWP currently associates 6 indexed WordPress sites with jpnp_bot_stop, equivalent to 0% of the current WordPress dataset.

The largest measured difference is username enumeration: 0% versus 38.5% overall (-38.5 percentage points).

HTTPS adoption is 83.3% vs 96.2% overall (-12.9 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp); Header-grade F is 83.3% vs 82.5% overall (+0.8 pp).

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

jpnp_bot_stop 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
g*e*i*p*r*p*a*e*s.org (WP 6.9.1) F Sep 5, 2026
t*a*c*s*c*e*s*u*.com (WP 6.8.3) F Sep 4, 2026
m*d*e*t*e*e*a*.com F Jul 31, 2026
c*u*t*y*l*b*i*l*.org D Jul 21, 2026
f*n*i*g*o*m*n*c*t*o*s.com F Jul 19, 2026
a*s*p*h*m*e*.org (WP 6.7.4) F Jul 18, 2026