Skip to main content

Security report for holo.host

Holo Host · Technology · United States

Low risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

77/100

Risk levelLow

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

Holo Host is a technology company specializing in community owned cloud hosting infrastructure tailored for Holochain and decentralized applications. The company positions itself as an ethical and sovereign alternative to traditional centralized cloud providers, targeting organizations and developers who prioritize data ownership, privacy, and freedom from big tech monopolies. Their key services include dedicated Holo Cloud Nodes and the Holo Web Bridge, enabling resilient and user-owned digital infrastructure. The business is affiliated with the Holochain Foundation and has been operational since 2017, with a small but focused market presence. Technically, the website employs modern JavaScript technologies, integrates Google Analytics with user consent, and uses Cloudflare DNS and Cloudfront for content delivery. The site is mobile optimized with good SEO practices and clear navigation. However, no major CMS or frameworks are detected, indicating a custom-built solution. Performance is moderate, and accessibility is basic but adequate. From a security perspective, the site enforces HTTPS and uses clientTransferProhibited status on the domain. Cookie consent mechanisms are implemented, but security headers are not explicitly detected, and no published security or incident response policies are found. The WHOIS data shows privacy protection but is consistent with the business profile and domain age. No vulnerabilities or suspicious patterns are evident. Overall, Holo Host demonstrates a solid digital maturity level with good privacy compliance and business credibility. Strategic improvements in security policy transparency and DNSSEC enablement could further enhance trust and resilience.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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 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 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. 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 holo.host

This scan found 18 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
45
Email security
80
DNS health
80
Network security
100
GDPR outside view
83
Average
77

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

Holo Host operates in the niche decentralized hosting sector, leveraging community ownership and ethical technology values as competitive advantages. Their business model focuses on providing infrastructure for Holochain apps and decentralized systems, appealing to organizations seeking digital sovereignty. Revenue likely derives from hosting service subscriptions and enterprise partnerships. The company maintains strategic partnerships with organizations like Visvere and HummHive, enhancing its ecosystem and market reach. The affiliation with the Holochain Foundation strengthens credibility and aligns with open-source community values. Growth indicators include active content updates, partner testimonials, and a clear roadmap. The company emphasizes resilience, privacy, and reduced dependence on big tech, positioning itself uniquely in the Web3 infrastructure market.

Security posture

Holo Host exhibits a moderate to good security posture. HTTPS is enforced site-wide, and domain transfer protections are in place. Cookie consent is implemented, reflecting privacy awareness. However, the absence of DNSSEC and security headers such as Content-Security-Policy or X-Frame-Options represents areas for improvement. No explicit security policies or incident response contacts are published, which could hinder transparency and trust in security incident handling. No vulnerabilities or exposed sensitive data were detected in the HTML content. The use of third-party scripts like Google Analytics and EngageBay is managed with consent mechanisms. Overall, the security culture appears adequate but would benefit from enhanced policy publication and technical hardening.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement and publish a formal security policy and incident response plan accessible on the website.
  3. Add standard security headers (Content-Security-Policy, X-Frame-Options, X-XSS-Protection) to HTTP responses.
  4. Consider publishing a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Enhance accessibility features and conduct regular security audits to maintain compliance and resilience.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Holo Host
Description
Holo offers community owned cloud hosting infrastructure for Holochain and decentralized apps. Built for organizations that value digital sovereignty, ethical design, and freedom from monopolistic platforms.
Key services
Holo Cloud Nodes, Holo Web Bridge, Hosting Services for Holochain and decentralized apps
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Google Analytics (GA4), Cloudflare DNS, EngageBay (marketing automation), Survey form scripts from cloudfront.net
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • Cookie consent banner with opt-in
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics (GA4)
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
EngageBay
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is focused on decentralized hosting infrastructure and ethical technology.
  3. Clear navigation with multiple calls to action for demos and hosting services.
  4. Privacy and cookie policies are present with consent mechanisms.
  5. No direct contact emails or phone numbers found; contact via forms only.
  6. Use of modern analytics and marketing tools with consent.
  7. No explicit security policy or incident response information published.
  8. WHOIS data shows privacy protection but domain age and registrar are consistent with legitimacy.
Technical notes

Notes

The website is built with modern JavaScript and integrates third-party services such as Google Analytics (GA4) and EngageBay for marketing automation. Content delivery leverages Cloudflare DNS and Cloudfront CDN, ensuring reasonable performance and availability. The site is mobile responsive with good SEO metadata including Open Graph and Twitter Card tags. No major CMS or frameworks were detected, indicating a custom or lightweight architecture. Performance is moderate, with some opportunities for optimization. The technical stack supports the business model effectively but could benefit from additional security and accessibility enhancements to reduce technical debt and improve user experience.
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 holo.host. 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 holo.host.

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.