Skip to main content

Security report for cloudaccess.host

Cloud Access LLC · Technology · United States

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

Security score

51/100

Risk levelMedium

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

Cloud Access LLC operates the domain cloudaccess.host, which appears to be a technology-focused business likely providing cloud hosting or related services. However, the website content is inaccessible, presenting a 403 Forbidden error indicating restricted access or directory protection. This limits the ability to assess the business's public-facing digital presence or service offerings. Technically, the site runs on Apache but lacks HTTPS support due to an invalid or missing SSL certificate, which is a critical security deficiency. DNS configuration is basic but lacks DNSSEC and has malformed CAA records, further reducing security posture. No privacy, cookie, or terms of service policies are present, indicating poor compliance with privacy regulations. WHOIS data shows a mature domain registered to Cloud Access LLC in the US, consistent with a legitimate business entity. Overall, the site exhibits a low security and compliance maturity level with critical issues that must be addressed to improve trust and accessibility.

Scanned

NIS2 and GDPR posture

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

7 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 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';…

  2. 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

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

Keep watching cloudaccess.host

This scan found 22 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
85
Security headers
15
Email security
70
DNS health
75
Network security
20
GDPR outside view
40
Average
51

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

The domain cloudaccess.host is owned by Cloud Access LLC, a US-based technology company established in 2014. The company likely operates in the cloud hosting sector, inferred from the domain and MX records. The domain is mature and registered with a reputable registrar, indicating stability. However, the lack of accessible website content and absence of public business information limit visibility into market positioning, revenue streams, or customer segments. No partner or subsidiary domains were identified. The business model and target audience cannot be determined from the available data. The company should improve its digital presence to enhance market reach and credibility.

Security posture

The security posture of cloudaccess.host is weak. The absence of a valid SSL certificate and HTTPS support exposes users to potential interception and data integrity risks. The lack of security headers and missing DMARC record increase susceptibility to email spoofing and other attacks. DNSSEC is not enabled, and CAA records are malformed, reducing DNS security. No incident response or vulnerability disclosure information is available, indicating limited transparency and preparedness. The site is currently inaccessible due to a 403 Forbidden error, which may be intentional for security but also limits user access. Immediate remediation of SSL/TLS configuration and DNS security settings is recommended to improve the security baseline.

Recommendations

  1. Obtain and install a valid SSL/TLS certificate to enable HTTPS and secure user connections.
  2. Enable and configure HSTS with includeSubDomains and preload to enforce secure connections.
  3. Implement DMARC, SPF, and DKIM records to protect email domain from spoofing and phishing.
  4. Enable DNSSEC to enhance DNS integrity and prevent cache poisoning attacks.
  5. Correct and properly configure CAA DNS records to restrict certificate issuance.
  6. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  7. Publish privacy, cookie, and terms of service policies to improve compliance and user trust.
  8. Provide accessible contact information and incident response channels for security reporting.
  9. Review and adjust server permissions to allow appropriate public access or provide clear user guidance.
Technical notes

Notes

The website is hosted on an Apache server with a single IPv4 address (199.116.78.60). The DNS setup includes MX records pointing to cloudaccess.net mail servers and name servers under gridfast.net. However, DNSSEC is not enabled, and CAA records are malformed, indicating incomplete DNS security configuration. The SSL certificate is invalid or missing, and no TLS protocols are supported, resulting in no HTTPS availability. The HTTP headers are minimal and lack advanced security headers. Performance metrics are unavailable, suggesting no content delivery or blocked content. No CMS or frameworks are detected, and no analytics or tracking scripts are present. The site appears to be in a restricted or maintenance state, limiting technical evaluation. Overall, the infrastructure requires modernization and security hardening to meet current web standards.
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 cloudaccess.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 cloudaccess.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.