Security report for flou.cz
Technology · Czech Republic
Medium risk. 9 critical or high findings in GDPR outside view, Security headers and 3 other checks.
Flou.cz is a Czech Republic-based SaaS platform providing an intelligent information system tailored for small businesses, craftsmen, and sole proprietors (OSVČ). The platform centralizes management of offers, orders, invoices, contacts, and financial documents in a cloud environment accessible from multiple devices. Its business model focuses on subscription services with a free 30-day trial, targeting a niche market of small enterprises seeking to streamline administrative tasks. The website content is professionally presented in Czech, with clear navigation and consistent branding, supporting a trustworthy user experience. Technically, the website employs modern web technologies including Google Analytics for traffic analysis, Smartsupp Live Chat for customer support, and Google reCAPTCHA for bot protection. The site is responsive and optimized for mobile devices, though accessibility features are basic. Performance is moderate, with bundled CSS and JavaScript resources. Security best practices include HTTPS enforcement and cookie consent mechanisms, though HTTP security headers are not explicitly detected. From a security perspective, the site demonstrates a solid posture with encrypted communications and user privacy considerations. However, the absence of explicit incident response contacts and vulnerability disclosure mechanisms suggests room for improvement in transparency and readiness. The lack of WHOIS data limits domain registration trust analysis, but the professional presentation and contact information mitigate concerns. Overall, the site is low risk with good privacy compliance and business credibility. Strategically, Flou.cz should enhance its security headers, publish a security.txt file, and provide clearer incident response contacts to strengthen trust and compliance. Continued focus on accessibility and performance optimization will improve user experience and broaden market appeal.
Scanned
NIS2 and GDPR posture
- GDPR outside view
- 10/ 100 · Critical
- Checks completed
- 7of 7
NIS2 Art. 21(2)
- (a) Risk analysis and security policies: Not visible from outside
- (b) Incident handling: One indicator
- (c) Business continuity, backups and crisis management: Not visible from outside
- (d) Supply chain security: Not visible from outside
- (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
- (f) Assessing the effectiveness of security measures: Not visible from outside
- (g) Cyber hygiene and security training: Not visible from outside
- (h) Cryptography and encryption: Partly checked
- (i) HR security, access control and asset management: One indicator
- (j) Multi-factor authentication and secured communications: Not visible from outside
This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.
GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.
Priority findings
9 findings rated critical or high. Fix these first.
GDPR outside view
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 Privacy Policy found
GDPR requires a clear and accessible privacy policy
What to do: Add a comprehensive privacy policy page and link to it prominently
- GDPR Art. 12
- GDPR Art. 13
- NIST PT-5: NIST SP 800-53 Rev. 5 PT-5: Privacy Notice
- 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
- High
No Cookie Consent Banner found
GDPR requires explicit consent for non-essential cookies
What to do: Implement a cookie consent banner that appears on first visit
- GDPR Art. 7
- ePrivacy Art. 5(3)
- NIST PT-4: NIST SP 800-53 Rev. 5 PT-4: Consent
- High
Third-party services without privacy policy
Detected services: Google Analytics, Facebook
What to do: Document all third-party data sharing in your privacy policy
- 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 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 flou.cz
This scan found 23 issues across 6 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
- Security score drift
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly to your card. Cancel anytime. See sample alerts.
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. Secure checkout by Mollie; sold by SEQ SIA, Latvia.
Results by check
Each check with its score, findings and the evidence it collected.
How this score is calculated
The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.
Counted in this score
- SSL/TLS
- 72
- Security headers
- 65
- Email security
- 65
- DNS health
- 70
- Network security
- 20
- GDPR outside view
- 10
- Average
- 50
Not counted
- NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
- OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.
Findings that cap the score at 49
Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.
- The certificate is not trusted by browsers
- The website is not served over HTTPS
- A database, remote desktop, file-sharing or Telnet service is reachable from the internet
- The page loads a script from a compromised source
- The domain registration has expired
- SPF authorises every server to send mail as the domain
Partial scans
When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.
Risk levels
- Critical0–25
- High26–49
- Medium50–75
- Low76–100
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 HTTP security headers including CSP, HSTS, X-Frame-Options, and X-XSS-Protection to enhance browser security.
- Publish a security.txt file at the root domain to provide clear vulnerability disclosure and incident response contacts.
- Add explicit incident response contact information on the website, such as a security@ or abuse@ email address.
- Enhance accessibility features to meet recognized standards and improve usability for all users.
- Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Description
- Flou is an intelligent information system designed for craftsmen, sole proprietors (OSVČ), and small businesses. It centralizes management of offers, orders, invoices, and contacts in one cloud-based platform accessible anytime and anywhere.
- Key services
- Offers management, Orders and contracts, Catalog and contacts directory, Finance management including invoicing, Work reports and time tracking, Automation of reminders and recurring invoices, Multi-entity account management
- Content quality
- good
- Branding
- consistent
Technology
- Stack
- Google Analytics (gtag.js), Smartsupp Live Chat, Google reCAPTCHA, JavaScript, CSS Bundles
- Platforms
- Web (responsive design)
- Performance
- moderate
- Mobile
- good
- Accessibility
- basic
- SEO
- basic
Security
- Observed score
- 85/100
- Good practices seen
- HTTPS enforced
- Use of Google reCAPTCHA
- Cookie consent banner with management options
- No exposed sensitive data in HTML
Analytics and tracking
- Services
- Google Analytics
- Tracking level
- moderate
- Privacy practices
- good
Advertising
- Marketing tools
- Smartsupp Live Chat
- Transparency
- basic
Site quality
- Design
- good
- User experience
- good
- Content relevance
- good
- Navigation
- good
- Professionalism
- good
- Trustworthiness
- high
Key observations
- Website is fully accessible with no blocking or WAF challenges.
- Content is in Czech language targeting local small businesses and sole proprietors.
- No phone numbers or physical addresses explicitly found in the HTML content.
- Contact email is provided in footer: poradna@flou.cz.
- No forms with personal data collection visible on homepage HTML.
- Cookie consent banner is implemented with detailed options.
- No security.txt or explicit vulnerability disclosure page found.
- No incident response or security contact email found.
- Use of modern tracking and chat tools indicates moderate digital maturity.
- No explicit certifications or compliance badges displayed.
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. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.
- 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, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (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
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Earlier scans of this domain
- 50/100Medium31 findingsView report
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 flou.cz. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review flou.cz.