WordPress maintenance or security needs? Reach out!
TLDWP

Theme: business-consultant-finder (Used by 43 domains)

Security snapshot

Across 43 business-consultant-finder WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 2% Grade B 0% Grade C 0% Grade D 5% Grade F 93%
Fail the header check (F)93%vs 82.5% avg
Leak usernames37%vs 38.5% avg
Expose a sensitive file0%vs 1.8% avg
Use HTTPS98%vs 96.2% avg

What stands out

TLDWP currently associates 43 indexed WordPress sites with business-consultant-finder, equivalent to 0% of the current WordPress dataset.

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

Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp); HTTPS adoption is 97.7% vs 96.2% overall (+1.5 pp); Username enumeration is 37.2% vs 38.5% overall (-1.3 pp).

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

Where these sites live — top 7 domain endings
.com 36
.fr 2
.one 1
.id 1
.es 1

Business Consultant Finder

๐Ÿ‘ค aThemeArt ๐Ÿ”— Theme Homepage

Business-Consultant-Finder is a multi-purpose business theme with a professional, lightweight, approachable design and highly extendable. Suitable to create almost any type of website such a blog, portfolio, consulting business, startup company, finance business lawyers, mentors, professional services website and WooCommerce storefront.this Elegant Themes design gives you maximum flexibility.โ€ฆ

DomainExposuresHeadersLast Checked
a*t*y*e*.com (WP 7.1) F Sep 8, 2026
o*g*h*p*t.com (WP 7.1) F Sep 8, 2026
k*n*e*c*p*t*l.com (WP 7.1) D Sep 7, 2026
x*-*c*s*i*i*a*t*l*e*e*-*0*.com (WP 5.9.16) F Sep 2, 2026
j*y*u*e*g*g*m*n*.com (WP 7.1) F Sep 1, 2026
a*d*-*a*i.com (WP 6.8.8) F Aug 29, 2026
e*c*u*t*r*o*n*.com F Aug 29, 2026
g*p*y*r*m*o*s*s.com (WP 6.5.5) D Aug 27, 2026
f*e*h*g*d*g*t*l.c*m.au (WP 7.1) F Aug 27, 2026
b*n*c*a*h*t*p*i*g*e*o*t.com (WP 6.9.1) F Aug 27, 2026
p*e*e*t*s*f*a*c*.fr (WP 6.8.1) F Aug 25, 2026
r*c*p*o*u*.fr (WP 6.9.5) F Aug 25, 2026
c*b*r*o*i*a*p*l*o*e.com F Aug 25, 2026
c*n*i*m*o*p*r*p*.com (WP 7.1) F Aug 21, 2026
c*y*e*h*r*h*f*h*i*t.com (WP 7.1) F Aug 21, 2026
g*s*p*i*g.com (WP 6.8.8) F Aug 21, 2026
g*s*s*r*n*.com (WP 6.8.8) F Aug 20, 2026
b*t*m*n*c*a*o*r*o*n*.com (WP 7.0.4) F Aug 19, 2026
g*l*h*r*a*i*n*a*.com (WP 7.0.4) F Aug 19, 2026
d*g*t*l*o*k*p*c*.one (WP 7.0.2) F Aug 19, 2026
p*r*e*l*h*t*s.com (WP 6.8.8) F Aug 18, 2026
p*l*e*n*u*a.id (WP 7.0.4) F Aug 18, 2026
j*g*o*o.com (WP 6.9.7) F Aug 16, 2026
c*a*s*c*a*t*t*r*.com (WP 7.0.4) F Aug 16, 2026
s*n*o*e*n.com (WP 7.0.4) F Aug 15, 2026
d*t*x*v*.com (WP 7.0.4) F Aug 15, 2026
m*b*r*o*.com (WP 5.4.21) F Aug 15, 2026
d*t*n*.c*m.br (WP 7.0.4) F Aug 14, 2026
o*i*i*a*f*r*o*i*r*a*.es F Aug 3, 2026
m*n*o*i*d*a.com (WP 6.8.6) F Aug 1, 2026
a*e*e*a*e*i*t*n*e.com (WP 7.0.2) F Aug 1, 2026
i*i*n*s*m*d*l.com (WP 7.0.2) F Aug 1, 2026
w*m*n*n*i*m*t*c*.com (WP 7.0.2) F Jul 29, 2026
p*e*e*t*s*f*a*c*.com (WP 6.8.1) F Jul 28, 2026
t*e*o*s*i*u*p*t*w*y.com (WP 7.0.2) F Jul 28, 2026
v*r*u*l*o*f*e*r*a*s.com (WP 5.9.13) F Jul 26, 2026
m*c*n*u*t*r*.com (WP 7.0.2) A Jul 25, 2026
m*t*a*i*g*.com (WP 7.0.2) F Jul 25, 2026
m*s*l*a*h*m*n*t.com (WP 6.9.1) F Jul 23, 2026
a*m*t*o*g*n*r*y*o*u*i*n*.com (WP 7.0.2) F Jul 22, 2026
h*o*s*r*c*e.com (WP 6.8.6) F Jul 22, 2026
g*e*o*o*d*e*v*c*.com (WP 7.0.2) F Jul 20, 2026
m*f*e*i*g*d.com (WP 7.0.2) F Jul 18, 2026