Skip to main content

Security report for circle.so

Circle · Technology · N/a

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

Security score

78/100

Risk levelLow

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

Circle is a technology company founded in 2019 that offers a comprehensive community platform enabling users to build branded communities, manage events, and host courses. The platform targets community builders, event organizers, and course creators, positioning itself as a complete SaaS solution in the community management space. The website is professionally designed, mobile-optimized, and leverages modern web technologies such as Next.js, React, and Builder.io for content management. Hosting and CDN services appear to be provided by Vercel and Cloudflare, ensuring fast and secure delivery. Security posture is strong with HTTPS enforced, multiple security headers, and no exposed sensitive data, although DNSSEC is not enabled. The site integrates various marketing and analytics tools including Google Analytics, Facebook Pixel, and HubSpot, indicating moderate user tracking. However, explicit privacy and cookie policies are not found, and no direct contact information or security incident response details are provided, which are areas for improvement. Overall, Circle demonstrates a mature digital presence with a solid technical foundation and good security practices but should enhance privacy compliance and transparency to further build trust.

Scanned

NIS2 and GDPR posture

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

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 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 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. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Unregistered MX Record

      MX record points to unregistered domain: 5b6vhttjgzjo6qhcfz3sogfdmyojuvxgulgf4tjfswlukdc4kstq.mx-verification.google.com

      What to do: Remove or fix MX record pointing to unregistered domain

      • RFC 5321 §5.1
      • NIS2 21(2)(i)
      • IR 2024/2690 12.4: Implementing Regulation (EU) 2024/2690, Annex point 12.4: Asset inventory
      • NIST CM-8: NIST SP 800-53 Rev. 5 CM-8: System Component Inventory

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

Keep watching circle.so

This scan found 17 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
100
Security headers
70
Email security
70
DNS health
55
Network security
100
GDPR outside view
73
Average
78

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

Circle operates in the technology sector with a SaaS business model focused on community platform services. Its market positioning emphasizes a branded, all-in-one solution for communities, events, and courses. The company likely generates revenue through subscription plans for its platform. The target customer segments include online community managers, educators, and event hosts. The website's integration with multiple marketing and analytics platforms suggests active growth and customer engagement strategies. No parent or subsidiary companies are identified. The domain age and registration data align with the company's founding year, supporting credibility. The absence of explicit privacy and security policies may reflect a need to mature compliance practices as the company scales.

Security posture

The website enforces HTTPS with a strong SSL configuration and implements key security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options, indicating a robust security baseline. No vulnerabilities or exposed sensitive data were detected in the analyzed content. The use of Cloudflare DNS enhances DNS security, although DNSSEC is not enabled, which is recommended for further protection. The site uses secure third-party integrations for forms and analytics. However, the lack of a published security policy, incident response contacts, or vulnerability disclosure program limits transparency and may hinder rapid incident handling. Overall, the security posture is strong but could be improved with formalized policies and disclosure mechanisms.

Recommendations

  1. Enable DNSSEC on the domain to strengthen DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies clearly accessible from the website footer or header.
  3. Implement a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  4. Provide explicit contact information for security incidents, such as a dedicated security@ or abuse@ email address.
  5. Regularly review and audit third-party scripts and integrations to minimize potential security risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Circle
Description
Build a home for your community, events, and courses — all under your own brand.
Key services
Community platform, Events management, Course hosting
Content quality
good
Branding
consistent

Technology

Stack
Next.js, React, Cloudflare DNS, Vercel (likely hosting), Builder.io (content management), Visual Website Optimizer (VWO), Google Analytics, Facebook Pixel, LinkedIn Pixel, HubSpot Forms
Frameworks
Next.js, React
Platforms
Vercel
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of Cloudflare DNS
  • No exposed sensitive data detected
  • Use of security headers
  • Secure forms with HubSpot integration

Analytics and tracking

Services
Google Analytics, Microsoft Clarity, Visual Website Optimizer (VWO), ProfitWell
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Facebook Pixel, LinkedIn Pixel, Microsoft Clarity, ProfitWell, Claydar
Marketing tools
HubSpot, Visual Website Optimizer (VWO)
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. No explicit privacy, cookie, or terms of service pages found in the provided content.
  3. Multiple third-party marketing and analytics tools are integrated.
  4. No direct company contact emails or phone numbers found in the HTML content.
  5. Website uses modern web technologies and is well optimized for performance and mobile.
  6. Security best practices are observed but DNSSEC is not enabled.
  7. No vulnerability disclosure or security contact information is provided.
  8. Content is safe and suitable for general audiences.
Technical notes

Notes

The website is built using modern web technologies including Next.js and React, with content managed via Builder.io. Hosting appears to be on Vercel with Cloudflare DNS providing DNS services. The site is optimized for performance and mobile responsiveness, with preloading of fonts and images and use of CDN resources. Analytics and marketing tools such as Google Analytics, HubSpot, and Visual Website Optimizer are integrated for user behavior tracking and conversion optimization. Security headers and HTTPS are properly configured, contributing to a secure browsing experience. No major technical debt or outdated technologies were detected. Opportunities exist to enhance DNS security and improve privacy compliance documentation.
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

Earlier scans of this domain

  1. 83/100Low22 findingsView report
Reviews of this site

Share your experience with circle.so. 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 circle.so.

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.