WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: yesno-ext-send-answer (Used by 59 domains)

Security snapshot

Across 59 yesno-ext-send-answer WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 0% Grade D 0% Grade F 100%
Fail the header check (F)100%vs 82.5% avg
Leak usernames7%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS97%vs 96.2% avg

What stands out

TLDWP currently associates 59 indexed WordPress sites with yesno-ext-send-answer, equivalent to 0% of the current WordPress dataset.

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

Header-grade F is 100% vs 82.5% overall (+17.5 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp); HTTPS adoption is 96.6% vs 96.2% overall (+0.4 pp).

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

yesno-ext-send-answer 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
k*d*-*n*r*.com (WP 7.1) F Sep 9, 2026
k*n*k*s*t*b*-*h*n*a*.com (WP 7.1) F Sep 6, 2026
k*n*d*-*u*s*i*n.com (WP 7.1) F Sep 6, 2026
r*p*r*-*.com F Sep 6, 2026
k*i*u*d*n*g*o*-*h*n*a*.com (WP 7.1) F Sep 5, 2026
k*i*a*-*h*n*i*r*c*u*t.com (WP 7.1) F Sep 5, 2026
d*i*o*h*k*i*s*i*d*n.com (WP 7.1) F Sep 5, 2026
u*a*h*l*e*g*r*.com (WP 7.1) F Sep 5, 2026
r*m*i*e*s*i*d*n.com (WP 7.1) F Sep 4, 2026
r*m*k*-*o*e*s*i*d*n.com (WP 7.1) F Sep 4, 2026
x*p*x*s*i*d*n.com (WP 7.1) F Sep 4, 2026
m*r*s*u*9*3.com (WP 7.1) F Sep 3, 2026
s*u*r*-*o*k.com F Sep 3, 2026
k*t*k*m*t*n*s*i*d*n.com (WP 7.1) F Sep 2, 2026
t*w*-*x*r*s*-*h*n*a*.com (WP 7.1) F Sep 2, 2026
l*g*s*l*-*h*n*a*.com (WP 7.1) F Aug 30, 2026
e*e*g*-*u*p*r*-*h*n*a*.com (WP 7.1) F Aug 29, 2026
h*j*m*-*a*e*s*-*h*n*a*.com (WP 7.1) F Aug 29, 2026
t*m*r*k*g*o*s*i*d*n.com (WP 7.1) F Aug 28, 2026
t*m*i*r*c*u*t.com (WP 7.1) F Aug 28, 2026
s*i*s*a*q*e*t*o*.com (WP 7.1) F Aug 27, 2026
l*s*r*u.com (WP 7.1) F Aug 27, 2026
s*i*a*a*a*k*i*y*u*e*t*y.com (WP 7.1) F Aug 27, 2026
q*-*h*n*a*.com (WP 7.1) F Aug 27, 2026
s*i*a*u*e*t*y.com (WP 7.1) F Aug 26, 2026
n*k*y*m*d*n*i*s*i*d*n.com (WP 7.1) F Aug 26, 2026
n*k*g*w*k*u*y*u*e*t*y.com (WP 7.1) F Aug 25, 2026
e*i*-*h*n*a*.com (WP 7.1) F Aug 25, 2026
n*g*s*i*a*d*n*y*u*h*.com (WP 7.1) F Aug 25, 2026
s*s*e*h*a*t*-*h*n*a*.com (WP 7.1) F Aug 25, 2026
n*k*i*a*o*s*-*h*n*a*.com (WP 7.1) F Aug 24, 2026
n*a*o*q*e*t*o*.com (WP 7.1) F Aug 24, 2026
s*k*k*n*s*i*d*n.com (WP 7.1) F Aug 24, 2026
s*i*h*n*d*n*s*i*d*n.com (WP 7.1) F Aug 24, 2026
g*i*e*i*i*d*n.com (WP 7.0.4) F Aug 18, 2026
c*i*i*-*o*-*a*-*h*n*a*.com (WP 7.0.4) F Aug 18, 2026
m*e*-*h*n*a*.com (WP 7.0.4) F Aug 17, 2026
u*o*k*-*h*n*a*.com (WP 7.0.4) F Aug 16, 2026
f*j*p*i*t*s*i*d*n.com (WP 7.0.4) F Aug 15, 2026
f*j*n*k*n*o*.com F Aug 15, 2026
n*c*i*i*e*k*k*g*o*s*i*d*n.com (WP 7.0.2) F Jul 30, 2026
s*k*r*-*e*v*c*-*h*n*a*.com (WP 7.0.2) F Jul 30, 2026
s*f*t*-*t*g*-*h*n*a*.com (WP 7.0.2) F Jul 29, 2026
i*h*b*u*s*i*d*n.com (WP 7.0.2) F Jul 28, 2026
s*e*i*d*n*e*s*-*h*n*a*.com (WP 7.0.2) F Jul 28, 2026
a*s*s*a*f*-*h*n*a*.com (WP 7.0.2) F Jul 27, 2026
a*i*t*e*v*c*-*h*n*a*.com (WP 7.0.2) F Jul 26, 2026
m*h*-*h*n*a*.com (WP 7.0.2) F Jul 25, 2026
k*o*r*t*-*h*n*a*.com (WP 7.0.2) F Jul 24, 2026
d*x*e*t*s*i*d*n.com (WP 7.0.2) F Jul 24, 2026
m*t*u*k*r*.com (WP 7.0.2) F Jul 24, 2026
f*r*d*o*.jp F Jul 23, 2026
k*u*i*-*e*r*i*.com (WP 7.0.2) F Jul 20, 2026
k*u*h*n*s*i*d*n.com (WP 7.0.2) F Jul 20, 2026
k*t*b*k*-*e*k*u*r*c*u*t.com (WP 7.0.2) F Jul 20, 2026
k*b*t*-*u*s*i*n*a*r*.com (WP 7.0.2) F Jul 20, 2026
o*e*o*a*t*i*s*i*d*n.com (WP 7.0.2) F Jul 19, 2026
t*u*u*k*-*h*n*a*.com (WP 7.0.2) F Jul 18, 2026
h*r*n*m*-*e*s*t*u*s*i*d*n.com (WP 7.0.2) F Jul 18, 2026