Skip to main content

Security report for merlinone.com

Canto · Technology · N/a

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

Security score

54/100

Risk levelMedium

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

Canto operates as a leading provider of digital asset management (DAM) solutions, offering a comprehensive SaaS platform designed to help businesses organize, edit, share, and analyze digital content efficiently. The company positions itself as an industry leader with a strong focus on enterprise customers, providing feature-rich tools that enhance content workflows and brand management. The website reflects a professional and consistent brand image with excellent content quality and user experience. Technically, the website is built using modern web technologies including Vue.js and is hosted on Netlify, indicating a contemporary and scalable infrastructure. The site demonstrates good SEO and mobile optimization practices, although performance metrics are not explicitly available. Accessibility is basic but present. The use of structured data and meta tags supports search engine visibility. From a security perspective, the site has several critical shortcomings. Despite having security headers like X-Content-Type-Options and X-Frame-Options, the absence of a valid SSL certificate and lack of HTTPS support severely undermine the security posture. No TLS protocols are enabled, and HSTS is not enforced, exposing users to potential risks. Privacy and cookie policies are comprehensive and GDPR compliant, but no explicit contact emails or phone numbers are provided, relying instead on contact forms. Overall, while the business and technical aspects of the website are strong, the critical lack of SSL/TLS encryption represents a significant risk that must be addressed promptly. Strategic recommendations include immediate SSL certificate installation, enabling modern TLS protocols, and enforcing HSTS to protect user data and maintain trust. Enhancing contact transparency and expanding security frameworks would further strengthen the company's security and compliance posture.

Scanned

NIS2 and GDPR posture

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

4 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

    • 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. 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 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 merlinone.com

This scan found 15 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
55
Email security
50
DNS health
85
Network security
100
GDPR outside view
33
Average
54

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

Canto's market positioning as an industry leader in digital asset management is supported by its comprehensive product offerings and strong customer testimonials. The SaaS business model targets enterprise clients requiring scalable and secure content management solutions. The company leverages partnerships and integrations to enhance its ecosystem. Growth indicators include a well-maintained website with rich content, awards, and active social media presence. The absence of explicit founding year or parent company data limits deeper historical analysis but does not detract from the evident maturity and professionalism of the business.

Security posture

The current security maturity level is low due to the absence of HTTPS and valid SSL certificates, which are fundamental for secure web operations. While some security headers are implemented, critical gaps such as no TLS support, no HSTS enforcement, and lack of OCSP stapling expose the site to man-in-the-middle attacks and downgrade risks. Compliance with GDPR is supported by comprehensive privacy and cookie policies, but incident response readiness is unclear due to lack of explicit security contact channels. The security culture appears to be in early stages of maturity, with room for significant improvement in encryption and vulnerability management.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable TLS 1.2 or higher protocols and disable insecure protocols to protect data in transit.
  3. Implement and enforce HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Set up OCSP stapling to improve certificate revocation checking and reduce latency.
  5. Provide explicit security contact channels and enhance incident response documentation to improve trust and compliance.
Technical notes

Notes

The website uses Vue.js as its primary JavaScript framework, hosted on Netlify, which provides modern deployment and CDN capabilities. The site includes structured data in JSON-LD format for SEO and rich snippets. Performance data is unavailable, but the use of preloading and deferred scripts suggests optimization efforts. Accessibility is basic but present, and SEO optimization is good with proper meta tags and Open Graph data. The lack of a CMS is inferred, likely a static site generated or SPA. Technical risks include missing SSL/TLS and incomplete security header implementation, which could impact user trust and search engine rankings.
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 merlinone.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 merlinone.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.