Skip to main content

Security report for webroot.com

Webroot · Technology · United States

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

46/100

Risk levelHigh

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

Webroot, a subsidiary of Open Text Corporation, is a well-established cybersecurity company founded in 2004, providing multi-vector protection solutions for endpoints, networks, and identity protection. The company targets both home users and businesses, offering a broad portfolio of products including antivirus, identity protection, cloud backup, VPN, and threat intelligence services. The website reflects a mature enterprise with consistent branding, comprehensive content, and strong market positioning supported by industry awards and customer testimonials. Technically, the website is built on a Concrete5 CMS platform, leveraging Apache server technology, jQuery, Google Fonts, and is delivered via Imperva CDN. While the site is mobile-optimized and accessible with good SEO practices, performance data is limited and suggests moderate speed. The site uses modern marketing and analytics tools such as Google Tag Manager and Sitespect for tracking and optimization. From a security perspective, the site lacks a valid SSL certificate and does not support HTTPS or modern TLS protocols, which is a critical vulnerability exposing users to potential interception and attacks. Security headers are partially implemented but key protections like HSTS and OCSP stapling are missing. No explicit security policy or incident response information is provided, which could be improved to enhance trust and compliance. Overall, the website demonstrates high business credibility and content quality but suffers from significant security configuration issues that must be addressed to protect users and maintain compliance. Strategic improvements in SSL/TLS deployment and security best practices are recommended to elevate the security posture and user trust.

Scanned

NIS2 and GDPR posture

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

8 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

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

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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';…

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

Keep watching webroot.com

This scan found 16 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
0
Security headers
20
Email security
50
DNS health
90
Network security
100
GDPR outside view
15
Average
46

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

Webroot operates in the cybersecurity technology sector, serving a diverse customer base including individual consumers, families, small to medium businesses, managed service providers, and technology partners. The company leverages a subscription-based business model offering various tiers of endpoint protection, identity theft protection, and cloud services. Its market position is strengthened by its parent company Open Text, extensive industry certifications, and a large installed base of over 285 million protected devices. The company maintains a robust partner ecosystem and provides resources such as trials, product comparisons, and support to facilitate customer acquisition and retention. Growth indicators include new product launches, continuous updates, and active community engagement. The website's integration with Open Text's broader infrastructure and branding enhances its credibility and reach. However, the lack of direct contact emails and phone numbers on the site may limit immediate customer engagement channels. The company’s strategic focus on both home and business cybersecurity markets positions it well for sustained growth amid increasing cyber threats.

Security posture

The current security posture of the website is moderate to poor due to the absence of a valid SSL certificate and lack of HTTPS support, which is a critical security flaw. While the site employs secure cookie flags and avoids known SSL/TLS vulnerabilities like Heartbleed and POODLE, the missing encryption layer exposes all data transmissions to risk. Security headers are present but incomplete, lacking HSTS and OCSP stapling, which are important for preventing downgrade attacks and improving certificate validation. No dedicated security policy or incident response contact information is found, which could hinder transparency and responsiveness in case of security incidents. The DNS configuration shows malformed CAA records, which could affect certificate issuance security. Overall, the site needs urgent remediation of its SSL/TLS configuration and enhancement of security policies to meet industry standards and regulatory compliance such as GDPR and NIS2.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable and enforce modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated versions.
  3. Configure HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Correct the malformed CAA DNS records to ensure proper certificate authority authorization.
  5. Publish a clear security policy and incident response contact information on the website.
  6. Enhance security headers to include Content Security Policy (CSP), X-Content-Type-Options, and X-Frame-Options.
  7. Improve performance monitoring and optimization to reduce page load times.
  8. Consider adding direct verified contact emails and phone numbers for customer support and security inquiries.

Contact details published on the site

Addresses
Legal name
Open Text Corporation
Technical notes

Notes

The website runs on Apache server with Concrete5 CMS, utilizing jQuery and Google Fonts for frontend functionality and styling. It is served through Imperva CDN, which provides some security and performance benefits. The site uses Google Tag Manager and Sitespect for analytics and A/B testing. The HTML content is well-structured with responsive design and accessibility considerations. However, the SSL/TLS configuration is critically lacking, with no valid certificate and no TLS protocols enabled, resulting in insecure HTTP connections. DNSSEC is not enabled, and CAA records are malformed, indicating potential gaps in DNS security. Performance metrics are not available, but chunked transfer encoding and multiple external resources suggest moderate loading speed. Overall, the technical infrastructure is modern but requires urgent security upgrades and performance tuning.
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 webroot.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 webroot.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.