WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: simple-pay-jp-payment (Used by 41 domains)

Security snapshot

Across 41 simple-pay-jp-payment WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 2% Grade D 2% Grade F 95%
Fail the header check (F)95%vs 82.5% avg
Leak usernames68%vs 38.5% avg
Expose a sensitive file2.4%vs 1.8% avg
Use HTTPS98%vs 96.2% avg

What stands out

TLDWP currently associates 41 indexed WordPress sites with simple-pay-jp-payment, equivalent to 0% of the current WordPress dataset.

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

Header-grade F is 95.1% vs 82.5% overall (+12.6 pp); HTTPS adoption is 97.6% vs 96.2% overall (+1.4 pp); Sensitive-file exposure is 2.4% vs 1.8% overall (+0.6 pp).

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

Simple PAY.JP Payment

πŸ‘€ koyacode πŸ”— Plugin Homepage

This plugin provides payment form by PAY.JP with simple shortcode. Note: The supported currency is only JPY so far. Example of Shortcode: [simple-payjp-payment amount=50 form-id="id-string" name='no' result-ok=" result-ng=" ] amount (mandatory*): price in JPY plan-id (mandatory*): subscription plan ID form-id (mandatory): any ID of the form name: show/hide name field (β€˜yes’ => show (default), β€˜no’ => hide) result-ok: page url to redirect after payment succeeded if you want to customize success message result-ng: pag…

Domain Version Exposures Headers Last Checked
k*-*e*-*3.a*.jp F Sep 8, 2026
k*r*s*i*.o*.jp F Sep 5, 2026
a*d*.jp (WP 5.9.16) F Sep 3, 2026
c*t*-*n*.tokyo C Aug 31, 2026
t*h*o*d*.com (WP 5.5.20) F Aug 29, 2026
w*n*.c*.jp F Aug 29, 2026
g*l*e*m*n*o*f*r*.com (WP 7.1) F Aug 28, 2026
m*m*-*e*s*i*.com F Aug 27, 2026
t*k*s*i*e*k*g*s*i*a.com F Aug 27, 2026
w*n*m*k*n.com F Aug 26, 2026
t*k*g*w*m*y*k*.com F Aug 26, 2026
j*s*-*p.com (WP 6.8.8) F Aug 26, 2026
b*d*m*k*r*-*y*.com (WP 7.1) F Aug 26, 2026
4*5*x*a*o*.com F Aug 25, 2026
s*u*a*s*1*4.com F Aug 25, 2026
c*l*r*u*k*d*o*e*s.com (WP 7.1) F Aug 24, 2026
h*d*m*r*-*k*.org F Aug 24, 2026
s*k*y*g.com F Aug 24, 2026
t*u*u*i*u*i.org (WP 6.9.7) F Aug 19, 2026
b*y*s*o*.com F Aug 19, 2026
s*r*r*s*-*k*s*k*.com (WP 5.4.21) F Aug 19, 2026
g*r*r*d*.com (WP 7.0.4) F Aug 19, 2026
d*-*a*i*y.net (WP 7.0.4) F Aug 18, 2026
c*d*0.site (WP 7.0.4) F Aug 16, 2026
g*n*i*o*y*.com F Aug 16, 2026
g*n*c*b*x.com (WP 7.0.4) F Aug 15, 2026
s*n*e*a.com F Aug 15, 2026
t*k*o*i*y.c*.jp F Aug 5, 2026
s*d*n*h*t*u.c*.jp F Aug 2, 2026
m*a*.o*.jp (WP 7.0.2) F Aug 1, 2026
e*y*u*h*d*i*a*u.net F Jul 29, 2026
g*i*h*k*.c*.jp (WP 6.4.3) F Jul 28, 2026
n*o*o*a*r*.net (WP 6.3.8) F Jul 25, 2026
t*p*.jp (WP 7.0.2) F Jul 25, 2026
j*a*.jp F Jul 23, 2026
o*e*a*p.com (WP 7.0.2) F Jul 22, 2026
n*o*a*s.org (WP 6.9.5) F Jul 22, 2026
m*s*t*e*i*m*-*u*d.com F Jul 21, 2026
m*r*n*o*o.jp D Jul 21, 2026
b*a*e*i*r*r*.jp (WP 6.8.6) F Jul 21, 2026
o*a*u*r*a*i*e*l*s.org (WP 7.0.2) F Jul 20, 2026