Skip to main content

Security report for stat.re

Plausible Analytics · Technology · N/a

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

Security score

66/100

Risk levelMedium

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

Plausible Analytics offers a privacy-focused, lightweight alternative to Google Analytics, targeting website owners who prioritize visitor privacy and data ownership. The business operates a self-hosted analytics dashboard at stat.re, distinct from their official managed hosting at plausible.io. The company is positioned as a niche player in the web analytics market with a subscription-based business model supported by over 10,000 paying customers. The website content is professional, well-structured, and consistent with the brand's privacy-centric ethos. Technically, the website employs modern web technologies including JavaScript and CSS, with Cloudflare Insights used for performance monitoring. The site is mobile-optimized and accessible, with fast loading times and good SEO practices. However, explicit security headers are not evident in the HTML content, and no cookie consent mechanism is implemented despite the presence of a cookie policy. No forms on the main page collect sensitive data, reducing immediate risk. From a security perspective, the site enforces HTTPS and shows no signs of exposed sensitive data or vulnerable libraries. The absence of a published vulnerability disclosure or incident response contact reduces transparency in security management. WHOIS data aligns well with the website's claims, indicating a legitimate and trustworthy domain registration. Overall, the security posture is strong but could be improved by adding security headers and formalizing incident response processes. The overall risk assessment is low, with no critical issues detected. Strategic recommendations include implementing cookie consent, adding security headers, publishing vulnerability disclosure information, and enhancing incident response readiness to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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 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. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

  4. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Weak SPF Policy

      SPF record has permissive policy allowing any server to send email

      What to do: Use -all or ~all qualifier for better email security

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

Keep watching stat.re

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. 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
75
Security headers
55
Email security
70
DNS health
45
Network security
100
GDPR outside view
53
Average
66

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention stat.re, from OffSeq Breach.

No leaked records found

Breach holds no records for stat.re right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Plausible Analytics occupies a specialized segment in the web analytics market, focusing on privacy and simplicity. Its competitive advantage lies in being open source, lightweight, and fully respecting user privacy, differentiating it from dominant players like Google Analytics. The subscription-based model ensures recurring revenue, supported by a sizable paying user base. The company leverages partnerships and community engagement through GitHub, Twitter, Mastodon, and LinkedIn, fostering transparency and trust. The self-hosted dashboard at stat.re serves technically savvy customers preferring control over their data. Growth indicators include a strong community and continuous documentation updates. The partnership with plausible.io as the official managed hosting provider strengthens the ecosystem and market reach.

Security posture

The website demonstrates a mature security posture with mandatory HTTPS and no visible exposure of sensitive data. The use of Cloudflare Insights indicates proactive performance and security monitoring. However, the lack of explicit security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options represents an area for improvement. The absence of a formal vulnerability disclosure policy or security.txt file limits transparency and may hinder coordinated vulnerability reporting. No incident response contact channels are provided, which could delay response to security incidents. Overall, the security culture appears strong but would benefit from formalizing policies and enhancing header configurations to align with best practices and compliance requirements.

Recommendations

  1. Implement a cookie consent mechanism to comply with privacy regulations and enhance user trust.
  2. Add security headers including Content Security Policy, HSTS, and X-Frame-Options to strengthen defense-in-depth.
  3. Publish a vulnerability disclosure policy and security.txt file to facilitate responsible reporting and improve transparency.
  4. Provide clear incident response contact information to enable timely communication in case of security events.
  5. Consider pursuing recognized security certifications such as ISO 27001 to reinforce business credibility and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Plausible Analytics
Description
Plausible Analytics is a simple, open source, lightweight (< 1 KB) and privacy-friendly alternative to Google Analytics. It is independent and funded by over 10,000 paying subscribers.
Key services
Web analytics, Privacy-friendly data tracking, Self-hosted and managed hosting options
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, CSS, HTML5
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data
  • No vulnerable libraries detected
  • No forms collecting sensitive data on main page

Analytics and tracking

Services
Cloudflare Insights
Tracking level
minimal
Privacy practices
excellent

Advertising

Tracking pixels
Cloudflare Insights
Transparency
good

Site quality

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

Key observations

  1. Website is a self-hosted dashboard for Plausible Analytics, distinct from official plausible.io managed hosting.
  2. Content is focused on privacy-friendly web analytics.
  3. No forms on main page except login/register links.
  4. No direct contact emails or phone numbers on this domain; contact info is on plausible.io domain.
  5. No explicit cookie consent banner despite cookie policy presence.
  6. Uses Cloudflare Insights for performance monitoring.
  7. No security.txt or explicit vulnerability disclosure found.
Technical notes

Notes

The website is built using modern web standards with clean HTML5, CSS, and JavaScript. It leverages Cloudflare for CDN and performance monitoring, contributing to fast load times and good mobile optimization. The absence of a CMS suggests a custom or static site approach, reducing attack surface. SEO is well addressed with appropriate meta tags and descriptive titles. Accessibility features appear adequate, supporting a broad user base. Technical debt is minimal, but the lack of security headers and cookie consent indicates areas for modernization. Overall, the technical infrastructure supports reliable and performant operations with opportunities for enhanced security and compliance integration.
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 stat.re. 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 stat.re.

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.