Skip to main content

Security report for thermostat.io

Thermostat · Technology · N/a

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

Security score

68/100

Risk levelMedium

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

Thermostat.io is a specialized SaaS provider offering Net Promoter Score (NPS) survey software designed to simplify customer satisfaction measurement through one-question surveys. The company targets businesses, particularly SaaS and e-commerce, seeking actionable customer feedback with flexible survey administration methods including email, popup, link, and API. The website demonstrates a professional and consistent brand presence with clear pricing tiers and a 30-day money-back guarantee, positioning itself as a trustworthy niche player in the customer feedback software market. Technically, the site leverages modern frontend frameworks such as Alpine.js and Livewire, is hosted behind Cloudflare with a valid SSL certificate and strong security headers, and integrates with third-party services like Zapier and Fathom Analytics for marketing and analytics. However, privacy compliance is basic, with no cookie consent mechanism and a privacy policy hosted on a third-party domain. Security posture is good but could be improved with DNSSEC, CAA records, and published incident response policies. Overall, the website is well-implemented, secure, and credible but would benefit from enhanced privacy and security transparency.

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

4 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

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

Keep watching thermostat.io

This scan found 18 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. 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
64
Security headers
65
Email security
50
DNS health
85
Network security
100
GDPR outside view
43
Average
68

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

Thermostat operates a subscription-based SaaS business model with free and tiered paid plans differentiated by survey volume and features. Its market positioning focuses on simplicity and effectiveness in NPS surveying, appealing to small and medium businesses. The company leverages partnerships with Zapier for integrations and uses Mailgun for email delivery. The absence of direct contact emails or phone numbers on the site suggests a lean support model primarily via contact forms. The use of Cloudflare and modern web technologies indicates a mature technical infrastructure. The company’s transparent pricing and money-back guarantee are competitive advantages. However, the lack of explicit security and privacy policies may impact trust for privacy-conscious customers.

Security posture

The website enforces HTTPS with a valid SSL certificate and HSTS, employs multiple security headers (X-Frame-Options, X-XSS-Protection, X-Content-Type-Options), and uses secure cookies with appropriate flags. No vulnerabilities or exposed sensitive data were detected. However, the absence of DNSSEC and CAA records reduces DNS security. There is no published security policy or incident response contact, which limits transparency and preparedness perception. Privacy compliance is limited by the lack of cookie consent mechanisms and hosting the privacy policy offsite. Overall, the security posture is good but could be enhanced by adopting additional DNS security measures, publishing security policies, and implementing privacy best practices.

Recommendations

  1. Implement a cookie consent banner and publish a dedicated cookie policy to improve GDPR compliance.
  2. Add DNSSEC and CAA DNS records to strengthen domain security and certificate issuance control.
  3. Publish a comprehensive security policy and incident response contact information on the website.
  4. Host the privacy policy on the company’s own domain to improve trust and control.
  5. Add Content Security Policy (CSP) headers and enable certificate transparency reporting for enhanced security.
Technical notes

Notes

The website is built with modern frontend technologies including Alpine.js and Laravel Livewire, styled with Tailwind CSS, and served via Cloudflare CDN. It integrates with third-party services such as Zapier and Mailgun for automation and email delivery, and uses Fathom Analytics for privacy-focused user tracking. The site is mobile responsive and well-structured with semantic HTML and ARIA roles for accessibility. Performance is optimized with preloading of CSS and deferred script loading. No CMS was detected, indicating a custom-built solution. The technical infrastructure is robust and modern, supporting scalability and integration needs. Opportunities exist to improve SEO and accessibility further by adding more meta tags and ARIA landmarks.
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 thermostat.io. 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 thermostat.io.

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.