Skip to main content

Security report for callpage.io

CallPage · Technology · N/a

Medium risk. 5 critical or high findings in Security headers and GDPR outside view.

Security score

68/100

Risk levelMedium

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

CallPage is a technology company specializing in lead capture and sales automation tools, including click-to-call widgets, AI voice agents, virtual PBX, and meeting scheduling solutions. The company targets marketing, sales, and support teams across diverse industries such as healthcare, education, real estate, automotive, ecommerce, and travel. With over 1,500 companies using its services, CallPage holds a strong market position as an innovative SaaS provider offering subscription-based lead generation and communication solutions. The website is built on a modern React framework (Next.js) hosted on AWS, integrating multiple marketing and analytics tools like HubSpot, Google Analytics, Hotjar, and Microsoft Clarity. Despite a rich content offering and good privacy compliance, the site suffers from critical security issues including an invalid SSL certificate and lack of HTTPS, which significantly impacts its security posture. The absence of key security headers and modern TLS protocols further lowers its security score. Overall, the website demonstrates excellent content quality and business credibility but requires urgent security improvements to protect user data and maintain trust.

Scanned

This is an earlier scan of callpage.io. View the latest report

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

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 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 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

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

Keep watching callpage.io

This scan found 22 issues across 5 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
100
Security headers
15
Email security
70
DNS health
80
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

CallPage operates in the technology sector with a focus on lead generation and customer engagement solutions. Its business model revolves around SaaS offerings with free trials to attract users. The company serves a broad target audience including marketing, sales, and support teams in multiple verticals, enhancing its market reach. The presence of an affiliate program and extensive integrations with popular tools like Zapier and HubSpot indicates a mature partnership ecosystem. Customer testimonials and case studies highlight strong customer satisfaction and product effectiveness. The company leverages advanced AI technologies to differentiate its offerings, such as AI Voice Agent for 24/7 call handling and lead qualification. The website's multilingual support (English, Italian, Polish) suggests a strategy for international market penetration. However, the lack of visible physical addresses or phone numbers may limit direct customer trust in some regions.

Security posture

The current security posture of the website is weak due to the absence of a valid SSL certificate and HTTPS support, exposing users to potential data interception risks. The lack of security headers such as HSTS, CSP, and others further weakens the defense against common web attacks. No DNSSEC or CAA records are configured, which could improve DNS security. The site does not exhibit known vulnerabilities like Heartbleed or POODLE, but the missing TLS protocols and session resumption mechanisms indicate outdated or misconfigured SSL/TLS settings. Privacy compliance is supported by a comprehensive cookie consent mechanism and GDPR-aligned policies, but the security infrastructure needs urgent enhancement. Incident response and vulnerability disclosure information are not publicly available, which may affect transparency and trust. Overall, the site requires immediate remediation of SSL issues and implementation of security best practices to safeguard user data and maintain compliance.

Recommendations

  1. Obtain and install a valid SSL certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated protocols.
  3. Implement HTTP security headers including HSTS with includeSubDomains and preload flags.
  4. Configure DNSSEC and CAA records to enhance DNS security and certificate issuance control.
  5. Publish clear incident response and vulnerability disclosure policies to improve transparency and trust.
Technical notes

Notes

The website is built using Next.js, a React-based framework supporting server-side rendering and static site generation, indicating a modern and scalable architecture. Hosting is provided by Amazon AWS, inferred from DNS nameservers. The site integrates multiple third-party marketing and analytics tools such as HubSpot, Google Tag Manager, Google Analytics, Hotjar, Microsoft Clarity, Facebook Pixel, Reddit Pixel, and Bing Ads, reflecting a mature digital marketing strategy. The CMS appears to be Strapi, based on URL patterns. Performance is suboptimal with a load time of approximately 15.7 seconds and a large page size (~1MB) with 252 resources, suggesting opportunities for optimization. Accessibility and SEO are rated good, with proper meta tags, alternate language links, and responsive design. However, the invalid SSL certificate and lack of HTTPS significantly undermine the technical robustness and security of the platform.
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. 68/100 +2Medium32 findingsView report
  2. 66/100Medium33 findingsView report
Reviews of this site

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