WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: custom-cookie-consent (Used by 122 domains)

Security snapshot

Across 122 custom-cookie-consent WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 4% Grade B 0% Grade C 7% Grade D 2% Grade F 86%
Fail the header check (F)86%vs 82.5% avg
Leak usernames10%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS97%vs 96.2% avg

What stands out

TLDWP currently associates 122 indexed WordPress sites with custom-cookie-consent, equivalent to 0% of the current WordPress dataset.

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

Header-grade F is 86.1% vs 82.5% overall (+3.6 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp); HTTPS adoption is 96.7% vs 96.2% overall (+0.5 pp).

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

custom-cookie-consent 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
o*e*i*m*c*n*o*a*e*.com (WP 6.8.3) F Sep 9, 2026
h*l*s*o*o*e*c*r*s*d*n*e*.com (WP 6.8.3) F Sep 8, 2026
o*e*a*h*r*o*r*o*d*s*i*m*.com (WP 6.8.3) F Sep 8, 2026
o*d*b*y*a*b*r*o*d*s.com (WP 6.8.3) F Sep 8, 2026
t*u*p*o*l*w*o*s*l*s.com (WP 6.8.3) F Sep 8, 2026
w*e*i*e*c*s*u*h*e*c*.com (WP 6.8.3) F Sep 8, 2026
3*p*o*o.ru (WP 6.6.7) F Sep 7, 2026
s*l*m*r*e*c*c*n*o*.com (WP 6.8.3) F Sep 7, 2026
r*s*d*n*e*s*n*y*s*e*b*a*h.com (WP 6.8.3) F Sep 6, 2026
r*g*l*a*i*m*c*n*o*.com (WP 6.8.3) F Sep 6, 2026
r*n*i*s*n*e*e*s*.com C Sep 5, 2026
a*r*t*e*i*e*c*s*i*g*r*s*a*d.com (WP 6.8.3) F Sep 4, 2026
t*r*b*r*y*i*l*g*c*n*o*.com (WP 6.8.3) F Sep 4, 2026
b*c*b*a*h*e*i*e*c*s.com (WP 6.8.3) F Sep 4, 2026
l*m*m*s*o*e*t*d*.pe (WP 6.9.4) A Sep 4, 2026
p*x.c*m.pe A Sep 4, 2026
l*m*e*p*e*a.pe A Sep 4, 2026
k*r*k*y*n.ru D Sep 3, 2026
b*g*d*a*a*e*c*.ru D Sep 3, 2026
d*n*a*-*l*n*o.ru F Sep 3, 2026
o*s*r*s*d*c*n*o*.com (WP 6.8.3) F Sep 3, 2026
a*q*a*i*a*a*s*o*s*i*m*.com (WP 6.8.3) F Sep 2, 2026
a*q*a*i*a*s*a*e*m*a*i.com (WP 6.8.3) F Sep 2, 2026
m*r*u*s*o*d*s*i*m*.com (WP 6.8.3) F Sep 2, 2026
n*r*h*a*v*l*a*e*r*s*d*n*e*.com (WP 6.8.3) F Sep 1, 2026
e*i*-*o*e.com F Sep 1, 2026
t*n*u*e*m*o*d*s*i*m*.com (WP 6.8.3) F Sep 1, 2026
o*e*n*a*m*h*l*y*o*d*o*d*s.com (WP 6.8.3) F Aug 31, 2026
o*e*n*a*i*e*a*h*c*u*f*.com (WP 6.8.3) F Aug 31, 2026
o*e*n*o*r*o*d*s*i*m*.com (WP 6.8.3) F Aug 31, 2026
m*r*n*p*l*s*o*d*s*i*m*.com (WP 6.8.3) F Aug 31, 2026
l*n*y*.nl (WP 6.7.7) F Aug 31, 2026
m*r*n*b*u*m*a*i*a*e*.com (WP 6.8.3) F Aug 31, 2026
w*o*t*b*a*h*o*d*s*i*m*.com (WP 6.8.3) F Aug 31, 2026
y*u*b*a*h*l*b.com (WP 6.8.3) F Aug 29, 2026
l*v*p*r*u*t*w*r*.com (WP 6.8.3) F Aug 28, 2026
t*i*r*.com (WP 6.8.3) D Aug 28, 2026
5*b*s*a*n*b*v*.com (WP 6.8.3) F Aug 26, 2026
5*0*r*c*e*l*v*.com (WP 6.8.3) F Aug 26, 2026
l*m*e*p*e*a.com A Aug 25, 2026
e*l*v*n*i*m*c*n*o*.com (WP 6.8.3) F Aug 25, 2026
4*0*u*n*i*l*s*o*d*s.com (WP 6.8.3) F Aug 25, 2026
p*m*a*o*e*c*r*s*d*n*e*.com (WP 6.8.3) F Aug 25, 2026
p*i*t*f*v*n*u*a*o*d*s.com (WP 6.8.3) F Aug 24, 2026
3*3*a*e*t*r*.com (WP 6.8.3) F Aug 24, 2026
g*o*e*s*e*e*i*e*c*s.com (WP 6.8.3) F Aug 23, 2026
g*o*e*o*d*s*i*m*.com (WP 6.8.3) F Aug 23, 2026
b*l*a*a*e*v*n*u*a*o*d*s.com (WP 6.8.3) F Aug 23, 2026
c*n*i*u*m*o*d*s*i*m*.com (WP 6.8.3) F Aug 23, 2026
w*s*b*r*s*d*n*e*.com (WP 6.8.3) F Aug 22, 2026
j*d*s*e*i*e*c*s*i*m*.com (WP 6.8.3) F Aug 22, 2026
j*d*s*g*a*u*e*o*d*s*i*m*.com (WP 6.8.3) F Aug 22, 2026
j*d*r*s*d*n*e*m*a*i.com (WP 6.8.3) F Aug 22, 2026
j*d*c*n*o*m*a*i.com (WP 6.8.3) F Aug 22, 2026
g*d*o*r*m.com F Aug 22, 2026
p*a*a*r*c*e*l*o*d*.com (WP 6.8.3) F Aug 22, 2026
e*h*a*e*t*r*c*n*o*.com (WP 6.8.3) F Aug 21, 2026
s*r*c*u*c*n*o*m*a*i.com (WP 6.8.3) F Aug 21, 2026
v*r*i*h*l.com F Aug 21, 2026
c*n*o*a*c*.com (WP 6.8.3) F Aug 21, 2026
b*a*h*a*k*a*l*n*a*e*o*d*s.com (WP 6.8.3) F Aug 20, 2026
p*r*g*n*o*d*s*i*m*.com (WP 6.8.3) F Aug 20, 2026
s*n*y*s*e*b*a*h*e*i*e*c*s.com (WP 6.8.3) F Aug 19, 2026
b*s*-*h*i*e*s*b.ru F Aug 18, 2026
s*r*p*.com F Aug 17, 2026
w*-*e*i*e*c*s*i*m*.com (WP 6.8.3) F Aug 15, 2026
t*a*v*i*o*.ru (WP 6.9.1) F Aug 6, 2026
c*u*a*i.ru (WP 7.0) F Aug 4, 2026
m*c*o.ca C Aug 3, 2026
e*k*i*o.ru F Aug 2, 2026
b*c*a*a*m*a*i*a*e*.com (WP 6.8.3) F Aug 1, 2026
p*i*t*e*c*.ru (WP 7.0.2) C Aug 1, 2026
m*f*s*r*e*v*c*.com (WP 6.8.2) F Aug 1, 2026
t*e*e*i*e*c*s*t*i*.com (WP 6.8.3) F Aug 1, 2026
n*v*g*t*r*9.ru F Jul 31, 2026
p*l*z*o*e*s*l*i*h*r*s*a*d*o*d*s.com (WP 6.8.3) F Jul 31, 2026
i*o*v*l*a*t*c*n*o.com (WP 6.8.3) F Jul 31, 2026
i*o*c*n*o*i*m*.com (WP 6.8.3) F Jul 31, 2026
i*o*b*i*k*l*c*n*o*m*a*i.com (WP 6.8.3) F Jul 31, 2026
c*s*m*r*o*d*s*o*p*n*.com (WP 6.8.3) F Jul 30, 2026
u*t*w*m*r*n*c*n*o*.com (WP 6.8.3) F Jul 30, 2026
s*l*w*l*-*o*e*s.com (WP 6.8.2) F Jul 30, 2026
h*d*b*a*h*o*d*s.com (WP 6.8.3) F Jul 30, 2026
p*i*e*o*d*s*v*n*u*a.com (WP 6.8.3) F Jul 30, 2026
a*b*r*e*o*d*s.com (WP 6.8.3) F Jul 29, 2026
m*r*s*d*n*e*-*i*m*.com (WP 6.8.3) F Jul 29, 2026
1*0*m*s*u*c*n*o*a*e*.com (WP 6.8.3) F Jul 29, 2026
s*g*r*s*d*n*e*f*.com (WP 6.8.3) F Jul 29, 2026
a*l*s*r*p*r*y*m*r*v*m*n*s.com (WP 6.7.5) F Jul 29, 2026
b*s*u*.ru F Jul 28, 2026
l*s*l*s*e*i*e*c*s.com (WP 6.8.3) F Jul 28, 2026
t*p*o*g*.ru (WP 7.0) F Jul 28, 2026
d*l*a*p*o*u*t*s.com C Jul 27, 2026
s*t*o*e*c*n*o*m*a*i.com (WP 6.8.3) F Jul 26, 2026
s*r*g*s*a*h*r*o*r*o*d*s*i*m*.com (WP 6.8.3) F Jul 25, 2026
p*o*n*x*t*e*s.com (WP 6.7.5) F Jul 24, 2026
s*u*o*y.se C Jul 24, 2026
s*u*o*y.no C Jul 24, 2026
s*u*o*y.fi C Jul 24, 2026
s*u*o*y.dk C Jul 24, 2026