WordPress maintenance or security needs? Reach out!
TLDWP

Theme: brixton (Used by 54 domains)

Security snapshot

Across 54 brixton WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 2% Grade B 2% Grade C 0% Grade D 9% Grade F 87%
Fail the header check (F)87%vs 82.6% avg
Leak usernames52%vs 38.6% avg
Expose a sensitive file3.7%vs 1.8% avg
Use HTTPS98%vs 96.3% avg

What stands out

TLDWP currently associates 54 indexed WordPress sites with brixton, equivalent to 0% of the current WordPress dataset.

The largest measured difference is username enumeration: 51.9% versus 38.6% overall (+13.3 percentage points).

Header-grade F is 87% vs 82.6% overall (+4.4 pp); Sensitive-file exposure is 3.7% vs 1.8% overall (+1.9 pp); HTTPS adoption is 98.1% vs 96.3% overall (+1.8 pp).

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

Where these sites live — top 11 domain endings
.com 39
.fr 3
.pl 2
.org 2
.ca 2
.nl 1
.pt 1
.eu 1
.no 1
.de 1
.se 1

brixton 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
m*l*g*o*m*n*.fr (WP 7.0.4) 4.1· 100% conf. F Sep 10, 2026
a*e*r*k*n*o*g*r*.com (WP 7.0.4) 5.6· 100% conf. F Sep 9, 2026
k*n*e*h*u*k*n*a*l.com (WP 7.1) 5.3· 100% conf. F Sep 9, 2026
f*r*p*b*i*.com (WP 7.0.2) 5.0· 100% conf. F Sep 9, 2026
k*i*y*.com 5.6· 100% conf. D Sep 9, 2026
a*r*a*t*.ca (WP 7.0.4) F Sep 8, 2026
h*a*t*h*a*f*o*b*l*.com (WP 6.9.4) F Sep 3, 2026
j*o*d*i*l.com (WP 7.0.4) F Sep 2, 2026
j*n*r*g*r.com (WP 6.5.10) F Aug 31, 2026
l*p*r*s*e*h*u*e*x.fr (WP 6.7.7) F Aug 30, 2026
d*g*o*d*u*s.com (WP 5.2.2) F Aug 30, 2026
r*c*e*t*b*r*e*.com (WP 5.1.24) F Aug 29, 2026
r*b*e*l*a*a*i.com F Aug 29, 2026
j*d*s*e*.com (WP 4.4.33) F Aug 29, 2026
l*v*n*t*e*r*a*g*i*e.com F Aug 29, 2026
c*a*y*a*e*.com (WP 7.0.4) F Aug 28, 2026
t*l*i*g*y*h*.com (WP 7.0.4) F Aug 27, 2026
p*p*e*l*h*n*o*a*i*n*a*.org A Aug 27, 2026
c*v*r*d*r*d*e*8*8.com (WP 7.1) F Aug 27, 2026
a*e*a*d*e*m*r*e*u.com (WP 6.9.7) D Aug 26, 2026
b*s*p*o*l*g.com F Aug 26, 2026
p*n*u*n*a*s*d*a*t*k*u*.com (WP 7.1) F Aug 24, 2026
t*r*e*u*s*o*f*l*g.com (WP 7.0.4) F Aug 24, 2026
l*f*o*t*e*a*i*y.com (WP 5.2.3) D Aug 24, 2026
p*k*y*o*t*n.com (WP 5.9.16) F Aug 24, 2026
v*n*o*v*r*a*k*t.ca (WP 7.1) F Aug 23, 2026
i*d*n*s*a*e*t*u*i*.com (WP 4.4.4) F Aug 19, 2026
b*s*l*d*s*a.com (WP 6.9.7) F Aug 18, 2026
i*b*u*d*a*k*t*n*t*d*y.com (WP 7.0.4) D Aug 18, 2026
v*l*m*r*s*e*t.no (WP 7.0.4) B Aug 16, 2026
g*e*o*t*f*a*e*b*a*t*.com F Aug 15, 2026
g*e*o*t*f*a*e*.com F Aug 15, 2026
b*e*m*t*o*t.nl (WP 6.4.9) F Aug 9, 2026
c*c*m*e.pt F Aug 5, 2026
b*o*a*y*l*g.pl (WP 5.8.11) F Aug 2, 2026
a*e*b*.eu F Aug 2, 2026
t*e*e*f*t*.com (WP 7.0.2) F Aug 1, 2026
f*o*t*e*p*c*t*a*n.com F Aug 1, 2026
c*s*d*l*s*a*a*.com (WP 7.0.2) F Jul 31, 2026
i*m*c*i*d*f*i*o*c*.com (WP 6.6.5) F Jul 30, 2026
f*r*h*b*o*y.com F Jul 30, 2026
b*c*s*a*e*a*t*r*.org (WP 6.8.6) F Jul 27, 2026
m*l*y*u*h*r.com (WP 7.0.2) F Jul 27, 2026
t*a*g*y*n*v.com F Jul 25, 2026
s*o*k*o*i*.com (WP 6.8.6) F Jul 24, 2026
h*i*i*o*l*n*e.de (WP 6.9.5) F Jul 24, 2026
t*e*t*f*n*.com (WP 5.5.18) F Jul 23, 2026
s*e*b*s*l*6*.com F Jul 23, 2026
t*e*o*e*i*e*p*e*c*e*.com (WP 7.0.2) F Jul 23, 2026
a*a*p*w*a*a.pl (WP 6.7.2) F Jul 22, 2026
h*p*4*u*t*n*k*d*.com (WP 6.8.6) F Jul 21, 2026
t*u*s*e*e*.fr (WP 7.0.2) F Jul 21, 2026
v*k*a*a*d*v*l*.se (WP 6.9) D Jul 20, 2026
b*u*e*c*a*u*.com (WP 5.9.13) F Jul 19, 2026