WordPress maintenance or security needs? Reach out!
TLDWP

Theme: floral-lite (Used by 51 domains)

Security snapshot

Across 51 floral-lite WordPress sites indexed by TLDWP, compared to the all-WordPress average.

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

What stands out

TLDWP currently associates 51 indexed WordPress sites with floral-lite, equivalent to 0% of the current WordPress dataset.

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

HTTPS adoption is 100% vs 96.2% overall (+3.8 pp); Sensitive-file exposure is 0% vs 1.8% overall (-1.8 pp); Username enumeration is 37.3% vs 38.5% overall (-1.2 pp).

These are observational associations among sites where TLDWP detected floral-lite, 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 40
.net 5
.org 3
.ru 1
.co.uk 1
.cz 1

Floral Lite

๐Ÿ‘ค GretaThemes ๐Ÿ”— Theme Homepage

Floral is a beautiful WordPress blog theme for personal blogs. Floral has a modern, clean and elegant look and lots of customization for bloggers. Built on the latest technology of WordPress, Floral is lightweight, fast and optimized for all mobile phones.

DomainVersionExposuresHeadersLast Checked
s*s*m*d*a.net (WP 7.1) F Sep 8, 2026
k*t*k*v*a.ru (WP 6.8.2) F Sep 8, 2026
m*s*i*g*l*n*-*a*a*e.com (WP 7.1) F Sep 6, 2026
t*a*s*o*m*n*e*s.com (WP 7.1) F Sep 4, 2026
c*c*a*e*y.com (WP 7.1) F Sep 3, 2026
k*a*e*a*.com (WP 7.0.4) F Sep 3, 2026
m*k*w*r*d*.org (WP 7.1) F Sep 3, 2026
r*z*r*d*.com (WP 7.1) F Sep 2, 2026
p*o*i*e*a*d*a*c*.net (WP 7.1) F Aug 31, 2026
i*o*e*a*r*n*l*t*h*r.c*.uk (WP 7.1) F Aug 29, 2026
n*k*i*h*g*n.com (WP 7.1) F Aug 28, 2026
g*h*m*m*l*s.com (WP 7.1) F Aug 28, 2026
j*s*e*i*k*a*o*t*i*.com (WP 6.7.7) F Aug 28, 2026
w*n*e*l*n*f*u*d*t*o*.com (WP 7.1) F Aug 27, 2026
c*m*u*e*-*o*s*l*i*g*1*1.com (WP 7.0.4) F Aug 27, 2026
b*t*r*a*.com (WP 7.1) F Aug 27, 2026
a*e*i*s*e*h*r*.com (WP 7.1) F Aug 26, 2026
e*o*r*j*p*n.com D Aug 26, 2026
w*c*i*a*h*r*l*.com (WP 7.1) F Aug 25, 2026
t*i*f*u*t*l*g*.com (WP 6.9.4) F Aug 23, 2026
t*i*k*n*g*r*w.com (WP 7.1) F Aug 22, 2026
s*i*h*i*g*o*e.com (WP 7.1) F Aug 20, 2026
s*y*e*o*n*s*l*g.com (WP 7.0.4) F Aug 19, 2026
v*c*n*z*k*a.cz (WP 7.0.4) F Aug 18, 2026
p*b*b*r*i*.com (WP 7.0.4) F Aug 18, 2026
b*r*b*b*o*a.com (WP 7.0.4) F Aug 18, 2026
w*s*e*d*c*d*m*.org (WP 7.0.4) F Aug 18, 2026
o*a*e*t*r*l*s.org (WP 7.0.4) F Aug 17, 2026
b*l*o*n*l*w*o*r.com (WP 7.0.4) F Aug 15, 2026
m*c*i*e*.com (WP 4.9.8) F Aug 15, 2026
c*s*a*v*e*e*.com F Aug 15, 2026
b*s*s*a*.com (WP 7.0.3) F Aug 8, 2026
r*d*r*w*s*u*i*.com (WP 7.0.2) F Aug 4, 2026
w*e*l*o*s*b*k*s.com (WP 7.0.2) F Aug 4, 2026
q*e*n*i*y*r*s*.net F Aug 4, 2026
b*o*e*m*l*.com (WP 7.0.2) F Aug 3, 2026
o*o*n*.com (WP 7.0.2) F Aug 2, 2026
t*l*r*n*e*c*o*e*.net (WP 7.0.2) F Aug 2, 2026
s*r*e*h*-*e*s*h*n.net (WP 7.0.2) F Aug 1, 2026
m*t*l*a*p.com (WP 7.0.2) F Aug 1, 2026
d*g*r*e*d*y*h*n*s.com (WP 7.0.2) F Aug 1, 2026
t*e*e*i*y*t*r*e*.com (WP 6.9.5) F Aug 1, 2026
l*r*s*v*r*s*.com (WP 6.1.1) F Jul 28, 2026
b*m*u*u*d*o*.com (WP 7.0.2) F Jul 27, 2026
k*i*e*p*u*b*n*r*n*.com (WP 7.0.2) F Jul 26, 2026
d*a*a*x*n*.com (WP 7.0.2) F Jul 25, 2026
m*c*l*p*e*e*t*m*d*u*a*a.com (WP 7.0.2) F Jul 25, 2026
w*l*o*e*o*u*3*5.com (WP 6.8.3) F Jul 23, 2026
m*c*a*l*-*e*t*n*.com (WP 4.9.26) F Jul 22, 2026
a*k*t*x*u*e.com (WP 7.0.2) F Jul 22, 2026
s*b*t*6*6*.com (WP 7.0.2) F Jul 18, 2026