WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: direct-payments-for-woocommerce (Used by 48 domains)

Security snapshot

Across 48 direct-payments-for-woocommerce WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 0% Grade D 13% Grade F 88%
Fail the header check (F)88%vs 82.5% avg
Leak usernames29%vs 38.5% avg
Expose a sensitive file4.2%vs 1.8% avg
Use HTTPS98%vs 96.2% avg

What stands out

TLDWP currently associates 48 indexed WordPress sites with direct-payments-for-woocommerce, equivalent to 0% of the current WordPress dataset.

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

Header-grade F is 87.5% vs 82.5% overall (+5 pp); Sensitive-file exposure is 4.2% vs 1.8% overall (+2.4 pp); HTTPS adoption is 97.9% vs 96.2% overall (+1.7 pp).

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

Direct Payments for WooCommerce

๐Ÿ‘ค Digages ๐Ÿ”— Plugin Homepage

Say goodbye to traditional payment gateways that require developers, API keys, and complex KYC processes. Direct Payments for WooCommerce makes it easy for WooCommerce store owners to accept payments directly through local and global methods with zero transaction fees. Set up Direct Payments for WooCommerce within minutes and give your customers the freedom to choose their preferred payment option.โ€ฆ

Domain Exposures Headers Last Checked
w*l*l*g*i*e*.com (WP 7.1) F Sep 7, 2026
k*n*g*o*t*p*e*e*.com F Sep 6, 2026
h*m*c*o*t*r*.com (WP 7.1) F Sep 6, 2026
n*t*i*i*n*s*d*.com (WP 7.1) F Sep 5, 2026
k*f*r*s.site F Sep 5, 2026
t*y*e*o*.com (WP 6.9.7) F Sep 4, 2026
a*d*c*i*n*u*p*e*e*t*.com (WP 7.1) F Sep 4, 2026
r*a*f*o*s*n*t*d.com F Sep 3, 2026
c*l*u*e*o*e*t*u*i*g.com F Sep 1, 2026
n*o*s*f*d*i*i*g.com (WP 7.1) F Sep 1, 2026
c*i*p*a*g*m*n*.com F Aug 31, 2026
h*n*i*s*i*u*e*.com D Aug 31, 2026
c*r*n*t*t*t*.com (WP 6.9.7) F Aug 30, 2026
r*b*e*a*f*.com (WP 6.5.10) D Aug 29, 2026
9*o*a*s*r*e*.com (WP 7.1) D Aug 28, 2026
j*r*e*l*c*.com D Aug 28, 2026
i*o*c*a*.law (WP 7.1) F Aug 27, 2026
m*i*o*d*l*n*t*i*i*n.com (WP 7.1) F Aug 26, 2026
r*b*e*a*f*.org (WP 6.5.10) D Aug 26, 2026
b*n*i*g*o.com (WP 7.1) F Aug 24, 2026
l*a*a*c*o*o*a*e.com F Aug 23, 2026
w*a*m*h*t.com F Aug 21, 2026
y*u*u*e*i*w*.shop F Aug 20, 2026
m*d*g*t.com (WP 7.0.2) F Aug 20, 2026
c*i*a*o*h*t*c*a*s*s.com D Aug 20, 2026
c*a*m*e*l*r*a*e*a*l.com F Aug 20, 2026
a*i*i*y*e*n*s.com (WP 7.0.4) F Aug 20, 2026
c*m*n*-*n*o*b*l*n*e.com F Aug 19, 2026
s*v*r*u*c*t*.com (WP 7.0.4) F Aug 19, 2026
b*r*-*u*f.com F Aug 17, 2026
s*d*b*r*e*t.com (WP 7.0.2) F Aug 17, 2026
r*s*n*l*g*c*e*.net (WP 7.0.4) F Aug 17, 2026
l*-*r*w.com F Aug 16, 2026
m*d*g*t.c*.uk (WP 7.0.2) F Jul 31, 2026
p*i*o*i*l*n*z*n*i*a*.com (WP 7.0.2) F Jul 30, 2026
g*e*n*e*l*h*l*b*l.com (WP 7.0.2) F Jul 27, 2026
c*d*x*e*t*o*u*i*n.com (WP 7.0) F Jul 24, 2026
i*n*v*t*v*p*o*c*v*r*.com F Jul 24, 2026
m*b*l*r*s*d*c*o*.com (WP 7.0.2) F Jul 23, 2026
s*d*c*s*o*e.com (WP 7.0.2) F Jul 23, 2026
a*o*a*u*.com (WP 7.0.2) F Jul 23, 2026
h*-*o*e*s.com (WP 6.8.3) F Jul 23, 2026
e*i*i*p*a*e*.org F Jul 22, 2026
s*e*p*e*r*f*t.com (WP 7.0.2) F Jul 21, 2026
a*c*i*r*i*s.com F Jul 21, 2026
b*u*n*r*w.com F Jul 20, 2026
d*c*m*n*r*.com (WP 7.0.2) F Jul 19, 2026
d*c*d.com (WP 7.0.2) F Jul 19, 2026