Skip to main content

Security report for digistats.ch

digistats · Technology · Switzerland

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

59/100

Risk levelMedium

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

digistats is a Swiss-based privacy-focused web analytics provider offering a Google Analytics alternative that emphasizes user privacy by avoiding cookies, IP tracking, and fingerprinting. The company targets website owners who require GDPR, CCPA, and PECR compliant analytics solutions that are lightweight and easy to integrate. Their service includes real-time analytics, behavior tracking, geographic and technology insights, and adblocker-resistant data collection. The business model is subscription-based with a free 14-day trial and no credit card required, positioning digistats as a niche player in the privacy analytics market with a strong Swiss data protection emphasis. Technically, the website is built with modern web technologies including JavaScript and Bootstrap, likely running on Laravel backend as inferred from CSRF tokens. The site is fast, mobile-optimized, and well-structured with clear navigation and professional design. Hosting appears to be Swiss-based, supporting their privacy claims. The site uses HTTPS with strong SSL configuration and includes CSRF protection. However, explicit security headers are not detected, and no public security or incident response policies are published. From a security perspective, digistats demonstrates good practices by avoiding cookies and IP storage, reducing privacy risks. The presence of CSRF tokens and HTTPS is positive, but the absence of published security policies and vulnerability disclosure mechanisms is a gap. No vulnerabilities or suspicious patterns were detected in the content or WHOIS data. The domain registration aligns with the website's Swiss privacy focus, enhancing legitimacy. Overall, digistats presents a trustworthy, professional, and privacy-compliant analytics service with strong technical and business foundations. Strategic improvements include publishing security policies, adding security headers, and providing explicit incident response contacts to further enhance trust and security posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
65/ 100 · Medium
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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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 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

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • 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

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

Keep watching digistats.ch

This scan found 22 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. 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. 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
95
Security headers
25
Email security
65
DNS health
85
Network security
20
GDPR outside view
65
Average
59

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

digistats occupies a specialized niche in the web analytics market by focusing on privacy and compliance with European and US privacy laws. Their competitive advantage lies in offering analytics that bypass common adblockers and avoid personal data collection, appealing to privacy-conscious businesses and website owners. The subscription SaaS model with tiered pricing addresses various traffic needs, supporting scalability. The company has established a credible brand with over 120 companies trusting their service, indicating market traction. The bilingual website and sister domain in Germany suggest regional expansion strategies. The lack of direct contact emails or phone numbers may indicate a lean operational model focused on digital engagement. The partnership ecosystem is not explicitly detailed, but the presence of localized domains suggests strategic regional presence.

Security posture

digistats demonstrates a mature security posture with HTTPS enforced, CSRF protection, and a privacy-first data collection approach that excludes cookies and IP tracking. These practices reduce attack surface and privacy risks. However, the absence of explicit security headers like Content-Security-Policy and lack of published security or incident response policies represent areas for improvement. No vulnerability disclosures or security.txt files were found, limiting transparency for security researchers. The domain registration is consistent and not privacy-protected, supporting legitimacy. Overall, the security maturity is good but could be enhanced by formalizing policies and improving header configurations.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and compliance.
  2. Implement and serve security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Create a vulnerability disclosure policy and security.txt file to encourage responsible reporting.
  4. Provide explicit incident response contact channels (e.g., security@ or abuse@ email addresses).
  5. Consider adding a cookie consent mechanism or clear statement explaining the absence of cookies for transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
digistats
Description
Google Analytics Alternative aus der Schweiz mit höhstem Datenschutz. Anonym, ohne Cookies und ohne IP-Speicherung. 14 Tage kostenlos testen.
Key services
Realtime web analytics, Privacy-friendly tracking without cookies or IP storage, Adblocker-resistant analytics, Custom event tracking, Data export in CSV
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Bootstrap, SVG graphics
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • CSRF token present in meta tag
  • No cookies or IP tracking
  • No visible vulnerable libraries

Analytics and tracking

Services
digistats own analytics platform
Tracking level
minimal
Privacy practices
excellent

Advertising

Marketing tools
pa.track (custom event tracking)
Transparency
excellent

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. Strong emphasis on privacy and GDPR compliance.
  3. No cookies or IP tracking used, enhancing privacy.
  4. Clear business model as a privacy-friendly analytics provider.
  5. No direct contact emails or phone numbers found; contact via form only.
  6. No explicit security or incident response policies published.
  7. No cookie consent banner detected, possibly due to no cookies usage.
  8. Website is bilingual (English and German) with language switcher.
  9. No social media links or phone numbers explicitly found.
  10. No security.txt or vulnerability disclosure page found.
Technical notes

Notes

The website is built on a modern technology stack with JavaScript and Bootstrap for frontend and likely Laravel for backend, indicated by CSRF token usage. The site is well-optimized for mobile devices and loads quickly, with minimal tracking code size (<1kb). The use of SVG graphics and asynchronous script loading enhances performance. SEO is supported by proper meta tags and structured navigation. Hosting appears to be Swiss-based, aligning with privacy claims. No CMS is explicitly detected, suggesting a custom or framework-based solution. The technical implementation is robust with room for improvement in security headers and formalized security documentation.
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 digistats.ch. 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 digistats.ch.

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.