Skip to main content

Security report for arsy.cz

Other · N/a

High risk. 9 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

47/100

Risk levelHigh

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

The website www.arsy.cz is currently inaccessible, returning a 403 Forbidden error page which blocks access to any meaningful content or business information. The lack of WHOIS data further complicates verification of domain ownership and legitimacy. Due to these access restrictions, no metadata, structured data, or contact details are available for analysis. This severely limits the ability to assess the company's business model, services, or market position. From a technical perspective, the site does not expose any detectable technologies, scripts, or frameworks, and no security headers or SSL configuration details are available. The absence of privacy, cookie, or terms of service policies indicates a lack of compliance readiness. The security posture is weak due to the inability to verify HTTPS usage or security best practices. Overall, the risk assessment is high due to the blocked content and missing WHOIS data, which raises concerns about domain legitimacy and operational status. Strategic recommendations include resolving the access restrictions, publishing essential compliance and security policies, and ensuring proper domain registration transparency to improve trust and security posture.

Scanned

This is an earlier scan of arsy.cz. View the latest report

NIS2 and GDPR posture

GDPR outside view
15/ 100 · Critical
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

9 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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

  2. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

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

Keep watching arsy.cz

This scan found 24 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
95
Security headers
15
Email security
60
DNS health
75
Network security
20
GDPR outside view
15
Average
47

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

Due to the 403 Forbidden error and missing WHOIS data, no reliable business intelligence can be derived. The domain appears inactive or misconfigured, with no visible market positioning, competitive advantages, or partnership information. No revenue streams or customer segments can be identified. The lack of accessible content and contact information suggests the business is either not operational online or intentionally restricted.

Security posture

The current security posture is poor. The site is inaccessible, preventing verification of HTTPS, security headers, or vulnerability status. No incident response or security policy information is published. The absence of privacy and cookie policies indicates non-compliance with GDPR and other regulations. The domain's WHOIS data is missing, which is a red flag for legitimacy and trust. Immediate remediation is required to enable secure access and publish necessary security documentation.

Recommendations

  1. Resolve the 403 Forbidden error to restore website accessibility.
  2. Ensure the domain WHOIS information is complete and publicly available to enhance trust.
  3. Implement HTTPS with a valid SSL certificate and configure security headers.
  4. Publish privacy, cookie, and terms of service policies to comply with regulations.
  5. Provide clear contact and incident response information to support security and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. The website returns a 403 Forbidden error page indicating access is blocked or restricted. No specific WAF vendor identified. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to 403 Forbidden error.
  2. No metadata, structured data, or SEO tags present.
  3. No forms, contact information, or external links found.
  4. No scripts or technologies detected from the minimal HTML.
  5. No privacy, cookie, or terms policies found.
  6. No security headers or SSL information available.
  7. WHOIS data is missing or unavailable, limiting domain legitimacy assessment.
Technical notes

Notes

The website currently serves only a minimal 403 Forbidden error page with no detectable technologies, scripts, or CMS. No meta tags or structured data are present. The lack of content and technical metadata indicates either a misconfigured server or intentional access restriction. No hosting provider or platform information can be inferred. Performance, mobile optimization, accessibility, and SEO cannot be assessed due to lack of content.
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. 47/100High33 findingsView report
Reviews of this site

Share your experience with arsy.cz. 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 arsy.cz.

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.