WordPress maintenance or security needs? Reach out!
TLDWP

Theme: vanguard (Used by 65 domains)

Security snapshot

Across 65 vanguard WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Security metrics currently cover 64 matching records in the cached metrics snapshot.

Grade A 0% Grade B 0% Grade C 5% Grade D 2% Grade F 94%
Fail the header check (F)94%vs 82.5% avg
Leak usernames42%vs 38.5% avg
Expose a sensitive file4.7%vs 1.8% avg
Use HTTPS94%vs 96.2% avg

What stands out

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

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

Username enumeration is 42.2% vs 38.5% overall (+3.7 pp); Sensitive-file exposure is 4.7% vs 1.8% overall (+2.9 pp); HTTPS adoption is 93.8% vs 96.2% overall (-2.4 pp).

These are observational associations among sites where TLDWP detected vanguard, 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 47
.nl 3
.fr 3
.org 2
.ru 1
.de 1
.it 1
.co.nz 1
.co.uk 1
.ne.jp 1
.pt 1

vanguard 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
a*t*i*r*s*a*c*.com (WP 6.9.7) 2.0.0· 100% conf. F Sep 9, 2026
a*n*i*g*e*o*t*x.com (WP 7.1) F Sep 8, 2026
h*p*f.n*.jp (WP 4.1.1) F Sep 7, 2026
k*r*k*y*l*r*a*r*y*t.com (WP 4.7.29) F Sep 7, 2026
y*t*s*r*e*n*.com (WP 7.1) F Sep 7, 2026
h*r*h*y*n*.com (WP 7.1) F Sep 7, 2026
h*m*h*l*c*e*t*i*c*b*t*r.com (WP 7.1) F Sep 6, 2026
h*m*h*l*c*e*t*.com (WP 7.1) F Sep 6, 2026
y*t*o.com (WP 6.9.7) F Sep 6, 2026
m*x*g*o*p*.com F Sep 5, 2026
v*n*u*r*g*l*e*y.com (WP 7.1) F Sep 5, 2026
u*a*s*e*p*n*.com (WP 7.0.4) F Sep 5, 2026
s*o*i*s*r*e*n*.com F Sep 3, 2026
b*o*e*s*l*.com F Sep 2, 2026
b*o*e*s*n*.com F Sep 2, 2026
t*t*l*y*e*v*c*s.com F Sep 1, 2026
g*n*u.nl (WP 6.4) C Sep 1, 2026
a*s*l*i*p*.com D Sep 1, 2026
c*l*g*l*a*p*a*t*c*h*l*.com F Sep 1, 2026
c*d*g*i*e*a*y*r.com F Sep 1, 2026
c*c*i*d*e*a*u*e*a*y*r.com F Aug 31, 2026
c*a*t*i*j*r*l*w*e*.com F Aug 31, 2026
v*n*u*r*g*o*p.c*.nz F Aug 31, 2026
f*g*e*l*n*.com F Aug 30, 2026
t*n*a*i*l*l*n.com (WP 7.1) F Aug 28, 2026
q*i*k*e*r*p*r*s.com F Aug 28, 2026
b*l*y*r*f*o*.com F Aug 26, 2026
g*o*p*-*o*u*i*.com (WP 4.7.25) F Aug 23, 2026
s*e*t*a*e*e*g*n*e*i*g.com (WP 7.0.4) F Aug 23, 2026
s*e*t*a*e*-*u*v*y*n*.com (WP 7.0.4) F Aug 23, 2026
s*e*t*a*e*-*n*i*e*r*n*.com (WP 7.0.4) F Aug 23, 2026
b*a*e*d*m*a*d*m*n.com (WP 7.0.4) F Aug 21, 2026
s*n*o*m*i*h*g*n.com F Aug 20, 2026
v*n*u*r*t*c*n*l*g*s*s.com (WP 7.0.4) F Aug 18, 2026
v*n*u*r*m*d*r*u*.com (WP 7.0.3) F Aug 18, 2026
v*n*u*r*g*a*i*.com (WP 7.0.4) F Aug 18, 2026
v*n*u*r*f*s*i*a*.com F Aug 18, 2026
v*n*u*r*c*n.com F Aug 18, 2026
s*k*s*o*e*e*v*c*s.com F Aug 18, 2026
i*w*v*n*u*e.org F Aug 17, 2026
s*n*e*a*o*n*c*i*n*.com F Aug 15, 2026
s*m*n*e*e*t*r.com F Aug 15, 2026
p*d*x.n*t.pl (WP 7.0.3) F Aug 7, 2026
a*a*g*r*-*p*.ru (WP 7.0.3) F Aug 7, 2026
p*d*x.c*m.pl (WP 7.0.2) F Aug 5, 2026
e*g.nl (WP 6.4) C Aug 5, 2026
t*e*u*h*n*e.com F Jul 31, 2026
m*d*z*n*t*n*s*a.com F Jul 31, 2026
t*e*i*t*n*r*u*.com F Jul 31, 2026
n*c*e*e*t*s*n*.com F Jul 30, 2026
l*n*l*y*e*n*s.com F Jul 27, 2026
a*v*.fr F Jul 26, 2026
s*o*t*x*c*t*v*s*a*c*.com F Jul 25, 2026
g*s*o*g*o*t*.com F Jul 25, 2026
p*i*i*p*n*s*a*a*s*c*e*y.com F Jul 24, 2026
f*o*4*o*d.fr F Jul 24, 2026
c*b*n*t*a*g*a*d.com (WP 6.9.1) F Jul 24, 2026
p*d*s*g*.pt F Jul 22, 2026
v*n*u*r*m*n*s*r*e*.org (WP 6.8.6) F Jul 22, 2026
e*g*n*u*s*r*j*c*e*.nl (WP 6.4) C Jul 21, 2026
o*o*s*e*a*i*e.fr F Jul 20, 2026
c*n*o*z*o*i*e*.it F Jul 19, 2026
r*b*r*h.de F Jul 19, 2026
u*l*p.c*.uk F Jul 18, 2026