Skip to main content

Security report for customercare.co

Customer Care Corp · Other · Canada

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

Security score

68/100

Risk levelMedium

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

CustomerCare.co operates as a centralized account management platform primarily serving users of a broad network of adult entertainment websites. The service allows users to manage their subscriptions, usernames, passwords, and email addresses across multiple partner sites, streamlining user experience in a niche market. The company behind the domain is KB Productions, based in Canada, with a domain registration dating back to 2012, indicating an established presence in this sector. Technically, the website employs standard web technologies including Bootstrap for UI components, Font Awesome for icons, and Google reCAPTCHA for bot mitigation. Hosting appears to leverage Amazon AWS DNS infrastructure. While the site is accessible and functional with basic mobile optimization and navigation clarity, it lacks advanced SEO and accessibility features. The password input field is insecurely implemented as a text field, posing a risk to user data confidentiality. From a security perspective, the site enforces HTTPS and uses reCAPTCHA, but lacks DNSSEC and important security headers such as Content-Security-Policy and Strict-Transport-Security. No explicit security policies or incident response contacts are published, and no cookie consent mechanism is present, which may impact GDPR compliance. The WHOIS data is consistent and transparent, supporting the legitimacy of the domain and business. Overall, CustomerCare.co presents a functional but basic service with moderate trustworthiness. Key improvements in security practices, privacy compliance, and user data protection are recommended to enhance the platform's credibility and safeguard user information.

Scanned

NIS2 and GDPR posture

GDPR outside view
58/ 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 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching customercare.co

This scan found 22 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
72
Security headers
30
Email security
70
DNS health
80
Network security
100
GDPR outside view
58
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

CustomerCare.co occupies a niche position within the adult entertainment industry by providing a centralized account management service that aggregates multiple adult content websites under one user interface. This business model simplifies subscription management for users and likely generates revenue through service fees or partnerships with the networked sites. The company, KB Productions, has maintained domain registration since 2012, suggesting stable operations. The target audience is adult content consumers who value convenience and centralized control over multiple subscriptions. The absence of direct contact emails or phone numbers and reliance on web forms may limit customer support transparency. The partnership ecosystem is implied through the extensive list of partner sites selectable in the account management form, indicating a broad network. Growth potential depends on improving security, privacy compliance, and expanding service offerings.

Security posture

The security posture of CustomerCare.co is moderate but with notable gaps. HTTPS is properly enforced, and Google reCAPTCHA is implemented to reduce automated abuse. However, the password input field is insecurely configured as a plain text field, exposing sensitive user credentials during input. The absence of DNSSEC and security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces the site's resilience against common web attacks. No published security policies, incident response contacts, or vulnerability disclosure programs were found, indicating limited transparency and preparedness for security incidents. Privacy compliance is weak due to the lack of cookie consent mechanisms and minimal GDPR indicators. Addressing these issues is critical to protect user data and maintain trust.

Recommendations

  1. Change the password input field type from 'text' to 'password' to secure user credential entry.
  2. Implement DNSSEC to enhance domain name system security and prevent DNS spoofing.
  3. Add essential security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Publish clear privacy and cookie policies with consent mechanisms to improve GDPR compliance.
  5. Establish and publicize an incident response contact channel and vulnerability disclosure policy to enhance security transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Customer Care Corp
Description
CustomerCare.co provides account management services for a large network of adult entertainment websites, allowing users to manage their subscriptions and account details across multiple partner sites.
Key services
Account management, Password and username retrieval, Multi-site subscription management
Content quality
basic
Branding
moderate

Technology

Stack
Google reCAPTCHA, Font Awesome, Zapier Interfaces Web Components
Frameworks
Bootstrap (implied by navbar classes)
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
55/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA on forms
  • Domain status flags to prevent unauthorized transfer or deletion

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Marketing tools
Zapier Interfaces chatbot embed
Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
basic
Navigation
good
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. Website serves as a centralized account management portal for multiple adult entertainment sites.
  2. No direct contact emails or phone numbers found; contact is via web form only.
  3. Password field is insecurely implemented as text input.
  4. No privacy or cookie consent banners detected despite GDPR relevance.
  5. Use of Google reCAPTCHA indicates some bot mitigation efforts.
  6. No explicit security policies or incident response information published.
  7. WHOIS data is transparent and consistent with business claims.
Technical notes

Notes

The website uses a conventional tech stack with Bootstrap for responsive UI components, Font Awesome for icons, and Google reCAPTCHA for bot protection. Hosting is supported by Amazon AWS DNS infrastructure, providing reliable DNS services. The site lacks a detected CMS, indicating a custom or static site architecture. Performance is moderate with basic mobile optimization and accessibility features. SEO optimization is minimal, with no Open Graph or JSON-LD structured data detected. The use of Zapier Interfaces chatbot suggests some integration with marketing or customer support automation tools. Technical debt is indicated by insecure form input types and missing security headers, which should be addressed to reduce operational risks.
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 customercare.co. 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 customercare.co.

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.