WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: js-composer-extend-kingdom (Used by 11 domains)

Security snapshot

Across 11 js-composer-extend-kingdom WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 9% Grade B 0% Grade C 0% Grade D 0% Grade F 91%
Fail the header check (F)91%vs 82.5% avg
Leak usernames27%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS91%vs 96.2% avg

What stands out

TLDWP currently associates 11 indexed WordPress sites with js-composer-extend-kingdom, equivalent to 0% of the current WordPress dataset.

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

Header-grade F is 90.9% vs 82.5% overall (+8.4 pp); HTTPS adoption is 90.9% vs 96.2% overall (-5.3 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).

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

js-composer-extend-kingdom 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
p*c*e*f*n*a*e.net (WP 7.1) F Sep 4, 2026
s*o*h*p*y*a*s.com (WP 6.4.3) F Aug 28, 2026
g*i*a*s*o*p.com (WP 7.0.4) F Aug 26, 2026
3*5*m*s*c.com (WP 6.4.3) F Aug 24, 2026
p*r*e*t*v*o*t*o*r*.com (WP 7.0.4) F Aug 20, 2026
w*t*r*o*e*v*s*o*e*.com (WP 7.0.4) F Aug 17, 2026
n*n*m*l*h*n*i*g.com (WP 7.0.2) F Aug 2, 2026
n*r*t*c*s*o*e.com (WP 6.4.3) F Jul 26, 2026
p*s*t*p*4.com (WP 6.4.8) A Jul 23, 2026
z*y*a*t.com (WP 7.0.2) F Jul 19, 2026
r*c*o*e*.com (WP 7.0.2) F Jul 18, 2026