WordPress maintenance or security needs? Reach out!
TLDWP

Theme: sunderland (Used by 61 domains)

Security snapshot

Across 61 sunderland WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 3% Grade D 11% Grade F 85%
Fail the header check (F)85%vs 82.5% avg
Leak usernames62%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS98%vs 96.2% avg

What stands out

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

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

Header-grade F is 85.2% vs 82.5% overall (+2.7 pp); HTTPS adoption is 98.4% vs 96.2% overall (+2.2 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp).

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

Where these sites live — top 6 domain endings
.com 56
.nl 1
.blog 1
.co.uk 1
.co 1
.ps 1

Sunderland

๐Ÿ‘ค Automattic ๐Ÿ”— Theme Homepage

Sunderland is a simple theme that supports full-site editing. It comes with a set of minimal templates and design settings that can be manipulated through Global Styles. Use it to build something beautiful.

DomainVersionExposuresHeadersLast Checked
h*n*o*l*b*a*y.com (WP 7.1) 1.0.5· 100% conf. B Sep 9, 2026
k*l*a*m*s*.com (WP 7.1) 1.0.5· 100% conf. F Sep 9, 2026
d*v*a*i*n*n*.com (WP 6.5.10) F Sep 7, 2026
m*t*i*u*o*s.com (WP 7.0.4) F Sep 4, 2026
b*a*k*o*k*u*k.com (WP 7.0.2) F Aug 31, 2026
c*l*h*b*k*s*.com F Aug 31, 2026
n*h*-*a.com F Aug 30, 2026
n*t*a*a*a*b*.com F Aug 28, 2026
n*t*a*z*l*.com (WP 7.1) F Aug 28, 2026
j*n*i*e*l*v*w*i*e*.com F Aug 27, 2026
m*k*n*y*i*l*a*s*n.com F Aug 26, 2026
p*n*a*p*e*l*n*t.co F Aug 25, 2026
w*s*s*d*i*p*a*t*e*t*s*.com F Aug 24, 2026
s*e*t*r*a*d*e*r*s.com (WP 7.1) F Aug 23, 2026
t*a*o*a*a.com (WP 7.0.4) F Aug 22, 2026
s*a*l*w*u*d*r*a*e*.com F Aug 22, 2026
l*o*i*o*u*i*.com F Aug 21, 2026
m*a*h*e*i*.com D Aug 20, 2026
s*v*n*i*s*o*l*r*i*c*m*v*e.com (WP 7.0.4) F Aug 17, 2026
f*x*-*r*g*n.com (WP 7.0.4) F Aug 17, 2026
b*r*t*o*o*s*.com F Aug 17, 2026
g*r*a*f*n*g*o*s.com (WP 7.0.4) F Aug 17, 2026
c*t*w*a*i*g*a*l*s.com (WP 7.0.4) F Aug 15, 2026
u*a*h*b*n*.com F Aug 15, 2026
n*t*.blog (WP 7.0.3) C Aug 10, 2026
t*e*i*i*e*k.com (WP 7.0.3) F Aug 8, 2026
b*a*b*n*.c*.uk F Aug 7, 2026
r*o*o*e*d*o*p*x.com F Aug 7, 2026
t*e*r*n*c*r*a*d.com (WP 6.8.6) F Aug 1, 2026
f*e*t*g*o*f*n*s.com D Aug 1, 2026
n*c*l*a*q*a*.com F Jul 31, 2026
s*r*s*v*s.com F Jul 30, 2026
m*r*a*b*i*e*.com F Jul 30, 2026
c*r*o*c*e.com F Jul 29, 2026
v*t*r*l*e*a*q*i*e*o.com (WP 6.7.5) F Jul 28, 2026
m*a*t*n*e*c*u*t*r.nl F Jul 26, 2026
m*a*t*n*e*c*u*t*r.com F Jul 26, 2026
p*n*a*p*e*l*n*t*e*i*.com F Jul 26, 2026
t*e*r*n*b*.com (WP 7.0.2) C Jul 26, 2026
c*m*f*n*.com F Jul 26, 2026
i*t*g*a*i*.com (WP 7.0.2) D Jul 25, 2026
t*e*e*e*i*l*-*r*w.com (WP 7.0.2) F Jul 25, 2026
c*u*k*e*k*l*j*y.com (WP 7.0.2) F Jul 25, 2026
p*o*b*r*a.com F Jul 24, 2026
p*a*t*s*i*.com F Jul 24, 2026
s*e*h*n*j*n*s.com F Jul 23, 2026
i*g*i*g*i*f*n*u*i*.com F Jul 23, 2026
m*n*s*7.com F Jul 23, 2026
b*c*r*s*u*i*.com (WP 6.6.5) F Jul 23, 2026
h*u*e*f*t*s*h*.com (WP 7.0.2) F Jul 23, 2026
w*l*b*i*g*l*v*t*.com (WP 7.0.2) F Jul 23, 2026
l*n*t*a*.com (WP 7.0.2) F Jul 22, 2026
m*c*e*u*i*.com F Jul 22, 2026
l*k*g*g*.com F Jul 22, 2026
s*a*a*i*t*c*a*y.com (WP 7.0.2) F Jul 22, 2026
c*a*l*t*u*p*t.com F Jul 20, 2026
f*s*f*s*o*d*r*.com (WP 7.0.2) D Jul 20, 2026
s*o*t*d*n*v*.com F Jul 20, 2026
b*h.ps (WP 7.0.2) F Jul 20, 2026
d*e*b*a*k*a*i*.com D Jul 19, 2026
b*o*c*e*c*n*u*t*n*.com (WP 6.6.2) D Jul 19, 2026