WordPress maintenance or security needs? Reach out!
TLDWP

Theme: catch-base-pro (Used by 48 domains)

Security snapshot

Across 48 catch-base-pro WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 2% Grade B 2% Grade C 0% Grade D 17% Grade F 79%
Fail the header check (F)79%vs 82.5% avg
Leak usernames48%vs 38.5% avg
Expose a sensitive file6.3%vs 1.8% avg
Use HTTPS94%vs 96.2% avg

What stands out

TLDWP currently associates 48 indexed WordPress sites with catch-base-pro, equivalent to 0% of the current WordPress dataset.

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

Sensitive-file exposure is 6.3% vs 1.8% overall (+4.5 pp); Header-grade F is 79.2% vs 82.5% overall (-3.3 pp); HTTPS adoption is 93.8% vs 96.2% overall (-2.4 pp).

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

Where these sites live — top 13 domain endings
.com 21
.de 12
.org 4
.fr 2
.it 1
.se 1
.eu 1
.ch 1
.be 1
.li 1
.ru 1
.nl 1
.koeln 1

catch-base-pro Premium / Custom

This theme is not available on WordPress.org. It may be a premium theme, a custom theme, or a theme from a third-party marketplace.

DomainVersionExposuresHeadersLast Checked
s*e*m*o*t*s*o*i*t*o*.se (WP 7.1) D Sep 6, 2026
k*m*a*i*c*u*s*l*n*.com (WP 7.0.4) F Sep 6, 2026
r*d*r*o*d*n*r.com F Sep 5, 2026
n*o*t*.com (WP 6.9.7) F Sep 3, 2026
c*h*y*s*o*s*r*c*i*n.com (WP 7.1) F Sep 3, 2026
o*d*i*s*.com (WP 6.2.11) F Sep 3, 2026
s*a*d*n*v*e*-*r*u*f*h*t*n.com D Aug 31, 2026
f*s*.be (WP 7.0.4) D Aug 31, 2026
t*i*e*o*r*n.com (WP 7.1) F Aug 30, 2026
c*o*s*u*.org F Aug 30, 2026
l*c*n*o*s*.com (WP 7.1) F Aug 30, 2026
d*g*t*i*r.de (WP 7.1) F Aug 29, 2026
d*i*t*o*t*.de (WP 6.8.8) A Aug 29, 2026
q*s*i*t*r*a*i*n*l.com (WP 7.0.4) F Aug 27, 2026
q*a*i*y*i*.de F Aug 26, 2026
b*l*s*u*g*i*k*n*i*e*z.li (WP 7.0.4) D Aug 26, 2026
b*s*b*k*-*o*r*j*p*n.com (WP 5.3.23) F Aug 25, 2026
w*e*t*n*e*s*n*l*s.ch (WP 5.7) F Aug 25, 2026
t*o*a*l*r*e*m*n.com F Aug 24, 2026
n*o*t*.ru (WP 6.9.7) F Aug 23, 2026
b*l*e*e*e*a*r*c*.com (WP 6.8.8) F Aug 23, 2026
b*l*e*e*e*a*v*s*r*.com (WP 6.8.8) F Aug 23, 2026
b*e*f*s*c*p.com F Aug 22, 2026
s*v*b*e.de (WP 6.0.14) F Aug 20, 2026
p*n*c*e*l*q*i*e.com (WP 7.0.4) F Aug 19, 2026
m*t*h*a*b*r*m*n*.koeln (WP 6.6.7) F Aug 16, 2026
h*r*t*g*s*u*i*s.eu F Aug 15, 2026
f*n*a*i*n*c*m*l*o*a*t*n*.it D Aug 8, 2026
h*c*-*i*o*.de (WP 7.0.3) F Aug 8, 2026
j*r*i*d*s*e*r*s.fr F Aug 2, 2026
d*-*u*s*s*o*f*e*c*i*h*e.de (WP 5.4.19) F Aug 1, 2026
t*e*e*e*t*e*s*a*h*l*c.com (WP 7.0.2) F Aug 1, 2026
m*t*r*y*l*-*o*r*j*p*n.com (WP 5.3.21) F Jul 30, 2026
l*v*i*d*s*i*i*n*a*r*s.com (WP 7.0.2) F Jul 30, 2026
a*u*d*c*m*n*f*r*i*r.fr (WP 7.0.2) F Jul 29, 2026
m*t*t*e*-*h*r*n*e*n*e*g.de (WP 6.9.4) F Jul 29, 2026
s*f*-*a*k*n*-*r*g*a*.com (WP 6.7.5) F Jul 28, 2026
a*t*s*a*-*a*e*a*.nl (WP 6.9.5) B Jul 26, 2026
t*z*w*l*c*u*t*v*.org (WP 7.0.2) F Jul 26, 2026
a*p*k*-*o*l*a*u*a*t*r.de (WP 7.0.2) F Jul 26, 2026
m*-*o*n*c*a*s*c*.de (WP 6.9.5) D Jul 24, 2026
c*b*b*s*o*.org (WP 6.8.6) F Jul 24, 2026
b*v*h*o*2*0*e*.de (WP 7.0.2) F Jul 23, 2026
u*i*y*a*d*n*.org (WP 7.0.2) D Jul 23, 2026
h*t*l*l*s*o*c*i*u*s.com (WP 6.5.8) F Jul 22, 2026
f*u*r*r*m*e*.de (WP 7.0.2) F Jul 21, 2026
h*m*s*y*o*m*s.com (WP 6.4.8) D Jul 21, 2026
k*l*u*e*b*-*c*w*r*w*l*h*c*s*r*s*e.de F Jul 18, 2026