Skip to main content

Security report for frill.co

Domains By Proxy, LLC (registrant proxy), actual company name not explicitly stated · Technology · United States

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

Security score

71/100

Risk levelMedium

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

Frill.co is a SaaS platform specializing in customer feedback, product roadmaps, announcements, and surveys, targeting startups, charities, and entrepreneurs. The company positions itself as an independent and bootstrapped alternative to competitors like Canny and Beamer, offering a web app and widget for seamless customer feedback management. The website is professionally designed with excellent content quality and clear navigation, supporting a positive user experience and strong trust indicators such as customer testimonials and third-party review ratings. Technically, the site is built on modern frameworks including Next.js and React, hosted on AWS infrastructure, and integrates multiple analytics and marketing tools. However, the website suffers from a critical security weakness due to the absence of a valid SSL certificate and HTTPS support, which significantly impacts its security posture. Privacy compliance is well addressed with a comprehensive privacy policy, cookie consent mechanism, and GDPR adherence. Overall, the site demonstrates a mature business presence but requires urgent security improvements to protect user data and enhance trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 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 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

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

Keep watching frill.co

This scan found 20 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
20
Email security
75
DNS health
85
Network security
100
GDPR outside view
43
Average
71

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

Frill operates in the technology sector, focusing on SaaS solutions for product teams and businesses seeking to streamline customer feedback and roadmap management. Its business model relies on subscription plans with a free trial, appealing to small to medium-sized enterprises and startups. The company leverages integrations with popular tools like Slack, Jira, Trello, and Zendesk to enhance workflow automation. Market positioning is strengthened by independent operation and positive customer feedback. The use of privacy protection in domain registration is typical for startups, and the domain age aligns with the company's founding year. The absence of direct contact information on the website suggests a focus on digital engagement channels. The partnership ecosystem includes recognized SaaS and analytics providers, supporting a robust operational framework.

Security posture

The security posture of frill.co is currently weak due to the lack of a valid SSL certificate and HTTPS support, exposing users to potential data interception risks. No HTTP security headers were detected, and modern TLS protocols are not enabled. While SPF and DMARC records are properly configured, enhancing email security, the absence of HSTS, OCSP stapling, and session resumption reduces overall security effectiveness. No explicit security policies or incident response contacts are publicly available, indicating limited transparency in security governance. The use of multiple third-party scripts and tracking pixels increases the attack surface, necessitating regular security audits. Immediate remediation of SSL/TLS issues and implementation of security headers are critical to improving the site's security posture.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Enable HSTS with includeSubDomains and preload directives to enforce HTTPS.
  4. Activate OCSP stapling and session resumption to improve TLS performance and security.
  5. Publish a clear security policy and incident response contact information to enhance transparency and trust.
Technical notes

Notes

The website is built on a modern technology stack including Next.js and React, hosted on AWS infrastructure with DNS managed by Amazon Route 53. It integrates various marketing and analytics tools such as Google Tag Manager, Hotjar, Plausible Analytics, and Usermaven, alongside a cookie consent management system (CookieYes). Despite the modern stack, the site suffers from slow load times (15.6 seconds) and a large page size (568 KB) with many resources (229), indicating potential optimization opportunities. Mobile optimization is good, but accessibility features are basic. SEO is well addressed with proper meta tags and Open Graph data. The absence of a valid SSL certificate is a major technical risk. Overall, the infrastructure is solid but requires performance tuning and security enhancements to reduce technical debt and operational 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 frill.co. 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 frill.co.

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.