WordPress maintenance or security needs? Reach out!
TLDWP

Theme: logistic-transport (Used by 53 domains)

Security snapshot

Across 53 logistic-transport 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.6% avg
Leak usernames60%vs 38.6% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS96%vs 96.3% avg

What stands out

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

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

Header-grade F is 96.2% vs 82.6% overall (+13.6 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp); HTTPS adoption is 96.2% vs 96.3% overall (-0.1 pp).

These are observational associations among sites where TLDWP detected logistic-transport, 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 45
.co.za 2
.hu 1
.ro 1
.de 1
.fr 1
.org 1

Logistic Transport

๐Ÿ‘ค Themescaliber ๐Ÿ”— Theme Homepage

Logistics Transport is a robust, professional, and versatile theme designed for transportation companies, packers and movers, logistics services, shipping firms, heavy equipment transport, courier and delivery agencies, transport insurance providers, cargo hubs, freight service providers, warehouses, postal services, home shifters, contractors, and multipurpose logistics businesses.โ€ฆ

DomainVersionExposuresHeadersLast Checked
f*m*u*t*a*s*o*t.com (WP 7.1) 1.6.9· 100% conf. F Sep 10, 2026
x*d*l*c*3*0.com (WP 5.7.17) 1.0.8· 100% conf. F Sep 9, 2026
f*e*h*r*i*h*c*n*d*.com (WP 7.1) 1.6.9· 100% conf. F Sep 9, 2026
h*l*o*a*k*g*j*.com (WP 6.6.7) F Sep 5, 2026
m*x*o*e*o*i*t*c*.com (WP 7.1) F Sep 5, 2026
e*g*e*r*s*e*p*o*a*i*n*.com (WP 6.8.8) F Sep 5, 2026
f*e*g*t*a*e*o*i*t*c*.c*.za (WP 7.1) F Sep 4, 2026
m*f*l.c*.za (WP 7.1) F Sep 4, 2026
r*b*c*a*c*f*e*h*u*e.com (WP 7.0.4) F Sep 4, 2026
e*c*r*o*a*i*.com (WP 7.1) F Sep 2, 2026
e*o*d*o*r*.c*m.br (WP 5.0.19) F Sep 1, 2026
h*g*e*t*w*r*d*i*e.com F Aug 28, 2026
s*m*e*d*g*e*.fr (WP 7.1) F Aug 27, 2026
a*b*r*a*e*t*r*r*s*s.com (WP 7.1) F Aug 25, 2026
a*c*0*1.org (WP 6.2.3) F Aug 24, 2026
h*r*c*k*n*-*l*g.de (WP 6.9) F Aug 24, 2026
s*f*k*.com (WP 7.1) F Aug 23, 2026
p*l*h*p*i*g.com (WP 6.9.7) F Aug 22, 2026
2*c*d*n*s*i*p*n*.com (WP 7.0.4) F Aug 22, 2026
s*r*p*a*r*m*v*l*a*c*u*e*.com (WP 7.0.4) F Aug 21, 2026
t*x*t*n*k*k.com (WP 7.1) D Aug 20, 2026
d*n*m*c*u*r*m*c*r*.com (WP 7.0.4) F Aug 19, 2026
m*d*n*e*c*r*o*r*v*l.com (WP 7.0.4) F Aug 17, 2026
s*n*a*e*v*c*-*u*o.com (WP 7.0.4) F Aug 16, 2026
u*a*i*l*r*o*i*t*k.com D Aug 16, 2026
j*-*l*v*n*s*l*t*o*s.com (WP 6.5.3) F Aug 16, 2026
g*e*i*y*t.com (WP 6.6.7) F Aug 15, 2026
n*v*a*1*p*.com (WP 7.0.4) F Aug 15, 2026
s*m*e*d*g*e*.com (WP 7.0.4) F Aug 14, 2026
s*m*d*r*m*j*l*g*s*i*.com (WP 7.0.4) F Aug 14, 2026
w*s*j*v*-*x*o*t.com (WP 6.9.4) F Aug 14, 2026
b*d*e*v*c*s*t*.com (WP 7.0.2) F Aug 1, 2026
a*i*m*l*g*s*i*s.com (WP 5.4.2) F Aug 1, 2026
a*w*s*u*i.com (WP 7.0.2) F Jul 29, 2026
t*u*o*s*e*l*r*a*d.ro F Jul 29, 2026
c*r*a*y*r*n*p*r*e*.com (WP 6.2.2) F Jul 29, 2026
t*a*r*-*i*o*i.com (WP 5.9.13) F Jul 29, 2026
p*i*e*a*t*o*r*e*.com (WP 7.0.2) F Jul 29, 2026
t*a*r*c*o*i*t*c*.com F Jul 29, 2026
f*o*z*n*a*.com (WP 7.0.2) F Jul 28, 2026
r*m*o*r*i*h*.com (WP 7.0.2) F Jul 27, 2026
i*t*l*i*o*i*t*c*.com (WP 7.0.2) F Jul 25, 2026
l*c*s*n*d*l*r*o.com (WP 7.0.2) F Jul 25, 2026
r*s*a*a*a.com (WP 7.0.2) F Jul 25, 2026
g*a*e*n*u*a*c*g*o*p.com F Jul 25, 2026
m*f*-*a*.com (WP 7.0.2) F Jul 25, 2026
v*t*p*t*l*.com F Jul 23, 2026
o*d*p*e*s.com (WP 6.9.5) F Jul 22, 2026
m*l*n*.com (WP 7.0.2) F Jul 22, 2026
n*i*e*y*a*i*o*t*z*e*e*.hu (WP 7.0.2) F Jul 21, 2026
u*i*e*e*p*d*t*n*.com (WP 5.2.21) F Jul 20, 2026
d*l*i*o*e*a*k*r*m*v*r*.com F Jul 20, 2026
h*b*i*e*m.com (WP 6.9.1) F Jul 19, 2026