Skip to main content

Security report for keyrock.eu

Keyrock · Finance · N/a

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

Security score

81/100

Risk levelLow

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

Keyrock is a medium-sized company specializing in providing liquidity solutions and market making services in the digital asset and cryptocurrency space since 2017. Positioned as a leading change-maker, it serves institutions and foundations with tailored financial technology solutions across centralized and decentralized venues. The website reflects a professional and modern digital presence with strong branding and clear communication of services. Technically, the site is built on WordPress with Vue.js components, optimized for performance, mobile responsiveness, and SEO. Security posture is solid with HTTPS enforced and domain protections in place, though improvements such as DNSSEC and explicit security policies could enhance trust further. Privacy compliance is well addressed with clear privacy and cookie policies and GDPR adherence. Overall, the site projects high trustworthiness and professionalism.

Scanned

NIS2 and GDPR posture

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

3 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 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 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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching keyrock.eu

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. 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
75
Security headers
65
Email security
85
DNS health
90
Network security
100
GDPR outside view
68
Average
81

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

Keyrock operates in the finance and technology sectors, focusing on digital asset liquidity and market making. Its business model revolves around providing algorithm-driven liquidity solutions, OTC trading, options desks, and treasury management to institutional clients. The company has established partnerships with major cryptocurrency exchanges, enhancing its market reach and credibility. Growth indicators include a sizable team of 170+ experts and global presence across EU, UK, and Switzerland. The company emphasizes innovation, integrity, and scalability, supported by reputable investors and FCA registration, positioning it strongly in the competitive digital finance market.

Security posture

The website demonstrates a mature security posture with HTTPS enforced, domain lock statuses (clientDeleteProhibited, clientTransferProhibited), and no visible exposure of sensitive data. However, DNSSEC is not enabled, which is a recommended enhancement for DNS security. The absence of a published security policy or incident response contact limits transparency in security governance. Use of third-party scripts like Google Tag Manager is standard but requires ongoing monitoring for vulnerabilities. No vulnerabilities or security incidents were detected in the content. Overall, the security posture is good but could benefit from formalized policies and additional DNS security measures.

Recommendations

  1. Enable DNSSEC to strengthen DNS security and prevent spoofing.
  2. Publish a dedicated security policy and incident response contact information to improve transparency and trust.
  3. Implement a vulnerability disclosure program or security.txt file to facilitate responsible reporting.
  4. Add additional HTTP security headers such as Content-Security-Policy and X-Content-Type-Options.
  5. Regularly audit and update third-party scripts and dependencies to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Keyrock
Description
Scaling liquidity and pricing assets since 2017. We enhance digital markets. Backed by time-tested algorithms and ironclad tech. Market making - OTC - Options
Key services
Market making, OTC trading, Options desk, Treasury solutions, Liquidity pool management, Ecosystem development, NFT liquidity
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Vue.js, Yoast SEO, Google Tag Manager, Cloudflare DNS
Frameworks
Vue.js
Platforms
WordPress
Performance
fast
Mobile
excellent
Accessibility
good
SEO
excellent

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain locked with clientDeleteProhibited and clientTransferProhibited
  • No exposed sensitive data in HTML
  • Use of Google Tag Manager with async loading

Analytics and tracking

Services
Google Analytics (via Google Tag Manager)
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
Yoast SEO
Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is professionally designed and well-structured
  2. Content is comprehensive and relevant to digital asset liquidity services
  3. Strong presence of trust indicators including FCA registration and investor backing
  4. No signs of malicious or suspicious content
  5. Good SEO and accessibility practices observed
  6. No direct company emails or phone numbers found, contact primarily via form and social media
  7. No explicit security or incident response policies published
Technical notes

Notes

The website is built on a WordPress CMS enhanced with Vue.js for frontend interactivity, leveraging Yoast SEO for search optimization and Google Tag Manager for analytics. Hosting and domain registration are managed via Amazon Registrar and Cloudflare DNS services, ensuring reliable infrastructure. The site is well-optimized for performance and mobile devices, with responsive design and accessibility considerations. The technical stack is modern and appropriate for the business needs, with no apparent technical debt or performance bottlenecks. Opportunities exist to further modernize security configurations and enhance incident response readiness.
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 keyrock.eu. 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 keyrock.eu.

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.