Skip to main content

Security report for qw.cz

Technology · Czech Republic

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

Security score

41/100

Risk levelHigh

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

The website qw.cz represents a hosting server service with minimal online presence. The domain is long-established since 2001 and registered with a Czech hosting registrar, REG-WEDOS, indicating a stable business foundation. The site content is extremely limited, consisting mainly of a title, a brief description, and a contact email, with no additional business or security information provided. Technically, the site lacks modern features such as HTTPS, security headers, or any form of privacy or cookie policies, which significantly impacts its security posture and user trust. There are no visible analytics or advertising tools, and no forms or interactive elements, suggesting a very basic web presence. Overall, the site appears to be a simple informational placeholder for a hosting service without advanced digital maturity or security measures.

Scanned

NIS2 and GDPR posture

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

11 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 qw.cz

This scan found 27 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
52
Security headers
15
Email security
60
DNS health
75
Network security
20
GDPR outside view
25
Average
41

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 business behind qw.cz appears to be a small-scale hosting service provider operating in the Czech Republic. The domain age and registrar align with a legitimate hosting business. However, the lack of detailed business information, certifications, or trust indicators limits insight into market positioning or competitive advantages. The business model is service-oriented, targeting general users seeking hosting solutions. There is no evidence of partnerships or subsidiaries. The minimal web presence suggests either a legacy or low-priority digital footprint.

Security posture

The security posture of the website is weak due to the absence of HTTPS, security headers, and any documented security policies. No incident response or vulnerability disclosure mechanisms are present. The lack of privacy and cookie policies indicates non-compliance with GDPR and other data protection regulations. While no explicit vulnerabilities or malware were detected, the minimal security controls and outdated web presence pose risks. The site would benefit from implementing basic security best practices and compliance measures to improve trust and reduce risk.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate to secure user connections.
  2. Add comprehensive privacy and cookie policies to comply with GDPR and inform users.
  3. Introduce security headers such as Content-Security-Policy and X-Frame-Options to enhance protection.
  4. Enhance website content and design to improve user experience and trustworthiness.
  5. Establish incident response contact channels and vulnerability disclosure policies.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
The website appears to represent a hosting server service under the domain qw.cz, providing hosting services.
Key services
hosting server
Content quality
poor
Branding
moderate

Technology

Performance
moderate
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
30/100

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 minimal and serves as a placeholder or basic informational page.
  2. No privacy, cookie, or terms of service policies are present.
  3. Contact information is limited to a single email address.
  4. No security headers or HTTPS status provided; likely HTTP only or unknown SSL status.
  5. No analytics, tracking, or advertising scripts detected.
  6. No forms or data collection mechanisms present.
  7. WHOIS data indicates a stable, long-registered domain with a Czech hosting registrar.
  8. No signs of WAF or blocking mechanisms detected.
Technical notes

Notes

The website uses a very basic HTML structure with no detected CMS, frameworks, or modern technologies. Hosting is provided by REG-WEDOS, a Czech hosting provider. The site lacks mobile optimization and accessibility features, and SEO is minimal due to missing meta tags and structured data. Performance is likely moderate given the simplicity but could be improved with modern web standards. There is technical debt in the form of outdated content and missing security implementations. Modernization opportunities include adopting HTTPS, responsive design, and enhanced metadata for SEO and accessibility.
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 qw.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 qw.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.