Skip to main content

Security report for callbell.eu

Callbell S.A.S. · Technology · France

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

Security score

73/100

Risk levelMedium

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

Callbell S.A.S. is a technology company founded in 2019, offering a SaaS omnichannel customer communication platform that integrates popular messaging apps such as WhatsApp, Facebook Messenger, Instagram, and Telegram. The platform targets businesses seeking to centralize and optimize customer support and sales communications through a multi-agent chat system, chatbot automation, and broadcast messaging. Positioned as a Meta Business Partner and trusted by over 75,000 companies worldwide, Callbell demonstrates a strong market presence and a comprehensive suite of services tailored for modern customer engagement. Technically, the website is built on WordPress using the Divi theme, leveraging modern JavaScript libraries and integrations such as Google Analytics, TikTok Pixel, and Zapier SDK. The site is well-optimized for mobile devices, features good SEO practices, and employs GDPR-compliant privacy and cookie policies with consent mechanisms. Performance is moderate with room for improvement in accessibility features. From a security perspective, the site enforces HTTPS with excellent SSL configuration and uses privacy tools like Iubenda for cookie consent. However, explicit security headers are not detected, and there is no published security policy or incident response contact, which are areas for enhancement. No vulnerabilities or suspicious content were found, and the domain registration is consistent and legitimate. Overall, Callbell's website reflects a professional, trustworthy, and business-focused platform with strong branding and user experience. Strategic recommendations include enhancing security header implementation, publishing a security policy, and adding vulnerability disclosure information to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

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

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 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 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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

  4. 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 callbell.eu

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. 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
75
Security headers
45
Email security
65
DNS health
85
Network security
100
GDPR outside view
68
Average
73

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 callbell.eu, from OffSeq Breach.

Total records
11,633
Employees
10
Customers
11,564
Third parties
59
Weak passwords
18%

Latest record dated 2026-05-15 · 13 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for callbell.eu.

Select it in the checkout above.

Masked preview

  • –dash.callbell.eu2026-05-15
  • –dash.callbell.eu2026-02-22
  • –dash.callbell.eu2026-02-22
  • –metabase.callbell.eu2026-02-22
  • –dash.callbell.eu2025-08-13

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)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

Callbell operates in the technology sector, providing a SaaS platform for multi-channel customer communication and support. Its competitive advantage lies in integrating multiple popular messaging apps into a single platform with multi-agent collaboration, chatbot automation, and marketing broadcast capabilities. The business model is subscription-based with tiered pricing plans, including enterprise options with advanced features like ChatGPT integration and SAML/SSO authentication. The company targets SMEs to medium-sized enterprises globally, supported by a strong partner ecosystem including Meta. Growth indicators include a large customer base and active marketing through webinars, blogs, and social media. The platform's API and Zapier integration facilitate extensibility and automation, enhancing operational efficiency for clients.

Security posture

The website demonstrates a mature security posture with enforced HTTPS and use of privacy compliance tools. The absence of explicit security headers such as Content-Security-Policy and X-Frame-Options is a minor gap that could expose the site to certain web-based attacks. No sensitive data leakage or vulnerable libraries were detected. The lack of a published security policy and incident response contacts limits transparency and readiness for security incidents. GDPR compliance is evident through privacy and cookie policies with consent mechanisms. Overall, the security posture is good but can be improved by adopting additional security headers, publishing security documentation, and establishing clear incident response channels.

Recommendations

  1. Implement and explicitly configure security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Publish a dedicated security policy page outlining security practices, data protection measures, and compliance certifications to increase transparency and trust.
  3. Establish and publicize an incident response contact channel (e.g., security@ or abuse@ email) and consider adding a security.txt file to facilitate vulnerability reporting.
  4. Enhance accessibility features to improve usability for users with disabilities, aligning with WCAG standards.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are included and maintain up-to-date software versions.

Contact details published on the site

Addresses
Legal name
Callbell S.A.S.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Callbell S.A.S.
Description
Callbell is a SaaS platform providing omnichannel customer communication solutions via messaging apps such as WhatsApp, Facebook Messenger, Instagram, and Telegram.
Key services
Chat Module, Advanced Chatbot, Broadcast Module, API & Webhooks, Multi-channel messaging integration
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, Google Analytics, Google Tag Manager, YouTube Iframe API, TikTok Pixel, Zapier Partner SDK, Iubenda Cookie Consent
Frameworks
Divi WordPress Theme
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of third-party security and privacy tools (Iubenda for cookie consent)

Analytics and tracking

Services
Google Analytics, Google Tag Manager, TikTok Analytics, Facebook Pixel
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google Ads (AW-831035669)
Tracking pixels
TikTok Pixel, Facebook Pixel
Marketing tools
Zapier Integration
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Comprehensive multi-language support with hreflang tags.
  3. Strong social media presence and integration.
  4. Use of modern marketing and analytics tools.
  5. Clear and professional business presentation.
  6. No visible security policy or incident response information.
  7. Privacy and cookie policies are present and GDPR compliant.
  8. Pricing plans clearly detailed with currency switcher.
  9. Multiple contact methods including email and phone provided.
  10. Use of WordPress with Divi theme and common JS libraries.
Technical notes

Notes

The website is built on WordPress with the Divi theme, utilizing jQuery and modern JavaScript libraries for interactivity. It integrates multiple analytics and marketing tools including Google Analytics, Google Tag Manager, TikTok Pixel, and Facebook Pixel. The site supports multi-language content with hreflang tags and is mobile optimized with responsive design. Performance is moderate, with some lazy loading and asynchronous script loading to improve speed. The use of Zapier SDK indicates automation capabilities. Technical risks are minimal but include the need for improved security headers and enhanced accessibility. The infrastructure appears stable and professionally maintained, suitable for a SaaS business model.
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 callbell.eu. 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 callbell.eu.

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.