Skip to main content

Security report for sherlock.xyz

Sherlock Protocol · Technology · N/a

Medium risk. 5 critical or high findings in GDPR outside view and SSL/TLS.

Security score

71/100

Risk levelMedium

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

Sherlock Protocol is a leading blockchain security company specializing in smart contract audits, audit contests, bug bounty programs, and exploit coverage for Web3 protocols. Founded in 2020, it has established itself as a trusted partner for top blockchain projects such as Ethereum Foundation, Aave, Optimism, and MakerDAO. The company offers a comprehensive suite of security services including its Blackthorn private security firm and Sherlock Shield coverage, positioning itself as a global leader in blockchain security solutions. Technically, the website is built on Webflow with modern JavaScript libraries such as GSAP for animations and Swiper.js for interactive content. It leverages Cloudflare for DNS and likely CDN services, ensuring good performance and security. The site is mobile-optimized, accessible, and well-structured with professional design and clear navigation. Analytics and tracking tools include Google Tag Manager, Hotjar, and LinkedIn Insight, indicating moderate user tracking. From a security perspective, the site uses HTTPS and has domain protections like clientTransferProhibited and clientDeleteProhibited status. However, it lacks DNSSEC, explicit security headers, and published privacy or cookie policies, which are areas for improvement. No security.txt or vulnerability disclosure page is present, limiting transparency for security incident reporting. Overall, Sherlock Protocol presents a high level of business credibility and technical maturity with strong trust signals from client testimonials and partnerships. The main risks relate to privacy compliance and some missing security best practices. Strategic recommendations include publishing comprehensive privacy and cookie policies, enabling DNSSEC, adding security headers, and establishing a vulnerability disclosure mechanism to enhance trust and compliance.

Scanned

NIS2 and GDPR posture

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

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.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Twitter, LinkedIn, Google APIs

      What to do: Document all third-party data sharing in your privacy policy

  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.

    • 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 sherlock.xyz

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
75
Security headers
60
Email security
75
DNS health
80
Network security
100
GDPR outside view
35
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 sherlock.xyz, from OffSeq Breach.

No leaked records found

Breach holds no records for sherlock.xyz 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

Sherlock Protocol operates in the blockchain security sector, targeting Web3 projects and DeFi platforms. Its competitive advantage lies in combining top-ranked security researchers with innovative audit contest models and private security services (Blackthorn). The business model is service-based, generating revenue from audits, contests, bug bounties, and coverage products. The company has a strong partnership ecosystem, including Blackthorn and relationships with leading protocols. Growth indicators include a large number of critical vulnerabilities found and significant rewards paid out to researchers. The company emphasizes transparency, collaboration, and innovation in security competitions, positioning itself as a market leader with a focus on quality and trust.

Security posture

Sherlock Protocol demonstrates a mature security posture with HTTPS enforced and domain-level protections in place. The company uses Cloudflare DNS with transfer and delete prohibitions, reducing domain hijacking risks. However, the absence of DNSSEC and security headers such as Content-Security-Policy or X-Frame-Options indicates room for improvement. No explicit incident response or security policy documentation is publicly available, which could hinder rapid response and transparency. The lack of a security.txt or vulnerability disclosure page limits external reporting channels. Overall, the security culture appears strong internally, supported by a network of top security researchers, but public-facing security documentation and controls should be enhanced to meet best practices and compliance standards.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy with explicit consent mechanisms to improve GDPR and privacy compliance.
  2. Enable DNSSEC on the domain to strengthen DNS security and prevent spoofing.
  3. Implement standard security headers (e.g., Content-Security-Policy, X-Frame-Options, Strict-Transport-Security) to enhance web security posture.
  4. Create and publish a security.txt file or dedicated vulnerability disclosure page to facilitate responsible reporting and incident response.
  5. Consider adding direct contact emails or phone numbers for security and general inquiries to improve accessibility and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Sherlock Protocol
Description
Sherlock provides blockchain security solutions including expert audits, audit contests, bug bounties, and exploit coverage for Web3 protocols. They serve top Web3 companies and protocols with a suite of security services.
Key services
Blackthorn private security firm, Collaborative Audits, Audit Contests, Bug Bounties, Sherlock Shield coverage
Content quality
excellent
Branding
consistent

Technology

Stack
Webflow, GSAP (GreenSock Animation Platform), Swiper.js, Google Tag Manager, Hotjar, LinkedIn Insight Tag, Fubi (accessibility tool)
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enabled
  • Use of Cloudflare DNS with clientTransferProhibited and clientDeleteProhibited domain status

Analytics and tracking

Services
Google Analytics (via GTM), Hotjar, LinkedIn Insight
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
LinkedIn Insight Tag, Hotjar
Marketing tools
Hotjar, LinkedIn Insight
Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed and fully accessible.
  2. No privacy or cookie policies found, indicating compliance gaps.
  3. Contact information is only via contact form; no direct emails or phone numbers found.
  4. Strong trust signals via client testimonials and partner mentions.
  5. Use of modern web technologies and analytics tools.
  6. No security.txt or vulnerability disclosure page found.
  7. No explicit security headers detected in provided data.
  8. Domain WHOIS data supports legitimacy and consistent business presence.
Technical notes

Notes

The website is built using Webflow CMS, leveraging modern JavaScript libraries such as GSAP for animations and Swiper.js for interactive sliders. It uses Google Fonts (Inter family) for typography and is hosted behind Cloudflare DNS servers, indicating reliable hosting and CDN usage. Analytics and tracking are implemented via Google Tag Manager, Hotjar, and LinkedIn Insight, providing comprehensive user behavior insights. The site is mobile-optimized with responsive design and accessibility considerations, including the use of the Fubi accessibility tool. Performance appears fast with optimized images and asynchronous script loading. Technical risks include missing DNSSEC and lack of explicit security headers, which could be addressed to reduce attack surface and improve 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

Earlier scans of this domain

  1. 71/100Medium27 findingsView report
Reviews of this site

Share your experience with sherlock.xyz. 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 sherlock.xyz.

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.