Skip to main content

Security report for preely.com

GetWhy A/S · Technology · Denmark

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

Security score

60/100

Risk levelMedium

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

Preely is a Denmark-based technology company offering a SaaS platform focused on enhancing product decision-making through remote user testing and continuous discovery. Their platform supports testing of prototypes across devices and integrates AI (ChatGPT) for advanced test analysis. The company targets product teams, UX professionals, and businesses seeking efficient user feedback mechanisms. The website demonstrates a professional presence with trusted clients and active social media engagement. Technically, the website is built on WordPress with WPBakery Page Builder, leveraging Cloudflare for DNS and CDN services. It employs standard marketing and analytics tools including Google Analytics, Facebook Pixel, and Cookiebot for GDPR-compliant cookie management. While the SSL certificate is valid, the site lacks advanced security headers and HSTS, and performance metrics indicate a slower load time. Security posture is moderate with no critical vulnerabilities detected, but improvements are recommended in HTTP security headers and DNSSEC implementation. Privacy compliance is strong, supported by a comprehensive privacy policy and cookie consent mechanism. Business credibility is reinforced by clear company information, testimonials, and client logos. Overall, Preely presents a trustworthy and functional online presence with room for technical and security enhancements to further strengthen its posture and user trust.

Scanned

NIS2 and GDPR posture

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

9 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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

Keep watching preely.com

This scan found 25 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
67
Security headers
25
Email security
60
DNS health
85
Network security
100
GDPR outside view
25
Average
60

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

Preely operates in the competitive UX research and product feedback market, differentiating itself with AI-powered analysis and seamless integration with popular design tools. Its business model is subscription-based SaaS with a free trial, targeting UX teams and product managers. The company has established credibility through partnerships with notable clients and maintains active marketing and social engagement. Growth potential lies in expanding AI capabilities and broadening user panel recruitment features. The company’s operations appear transparent and aligned with GDPR requirements, supporting sustainable market positioning.

Security posture

The website maintains a valid SSL certificate ensuring encrypted communications but lacks HTTP security headers such as HSTS, Content-Security-Policy, and X-Frame-Options, which are recommended to mitigate common web attacks. DNSSEC is not enabled, exposing potential DNS spoofing risks. Cookie consent is managed via Cookiebot, indicating GDPR awareness. No exposed sensitive data or vulnerable libraries were detected. Incident response and security policy documentation are not publicly found, suggesting an area for improvement. Overall, the security maturity is moderate with actionable recommendations to enhance defenses and compliance.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS.
  2. Implement essential security headers: Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
  3. Activate DNSSEC for the domain to protect against DNS spoofing and cache poisoning.
  4. Publish a clear security policy and incident response contact information to improve transparency and trust.
  5. Regularly audit and update third-party scripts and plugins to minimize vulnerabilities.

Contact details published on the site

Addresses
Legal name
GetWhy A/S
Registration number
33510608
Technical notes

Notes

The website uses a mature CMS (WordPress) with a popular page builder (WPBakery), supported by Cloudflare DNS and CDN services. It integrates multiple marketing and analytics tools, including Google Analytics and Facebook Pixel, with GDPR-compliant cookie management via Cookiebot. Performance is suboptimal with a high page size and load time, indicating potential for optimization. The site is mobile-optimized and SEO-friendly with proper meta tags and structured data. Technical debt is moderate, with opportunities to improve security headers and enable DNSSEC. Overall, the infrastructure supports business needs but would benefit from performance tuning and enhanced security configurations.
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 preely.com. 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 preely.com.

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.