Skip to main content

Security report for screeb.app

Screeb · Technology · France

Low risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

77/100

Risk levelLow

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

Screeb is a technology company providing an all-in-one SaaS platform designed to enhance product experiences through user feedback, session replays, surveys, AI-driven analytics, and product tours. The company positions itself as a trusted partner for over 1000 product teams across more than 35 countries, focusing on GDPR compliance and privacy-conscious data collection. Their platform integrates with major SaaS tools such as Segment, Amplitude, Productboard, Notion, and Slack, indicating a mature ecosystem and strong market presence. Technically, Screeb leverages modern web technologies including Webflow for CMS and hosting, Piwik PRO for privacy-focused analytics, and JavaScript-based tracking and session replay scripts. The website is well-optimized for performance, mobile responsiveness, and accessibility, reflecting a high level of digital maturity. The use of a cookie consent banner and privacy policy demonstrates good privacy compliance practices. From a security perspective, the site enforces HTTPS and employs privacy-respecting analytics. However, explicit security headers and published security policies are not evident, suggesting room for improvement in transparency and incident response readiness. No vulnerabilities or exposed sensitive data were detected in the analyzed content. Overall, Screeb presents a professional, trustworthy, and privacy-conscious online presence with a strong focus on user experience and product analytics. The risk profile is low, but enhancing security disclosures and contact information would further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
100/ 100 · Low
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

3 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. 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching screeb.app

This scan found 19 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. 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
72
Security headers
30
Email security
75
DNS health
85
Network security
100
GDPR outside view
100
Average
77

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

Screeb operates in the competitive SaaS market for product analytics and user feedback tools, targeting product managers, UX teams, and SaaS companies. Their business model centers on subscription-based access to a comprehensive platform that combines session replays, surveys, AI analytics, and product tours. The presence of integrations with leading SaaS platforms and a client base spanning 35+ countries indicates a scalable and internationally oriented business. The company emphasizes GDPR compliance, which is critical for European and global customers. While direct revenue data is not available, the breadth of services and client trust signals suggest a medium-sized enterprise with growth potential. The lack of explicit contact details and security policies online may reflect a focus on digital self-service and automated support channels.

Security posture

The website demonstrates a solid baseline security posture with HTTPS enforced and privacy-focused analytics via Piwik PRO. The cookie consent mechanism aligns with GDPR requirements, enhancing privacy compliance. However, the absence of explicit security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces defense-in-depth. No published security policy or incident response contact information limits transparency and readiness perception. No vulnerabilities or sensitive data exposures were detected in the HTML content. Overall, the security maturity is good but could be improved by publishing formal security documentation, adding security headers, and providing clear incident response contacts.

Recommendations

  1. Implement and publish explicit security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance browser security.
  2. Create and publish a dedicated security policy page detailing security frameworks, practices, and incident response procedures.
  3. Establish and publicize a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Add clear contact information for security incidents, such as a security@ or abuse@ email address.
  5. Regularly audit and update third-party scripts and dependencies to mitigate risks from vulnerable libraries.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Screeb
Description
Screeb brings everything you need to elevate the product experience — observe user behavior through session replays, gather insights with surveys, analyze data with AI, and guide users with product tours.
Key services
Session Replays, Funnel Analysis, Surveys, AI Reports & Analysis, Product Tours, User Interview Recruitment, Release Management
Content quality
excellent
Branding
consistent

Technology

Stack
Webflow, Piwik PRO (analytics), JavaScript, CDN usage, Finsweet Attributes, Screeb Tag JS
Frameworks
Webflow CMS
Platforms
Web, Mobile (web & mobile apps supported)
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner with accept/deny options
  • No exposed sensitive data in HTML
  • Use of Piwik PRO for privacy-focused analytics

Analytics and tracking

Services
Piwik PRO, Google Tag Manager
Tracking level
extensive
Privacy practices
good

Advertising

Tracking pixels
Piwik PRO
Marketing tools
Piwik PRO
Transparency
good

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 challenges.
  2. Strong GDPR and privacy compliance with visible cookie consent mechanism.
  3. Comprehensive product offering focused on user feedback and product analytics.
  4. Use of modern web technologies and privacy-respecting analytics.
  5. No visible contact emails or phone numbers on the main site.
  6. No explicit security or incident response policies published.
  7. Good branding consistency and professional design.
  8. Multiple integrations with well-known SaaS platforms.
  9. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on Webflow CMS, leveraging modern JavaScript and CSS technologies. It uses Piwik PRO and Google Tag Manager for analytics and tracking, emphasizing privacy compliance. The hosting is via Webflow's CDN, ensuring fast global delivery and good performance. The site is mobile-optimized with responsive design and accessibility features such as focus outlines and semantic HTML. The technical implementation is modern and well-structured, with no broken elements detected. Opportunities exist to enhance security headers and formalize security documentation to reduce technical risks.
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 screeb.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 screeb.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.