Skip to main content

Security report for ccm19.de

Papoo Software & Media GmbH · Technology · Germany

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

Security score

71/100

Risk levelMedium

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

Papoo Software & Media GmbH operates CCM19, a European-focused cookie consent management software solution designed to ensure GDPR and other privacy law compliance for websites. Positioned as a privacy-conscious alternative to major global providers, CCM19 offers both cloud and on-premise deployment options, emphasizing data sovereignty by hosting exclusively in Germany. The company targets website operators, agencies, and hosting providers seeking customizable and legally compliant consent management tools. Their offerings include a comprehensive cookie consent manager, cookie scanner, Google Fonts checker, and specialized versions for agencies and hosting providers. The website demonstrates a mature digital presence with multilingual support, extensive documentation, and customer testimonials, reflecting a strong market position in the European privacy software niche. Technically, the site employs modern JavaScript libraries and the Foundation framework, with moderate performance and good mobile and accessibility optimizations. Security posture is adequate but shows gaps such as disabled TLS protocols and missing DNSSEC, which should be addressed to enhance trust and compliance. Overall, CCM19 presents a professional, trustworthy, and privacy-centric solution with clear business focus and solid technical foundations.

Scanned

This is an earlier scan of ccm19.de. View the latest report

NIS2 and GDPR posture

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

5 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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

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

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

Keep watching ccm19.de

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. 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
92
Security headers
70
Email security
80
DNS health
90
Network security
75
GDPR outside view
18
Average
71

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 ccm19.de, from OffSeq Breach.

Total records
284
Employees
0
Customers
284
Third parties
0
Weak passwords
1%

5 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 ccm19.de.

Select it in the checkout above.

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

CCM19 is positioned as a specialized technology provider in the privacy compliance sector, focusing on cookie consent management for European markets. Their competitive advantage lies in full data hosting within Germany, compliance with multiple privacy regulations (GDPR, TDDDG, CCPA, BDSG, LGPD, POPIA), and offering both cloud and on-premise solutions. The business model includes subscription-based SaaS and downloadable software with tiered pricing and agency-specific versions supporting multi-tenancy and white-labeling. Revenue streams likely derive from software licenses, support services, integration assistance, and affiliate partnerships. The company maintains a strong partnership ecosystem with recognized privacy and cybersecurity organizations, enhancing credibility. Growth indicators include a large installed base (over 210,000 websites), active customer engagement, and continuous product updates. The company emphasizes customer support and transparency, which supports retention and market trust.

Security posture

The security maturity of CCM19's web presence is moderate. The site uses a valid SSL certificate but currently has no TLS protocols enabled, which is a critical misconfiguration that undermines HTTPS security. DNSSEC is not enabled, and CAA records are improperly configured, reducing DNS security assurances. The site employs HSTS with a strong max-age, which is a positive security control. No known SSL/TLS vulnerabilities such as Heartbleed or POODLE are present. The absence of a published security policy, incident response information, or security.txt file indicates limited transparency in security governance and incident handling. Data protection compliance appears strong, with GDPR-aligned consent mechanisms and data hosting exclusively in Germany. However, improvements in SSL/TLS configuration and explicit security governance disclosures would enhance the overall security posture and trustworthiness.

Recommendations

  1. Enable and properly configure TLS 1.2 or TLS 1.3 protocols to secure HTTPS connections.
  2. Implement DNSSEC to protect against DNS spoofing and improve domain security.
  3. Correct and specify CAA DNS records to restrict certificate issuance to authorized CAs.
  4. Publish a clear security policy and incident response plan, including contact channels for security issues.
  5. Add additional security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to harden the web application.

Contact details published on the site

Addresses
Legal name
Papoo Software & Media GmbH
Technical notes

Notes

The website infrastructure is built on a modern web technology stack including jQuery, Foundation framework, and various JavaScript plugins for UI and functionality enhancements. The CMS appears to be Papoo, a German CMS platform, which aligns with the company's local hosting and data sovereignty focus. Hosting is provided by kasserver.com, a German hosting provider. Performance metrics indicate moderate load times with a relatively high number of resources (72) and page size (~187 KB), suggesting room for optimization. Mobile and accessibility considerations are well addressed, with multilingual support and compliance with accessibility standards. Technical debt is minimal, but the critical SSL/TLS misconfiguration poses operational risks. Opportunities exist to modernize SSL/TLS setup, optimize resource loading, and enhance security headers to improve resilience and user trust.
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. 70/100Medium24 findingsView report
  2. 70/100Medium24 findingsView report
Reviews of this site

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

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.