Security report for flowers24.lv
FLOWERS24 LTD · Retail · Latvia
High risk. 13 critical or high findings in GDPR compliance, Network security and 3 other checks.
46/100
Risk levelHigh
Flowers24.lv is a small e-commerce business specializing in flower and teddy bear sales with delivery services primarily targeting the Latvian market, especially Riga. The website is built on WordPress with WooCommerce, leveraging popular plugins and integrations for e-commerce functionality and marketing. The company presents clear contact information and maintains a presence on multiple social media platforms, enhancing customer engagement. The site includes privacy and cookie policies with consent mechanisms, indicating awareness of GDPR compliance. Technically, the site is hosted on SiteGround and uses modern web technologies, but lacks some security headers that could improve its security posture. The absence of WHOIS data limits domain legitimacy verification, but the website content and business information appear consistent and professional. Overall, the site offers a good user experience with clear navigation and product presentation, suitable for its target audience.
Scanned
NIS2 and GDPR posture
- NIS2 posture
- 2/ 100 · Critical
- GDPR posture
- 48/ 100 · High
- Checks completed
- 7of 7
Indicative only: based on publicly visible signals, not a certification or legal assessment. NIS2 signals relate to Article 21 of Directive (EU) 2022/2555; GDPR signals to Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive.
Priority findings
13 findings rated critical or high. Fix these first.
GDPR compliance
These are the privacy signals visitors and data protection authorities look for under GDPR.
- Critical
EU business without adequate privacy measures
EU businesses are subject to strict GDPR requirements
What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures
- High
No Cookie Policy found
GDPR requires clear information about cookie usage
What to do: Add a dedicated cookie policy explaining cookie usage and purposes
- Critical
Network security
Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.
- Critical
Critical Service Exposed: PostgreSQL
Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server
What to do: Immediately restrict access to PostgreSQL using firewall or VPN
- NIS2 21(2)(e)
- IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
- NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
- NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
High-Risk Service Exposed: FTP
Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer
What to do: Consider restricting access to FTP or implementing strong authentication
- NIS2 21(2)(e)
- IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
- NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
- NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
Security headers
Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.
- High
Missing Strict-Transport-Security header
Forces HTTPS connections
What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"
- CWE-319
- OWASP A04:2025
- ASVS V3.4.1
- RFC 6797 §6.1.1
- Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: hsts_min_age 63072000
- NIS2 21(2)(h)
- IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
- NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
- High
Missing X-Frame-Options header
Prevents clickjacking attacks
What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"
- CWE-1021
- OWASP A06:2025
- CAPEC-103
- ASVS V3.4.6
- OWASP Secure Headers: OWASP Secure Headers Project recommends X-Frame-Options: deny
- RFC 7034
- High
Missing Content-Security-Policy header
Controls resources the browser is allowed to load
What to do: Implement a Content-Security-Policy appropriate for your application
- ASVS V3.4.3
- OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching flowers24.lv
This scan found 34 issues across 7 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.
Daily monitoring
Recommended€25per month
- TLS certificates and expiry
- DNS records
- SPF, DKIM and DMARC
- Security headers
- GDPR and NIS2 posture
- Exposed services
- Third-party trackers
- Risk score drift
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly. Cancel anytime. The full timeline opens with your unlock code.
Full report
€39.90one-time
- The complete analysis as a PDF you can cite
- Email delivery with an unlock code
- Lifetime access to this report
Prices incl. 21% VAT. Payments by EveryPay; sold by SEQ SIA, Latvia.
Results by check
Each check with its score, findings and the evidence it collected.
Technical appendix
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Business context
Business profile
Security posture
Recommendations
- Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy.
- Enable HTTP Strict Transport Security (HSTS) to enforce HTTPS connections.
- Regularly update WordPress core, themes, and plugins to patch known vulnerabilities.
- Add a dedicated security or incident response page with contact information for reporting issues.
- Enhance privacy policy details to explicitly cover GDPR compliance and data retention policies.
Contact details published on the site
- Addresses
- Legal name
- FLOWERS24 LTD
- Registration number
- 11215737
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- FLOWERS24 LTD
- Description
- Flowers24.lv is an e-commerce website specializing in the sale and delivery of flowers and teddy bears, primarily targeting customers in Riga and surrounding areas. The site offers various flower categories including roses, tulips, peonies, and gift items like teddy bears in multiple sizes.
- Key services
- Flower sales, Teddy bear sales, Delivery services
- Content quality
- good
- Branding
- consistent
Technology
- Stack
- WordPress, WooCommerce, PHP, jQuery, Google Maps API, Slider Revolution, KingComposer, YITH WooCommerce Wishlist, WooCommerce Payments, Jetpack
- Frameworks
- WooCommerce, WordPress
- Platforms
- WordPress CMS
- Performance
- moderate
- Mobile
- good
- Accessibility
- basic
- SEO
- good
Security
- Observed score
- 65/100
- Good practices seen
- HTTPS enforced
- Secure login forms
- No exposed sensitive data in HTML
Analytics and tracking
- Services
- Google Analytics, WooCommerce Google Analytics Integration, Jetpack Stats
- Tracking level
- moderate
- Privacy compliance
- basic
Advertising
- Tracking pixels
- Facebook Pixel
- Marketing tools
- Facebook Pixel, WooCommerce Google Analytics Integration
- Transparency
- basic
Site quality
- Design
- good
- User experience
- good
- Content relevance
- good
- Navigation
- good
- Professionalism
- good
- Trustworthiness
- moderate
Key observations
- Website is a WordPress WooCommerce e-commerce site selling flowers and teddy bears.
- Content is well structured with clear navigation and product categorization.
- Contact information and social media links are prominently displayed.
- Privacy and cookie policies are present with consent mechanisms.
- No WHOIS data available due to query limit error; limits domain legitimacy verification.
- No security headers detected; opportunity to improve security posture.
- Uses common marketing and analytics tools including Facebook Pixel and Google Analytics.
- No adult or questionable content detected; safe for general audiences.
Technical notes
Notes
Standards and sources
Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR and IETF Datatracker (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
Retrieved 2026-10-24
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with flowers24.lv. Every review is verified by email and published after moderation.
Community rating
Loading reviews…