Skip to main content

Security report for crowdly.com

Crowdly · Technology · N/a

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

Security score

74/100

Risk levelMedium

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

Crowdly operates a mature customer engagement platform focused on activating brand advocates for market research, user-generated content, and word-of-mouth marketing. The company targets brands seeking to deepen customer loyalty and engagement through a SaaS model with managed service options. The website presents a professional and consistent brand image supported by client logos, case studies, and testimonials, indicating a strong market position. Technically, the website uses modern frameworks such as Bootstrap 5, integrates Google Analytics, Google Tag Manager, and Intercom for marketing and customer support. Hosting and DNS are managed via Cloudflare, providing performance and security benefits. The site is mobile optimized and SEO friendly, though accessibility features are basic. Security posture is solid with HTTPS enforced and CSRF protections in forms. However, DNSSEC is not enabled and security headers are not detected, representing areas for improvement. Privacy compliance is partial; a privacy policy is present and GDPR compliance is indicated, but no cookie consent mechanism is implemented. No explicit security policy or incident response contacts are published. Overall, Crowdly's website is trustworthy and professional with a good security baseline. Strategic improvements in privacy compliance and security hardening would enhance trust and reduce risk.

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

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 crowdly.com

This scan found 19 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
65
Security headers
65
Email security
85
DNS health
75
Network security
100
GDPR outside view
53
Average
74

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 crowdly.com, from OffSeq Breach.

No leaked records found

Breach holds no records for crowdly.com 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

Crowdly is positioned as a specialized SaaS provider in the customer engagement and advocacy space, serving medium-sized to large brands. Their business model combines software with optional managed services, targeting marketing teams focused on loyalty, research, and authentic customer content. The presence of well-known client logos and detailed case studies suggests a competitive advantage in delivering measurable advocacy outcomes. The company appears to have stable operations since 2006, with a consistent brand and digital presence. Partnerships or subsidiaries are not explicitly identified. Marketing efforts leverage digital channels and content marketing to attract prospects. The company’s ecosystem includes integrations with Salesforce (lead capture form) and uses popular marketing and analytics tools, indicating a mature digital marketing strategy. Growth potential lies in expanding managed services and enhancing platform capabilities.

Security posture

The website demonstrates a moderate to good security maturity level. HTTPS is enforced site-wide, and forms include CSRF tokens, reducing common web attack vectors. Use of Cloudflare DNS and CDN adds protection and performance benefits. However, the absence of DNSSEC leaves DNS vulnerable to spoofing attacks. No HTTP security headers such as Content-Security-Policy or X-Frame-Options were detected, which could mitigate clickjacking and content injection risks. No security.txt or vulnerability disclosure policy is published, limiting transparency for security researchers. Incident response contacts are not provided, which could delay reporting and remediation of security incidents. Privacy compliance is partial; while a privacy policy exists and GDPR compliance is implied, cookie consent mechanisms are missing, potentially exposing the company to regulatory risk. No exposed sensitive data or vulnerable libraries were detected in the HTML content. Overall, the security posture is adequate but could be improved by implementing recommended headers, DNSSEC, and formal security policies.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve overall DNS security.
  2. Implement standard HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  3. Add a cookie consent banner or mechanism to comply with GDPR and other privacy regulations.
  4. Publish a formal security policy and incident response contact information to improve transparency and facilitate vulnerability reporting.
  5. Conduct regular security audits and penetration testing to identify and remediate potential vulnerabilities proactively.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Crowdly
Description
Crowdly offers an all-in-one customer engagement platform that activates customers for rapid research, customer-generated content, and authentic word-of-mouth marketing at scale.
Key services
Customer engagement platform, Advocate community building, Market research, User-generated content (UGC) and social sharing, Sampling and reviews, Loyalty and word-of-mouth marketing
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap 5, Google Fonts (Roboto, Hind Madurai), Google Tag Manager, Google Analytics, Google Ads, Intercom chat widget, Cloudflare DNS
Frameworks
Bootstrap
Platforms
Cloudflare (DNS and likely CDN)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • CSRF tokens present in forms
  • Use of Cloudflare DNS and protections

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Google Ads
Tracking pixels
Intercom
Marketing tools
Intercom
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and no blocking detected.
  2. Strong branding and consistent messaging about customer engagement platform.
  3. Multiple client logos and case studies enhance trust.
  4. No explicit cookie consent mechanism found.
  5. No visible security.txt or vulnerability disclosure policy.
  6. No explicit security policy or incident response information published.
  7. Use of modern web technologies and analytics tools.
  8. WHOIS data supports legitimacy and long-term operation.
Technical notes

Notes

The website is built on a modern technology stack including Bootstrap 5 for responsive design, Google Fonts for typography, and integrates Google Tag Manager and Analytics for tracking. Intercom is used for customer support chat functionality. Hosting and DNS are managed via Cloudflare, providing CDN and security benefits. The site uses CSRF tokens in forms, indicating attention to secure form handling. Performance is moderate with no obvious blocking scripts or heavy resources. Mobile optimization is good with responsive layouts and font scaling. SEO is supported by proper meta tags including Open Graph and Twitter cards. Accessibility features are basic; no ARIA landmarks or advanced accessibility attributes were detected. No CMS is detected, suggesting a custom or static site architecture. The site could benefit from enhanced accessibility and additional security headers to reduce technical risk.
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 crowdly.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 crowdly.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.