Skip to main content

Security report for statview.app

Statview · Technology · N/a

Medium risk. 5 critical or high findings in Security headers and GDPR outside view.

Security score

61/100

Risk levelMedium

0–100, higher is better. How it is calculated

Statview is a technology-focused SaaS platform offering a centralized dashboard solution for developers and project managers using Laravel and Filament PHP frameworks. The platform aims to consolidate project statistics and management features into a single interface, currently in beta trial phase. The website content is professionally designed and clearly communicates the product's value proposition and key features, targeting a niche developer audience. Technically, the site uses Laravel and Filament frameworks and integrates Matomo analytics for user tracking. However, the website suffers from significant security shortcomings, notably the absence of a valid SSL certificate and HTTPS support, which critically undermines user trust and data security. Additionally, the lack of privacy and cookie policies and absence of contact information further reduce compliance and credibility. Overall, the site is functional but requires urgent improvements in security and privacy compliance to meet industry standards and user expectations.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (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

5 findings rated critical or high. Fix these first.

  1. 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
    • 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';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

    • 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

Need hands-on remediation? Email guard@offseq.com

Keep watching statview.app

This scan found 13 issues across 5 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
100
Security headers
50
Email security
50
DNS health
85
Network security
40
GDPR outside view
40
Average
61

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

Statview positions itself as an early-stage SaaS provider in the developer tools market, focusing on Laravel and Filament users. Its competitive advantage lies in simplifying project statistics management by aggregating data across multiple projects. The business model appears subscription or usage-based, with a beta trial to attract early adopters. The platform's integration with popular PHP frameworks and the use of Matomo analytics indicate a modern tech stack. However, the lack of visible business contact details and compliance documentation may hinder trust and adoption. The company currently operates independently without visible parent or subsidiary relationships. Growth potential depends on improving security posture, expanding feature set beyond beta, and establishing transparent privacy and support channels.

Security posture

The website's security posture is weak due to the absence of a valid SSL certificate and HTTPS support, exposing users to potential data interception and man-in-the-middle attacks. No security headers are implemented, and DNSSEC is disabled, increasing susceptibility to DNS spoofing. The site does not employ HSTS, OCSP stapling, or session resumption, which are best practices for secure and performant TLS connections. Privacy compliance is lacking, with no privacy or cookie policies and no GDPR indicators. Incident response and vulnerability disclosure mechanisms are not present, limiting the ability to handle security incidents effectively. These gaps represent significant risks to user data protection and regulatory compliance. Immediate remediation is necessary to establish a secure and trustworthy environment.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement essential security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish comprehensive privacy and cookie policies with clear consent mechanisms to comply with GDPR and other regulations.
  4. Add clear and accessible contact information including support and security incident channels.
  5. Enable DNSSEC and CAA records to strengthen domain security and certificate issuance control.
Technical notes

Notes

The website is built on Laravel and Filament PHP frameworks, indicating a modern and extensible backend architecture. It uses Matomo for analytics, which is a privacy-focused alternative to Google Analytics. Hosting and DNS are managed via Cloudflare, providing potential for enhanced security and performance features, though these are not fully utilized. The site suffers from slow load times (~23 seconds) despite a moderate page size (~130 KB) and 34 resources, suggesting optimization opportunities. Fonts and assets are served from the same domain, reducing third-party dependencies. The absence of CMS and limited external integrations indicate a focused, custom-built platform. Technical debt is moderate, with clear paths for modernization through improved SSL, security headers, and performance tuning.
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.

Retrieved 2026-10-25

Reviews of this site

Share your experience with statview.app. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review statview.app.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.