WordPress maintenance or security needs? Reach out!
TLDWP

Theme: voyage (Used by 53 domains)

Security snapshot

Across 53 voyage WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 0% Grade B 0% Grade C 0% Grade D 4% Grade F 96%
Fail the header check (F)96%vs 82.5% avg
Leak usernames55%vs 38.5% avg
Expose a sensitive file11.3%vs 1.8% avg
Use HTTPS92%vs 96.2% avg

What stands out

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

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

Header-grade F is 96.2% vs 82.5% overall (+13.7 pp); Sensitive-file exposure is 11.3% vs 1.8% overall (+9.5 pp); HTTPS adoption is 92.5% vs 96.2% overall (-3.7 pp).

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

Where these sites live — top 8 domain endings
.com 42
.de 4
.co.uk 2
.sk 1
.eu 1
.net 1
.nl 1
.fr 1

Voyage

๐Ÿ‘ค Stephen Cui ๐Ÿ”— Theme Homepage

Voyage Theme is a flexible and responsive framework that combines a modified version of 960.gs and Twitter Bootstrap. It allows users changing layout and style using flexible and simple options: 1-, 2- or 3-column blog layout; fixed, fluid or responsive; grid width, color schemes, fonts (including Google Fonts) and many more. Voyage features 15 widget areas, 4 menu positions, 5 color schemes and 10 page templates including Featured Home, Landing Page, Full-Screen, Portfolio, Image Slider with template options.โ€ฆ

DomainVersionExposuresHeadersLast Checked
b*i*n*t*g*l*.com (WP 4.2.38) 1.4.5· 100% conf. F Sep 9, 2026
a*i*a*s*n*a*m*n*.com (WP 7.0.4) F Sep 7, 2026
k*n*s*e*c*c*e*t*o*s.com (WP 7.0.4) F Sep 7, 2026
b*i*i*h*t*r*c*i*n*.c*.uk (WP 6.0) F Sep 5, 2026
v*l*i*s*n*o*e.eu (WP 4.9.31) F Sep 5, 2026
d*l*i*d*v*c*u*.com (WP 7.1) F Sep 4, 2026
t*u*s*a*t*f*i*a.com (WP 7.0.4) F Sep 2, 2026
t*1*i*e.com (WP 3.5.2) F Sep 1, 2026
y*w*x*a*.com (WP 6.9.7) F Aug 31, 2026
y*c*n*t*d*o.com (WP 7.1) F Aug 30, 2026
y*u*d*y*u*.com (WP 7.0.4) F Aug 29, 2026
w*a*v*o*u*i.com (WP 5.9.1) D Aug 28, 2026
s*i*l*y*o*d*r.com F Aug 27, 2026
t*n*a*r*a*.com (WP 7.1) F Aug 26, 2026
3*d*s*r*c*a*t*r*e*.com (WP 6.1.5) F Aug 24, 2026
g*t*s*d*-*a*n*-*a*e*t.com (WP 7.1) F Aug 24, 2026
c*l*b*u*n*l*a*i*g.com (WP 7.0.4) F Aug 24, 2026
l*b*e*c*m*e*a*r.com (WP 7.1) F Aug 23, 2026
l*t*g*t*r*a*i*e*t*d*y.com F Aug 22, 2026
e*h*n*t*a*e*.com (WP 5.5.20) F Aug 21, 2026
s*e*z*o*f*l*.com (WP 3.8.1) F Aug 20, 2026
s*w*r*s*n*t*r*c*n*e*.com (WP 7.0.4) F Aug 19, 2026
j*m*l*g*-*l*m*r*.fr F Aug 19, 2026
g*i*i*g*l*e*t*n.com (WP 6.5.2) F Aug 18, 2026
v*c*n*e*.com F Aug 16, 2026
w*n*e*w*l.com (WP 7.0.4) F Aug 16, 2026
b*l*o*n*a*t*s*o*a*l*n*a.com (WP 3.6) F Aug 15, 2026
l*t*g*t*r*a*i*e*t*d*y.net F Aug 14, 2026
b*y*n*a*h*r.com (WP 7.0.2) F Aug 3, 2026
s*-*r*m*n*.de (WP 6.6.5) F Aug 3, 2026
c*a*p*g*e*o*l*y*a*l.com (WP 7.0.2) F Jul 31, 2026
w*i*g*t*g*t*s*h*l*.de (WP 5.3.19) F Jul 29, 2026
v*y*g*-*a*c*e.com (WP 7.0.2) F Jul 29, 2026
v*y*g*-*t*v*u*.com F Jul 29, 2026
s*d*o*a*.com (WP 4.3.1) F Jul 28, 2026
m*o*g*o*s.c*.uk F Jul 28, 2026
a*t*f*c*u*-*e*s*e*.de (WP 3.8.2) F Jul 28, 2026
n*v*r*o*k*a*k*a*a*i*n*.com D Jul 27, 2026
r*u*.nl (WP 6.9.5) F Jul 27, 2026
t*e*l*c*d*g*h*o*i*l*s.com (WP 6.0.9) F Jul 26, 2026
a*h*a*g*-*o*a*s*a*a.com (WP 3.8.2) F Jul 26, 2026
g*c*g*b*.de (WP 7.0.2) F Jul 25, 2026
r*y*n*e*c*e.com F Jul 25, 2026
d*i*n*c*n.sk (WP 4.9.10) F Jul 24, 2026
f*n*a*n*t.com (WP 6.8.3) F Jul 24, 2026
r*s*m*r*f*r*s*n*t*a*y.com (WP 6.9.4) F Jul 24, 2026
r*s*m*r*f*r*h*r*e*a*c*u*r*.com (WP 6.9.4) F Jul 24, 2026
f*g*t*o*y*u*l*f*m*v*e.com (WP 7.0.2) F Jul 23, 2026
f*g*t*y*u*l*f*m*v*e.com (WP 7.0.2) F Jul 23, 2026
m*c*h*c*w*d*e*d*y*.com (WP 4.6.29) F Jul 22, 2026
g*e*t*a*e*f*t*i*e*.com (WP 7.0.2) F Jul 20, 2026
c*a*s*a*o*r*v*e*s.com F Jul 20, 2026
b*i*i*h*a*t*a*t*o*s.com (WP 6.0) F Jul 19, 2026