Skip to main content

Security report for cydeckt.com

CardivAI GmbH · Healthcare · N/a

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

Security score

41/100

Risk levelHigh

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

CardivAI GmbH operates in the healthcare technology sector, specializing in generative AI-driven diagnostics for cardiovascular diseases. Their offerings include AI integrations, AWS cloud-based solutions architecture, and DevOps services tailored for mobile-first healthcare applications. The company positions itself as a niche provider leveraging advanced AI models such as Anthropic's Claude 4 and AWS infrastructure to deliver innovative healthcare diagnostics solutions. The website content and branding reflect a professional and consistent image targeting healthcare professionals and technology adopters in the medical diagnostics field. Technically, the website is hosted on AWS infrastructure using Amazon S3 and CloudFront, with modern frontend technologies including Bootstrap, Swiper, and JavaScript libraries for UI enhancements. Google Tag Manager and CookieYes scripts indicate moderate analytics and cookie consent management. However, the site lacks HTTPS support, which is a significant technical and security shortfall. Mobile optimization and SEO appear adequate, but performance metrics are unavailable. From a security perspective, the absence of a valid SSL/TLS certificate and HTTPS severely impacts the security posture, exposing users to potential data interception risks. No advanced security headers or protocols are implemented, and no incident response or vulnerability disclosure policies are evident. The use of AWS server-side encryption for content storage is a positive aspect, but overall security maturity is low. Privacy compliance is basic with cookie consent but lacks explicit GDPR compliance indicators. Overall, the website presents a credible business with professional content and clear contact information but requires urgent improvements in security, particularly enabling HTTPS and enhancing security headers. Strategic recommendations include implementing SSL/TLS, adopting security best practices, and formalizing privacy and incident response policies to improve trust and compliance.

Scanned

NIS2 and GDPR posture

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

9 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 cydeckt.com

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

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 cydeckt.com, from OffSeq Breach.

No leaked records found

Breach holds no records for cydeckt.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

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

CardivAI GmbH operates in a specialized niche combining healthcare diagnostics with generative AI and cloud computing. Their market positioning leverages AWS cloud services and advanced AI models to deliver innovative solutions for cardiovascular disease risk assessment. The business model focuses on B2B engagements with healthcare providers and technology partners. Key revenue streams likely include AI integration services, cloud architecture consulting, and DevOps implementations. The company demonstrates growth potential through its use of cutting-edge AI technologies and certifications in AWS solutions and DevOps. Partnerships appear limited to AWS and possibly Anthropic for AI models. The company maintains a professional online presence with active social media channels, supporting brand visibility and customer engagement. Strategic observations suggest a focus on innovation and cloud-native healthcare solutions, with opportunities to expand market reach by enhancing security and compliance frameworks.

Security posture

The current security posture of the website is weak due to the lack of HTTPS/SSL encryption, which is critical for protecting data in transit. The absence of security headers such as Content-Security-Policy and X-Frame-Options increases exposure to common web attacks. No evidence of incident response or vulnerability disclosure mechanisms reduces preparedness for security incidents. While AWS server-side encryption is used for content storage, this does not mitigate the risk of unencrypted HTTP traffic. Cookie consent is implemented, but GDPR compliance is not clearly demonstrated. The site does not employ modern TLS protocols or session resumption features, further weakening security. Overall, the security maturity is low, posing risks to user data confidentiality and trust. Immediate remediation is required to enable HTTPS and implement security best practices to align with industry standards and regulatory requirements.

Recommendations

  1. Implement a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Configure HTTP security headers including Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  3. Enable HSTS with includeSubDomains and preload directives to enforce HTTPS.
  4. Develop and publish a comprehensive privacy policy with explicit GDPR compliance statements.
  5. Establish an incident response plan and provide clear contact channels for security issues.
  6. Regularly audit and update third-party scripts and dependencies to avoid vulnerabilities.
  7. Enhance accessibility features and conduct performance optimization to improve user experience.
  8. Expand contact information to include phone numbers and physical addresses for better credibility.
  9. Consider publishing a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  10. Maintain consistent branding and update content regularly to reflect business developments.
Technical notes

Notes

The website is hosted on AWS infrastructure using Amazon S3 for storage and CloudFront as CDN, indicating a scalable and reliable hosting environment. The frontend leverages Bootstrap for responsive design, along with JavaScript libraries such as Swiper for sliders, Rellax for parallax effects, and Jarallax for background effects, providing a modern user interface. Google Tag Manager is used for analytics and marketing tag management, while CookieYes manages cookie consent. Despite these modern technologies, the lack of HTTPS is a critical technical deficiency. Performance data is unavailable, but the use of CDN and optimized assets suggests potential for good loading speeds. The site lacks a CMS, indicating a static or custom-built frontend. Opportunities exist to improve technical maturity by enabling HTTPS, enhancing security headers, and improving accessibility compliance.
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 cydeckt.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 cydeckt.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.