WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: responsive-cookie-banner (Used by 54 domains)

Security snapshot

Across 54 responsive-cookie-banner WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 2% Grade B 2% Grade C 2% Grade D 4% Grade F 91%
Fail the header check (F)91%vs 82.5% avg
Leak usernames31%vs 38.5% avg
Expose a sensitive file3.7%vs 1.8% avg
Use HTTPS96%vs 96.2% avg

What stands out

TLDWP currently associates 54 indexed WordPress sites with responsive-cookie-banner, equivalent to 0% of the current WordPress dataset.

The largest measured difference is header-grade F: 90.7% versus 82.5% overall (+8.2 percentage points).

Username enumeration is 31.5% vs 38.5% overall (-7 pp); Sensitive-file exposure is 3.7% vs 1.8% overall (+1.9 pp); HTTPS adoption is 96.3% vs 96.2% overall (+0.1 pp).

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

responsive-cookie-banner 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
t*o*o*a*c*e*g*o.com (WP 5.3.2) F Sep 7, 2026
d*t*h*n*t*h*u*i*g.com (WP 5.2.2) F Sep 7, 2026
d*i*h*a*d*a*o.com (WP 5.4.2) F Sep 4, 2026
z*n*r*m*l*i*t*e*m*d*z*n.com F Sep 2, 2026
z*n*r*m*k*e*n*i*r*e*i*i*.com F Sep 2, 2026
l*l*k*r*i*r*s*r*t*g*e*.de (WP 6.9.7) F Sep 2, 2026
s*y*a*k*a*p*n*a.com (WP 5.7.17) F Sep 1, 2026
s*y*a*k*n*m*l*e*s*.com (WP 5.7.17) F Sep 1, 2026
t*t*l*o*t*a*l*e*g*e*.com (WP 7.1) F Sep 1, 2026
o*y*s*u*3*.com (WP 7.1) F Sep 1, 2026
h*p*r*s*a.fr (WP 6.8.8) F Sep 1, 2026
z*n*r*m*k*e*n*i*r*e*i*i*.de F Aug 31, 2026
n*t*l*a*v*n*e*i*t*.com (WP 6.7.7) F Aug 27, 2026
e*p*j*r*j*c*.com (WP 6.5.10) F Aug 26, 2026
c*i*k*a*k*n*.it (WP 5.3.2) F Aug 24, 2026
b*i*-*o*s*r*c*i*n*.com (WP 6.8.8) F Aug 22, 2026
a*r*o*t*a*k*n*m*l*e*s*.com (WP 5.4.2) F Aug 22, 2026
i*m*r*i*y.eu (WP 4.9.26) F Aug 22, 2026
l*m*h*l*e*.com (WP 6.3) F Aug 20, 2026
i*d*r*i*c*s.com (WP 5.4.21) F Aug 20, 2026
l*c*q*i*r*e.com D Aug 19, 2026
f*l*x*c*o*z.de (WP 7.0.4) F Aug 19, 2026
p*r*o*a*r.com (WP 5.3.2) F Aug 18, 2026
p*r*i*g*i*a*o*a*p*n*a.com (WP 5.4.2) F Aug 18, 2026
p*r*i*g*l*w*o*t.com (WP 5.4.2) F Aug 18, 2026
a*r*p*r*o*a*c*e*g*l*w*o*t.com (WP 5.4.2) F Aug 17, 2026
a*r*p*r*o*p*r*h*g*i*-*a*p*n*a.com (WP 5.4.2) F Aug 17, 2026
d*b*o*n*k*c*o*t*e.com (WP 7.0.4) F Aug 17, 2026
m*d*r*-*o*t*g*l.com (WP 7.0.4) F Aug 16, 2026
f*l*x*c*o*z.com (WP 7.0.3) F Aug 9, 2026
a*e*c*r*a*i*n.com (WP 6.0.12) F Aug 5, 2026
h*r*e*m*l*z*o.it (WP 5.8.13) F Aug 5, 2026
b*e*l*-*n*o*s*u.com F Aug 1, 2026
i*n*t.xyz F Jul 30, 2026
c*r*l*n*y*g*a*t*e*t*m*.com (WP 7.0.2) F Jul 30, 2026
t*a*s*t*o*-*u*e*i*u*-*l*s.fr (WP 4.2.10) F Jul 29, 2026
n*w*-*i*s*o.eu (WP 5.1.19) F Jul 28, 2026
1*t*p.to (WP 6.7.5) F Jul 27, 2026
t*t*c*r*i*o.com (WP 7.0.2) F Jul 27, 2026
r*t*l*f*i*t*.com (WP 6.7.5) F Jul 27, 2026
d*k*-*a*t*r*.com (WP 6.9.5) F Jul 26, 2026
a*l*c*u*u*m.fr (WP 7.0.2) D Jul 26, 2026
s*y*a*k*a*p*n*a.net (WP 5.7.15) F Jul 25, 2026
s*y*a*k*n*m*l*e*s*.net (WP 5.7.15) F Jul 25, 2026
f*r*t*i*e*t.com F Jul 25, 2026
s*y*a*k*a*p*n*a.it (WP 5.7.15) F Jul 24, 2026
v*t*p*z*a*.com F Jul 23, 2026
v*t*s*e*i*l.com F Jul 23, 2026
s*c*l*-*t*l*e.com (WP 6.9.5) F Jul 21, 2026
o*b*a*s*p*l*e*.com A Jul 20, 2026
o*b*a*c*r*s*r*i*e*.com C Jul 20, 2026
o*b*a*.com B Jul 20, 2026
p*r*h*g*i*o*c*s*.it (WP 5.4.2) F Jul 20, 2026
m*i*i*-*e*s*.fr (WP 6.9.4) F Jul 19, 2026