Skip to main content

Security report for qiata.com

Error: 404 Page not found · Other · N/a

High risk. 8 critical or high findings in Email security, Network security and 2 other checks.

Security score

49/100

Risk levelHigh

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

The website at qiata.com currently serves only a 404 Page Not Found error with no accessible business content or metadata. The site uses Joomla CMS with the Helix Ultimate template framework and includes Bootstrap and Font Awesome libraries. The SSL configuration supports TLS 1.2 with a strong cipher suite but lacks modern features such as TLS 1.3, HSTS, OCSP stapling, and DNSSEC, indicating a basic security posture. No privacy, cookie, or terms of service policies are present, nor is there any contact or business information available on the site. Performance is slow with a page load time of approximately 4.8 seconds. Overall, the site lacks content, security best practices, and compliance indicators, resulting in a low trustworthiness and professionalism rating.

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

8 findings rated critical or high. Fix these first.

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

  2. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

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

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

Keep watching qiata.com

This scan found 21 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
92
Security headers
40
Email security
60
DNS health
85
Network security
50
GDPR outside view
40
Average
61
After the cap
49

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 · found on this site
  • 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 absence of accessible content and business information, no meaningful business intelligence can be derived. There are no indications of market positioning, business model, target audience, or partnerships. The site appears inactive or misconfigured, limiting any competitive or operational insights.

Security posture

The security posture is basic with HTTPS enabled and use of a strong cipher suite. However, critical security enhancements are missing, including HSTS, OCSP stapling, DNSSEC, CAA records, and security headers. No vulnerabilities such as Heartbleed or FREAK were detected. The lack of security policies, incident response contacts, and vulnerability disclosure mechanisms further weakens the security maturity. The site is vulnerable to downgrade attacks and lacks protections against common web threats.

Recommendations

  1. Enable and enforce HSTS with includeSubDomains and preload to protect against protocol downgrade attacks.
  2. Implement OCSP stapling to improve TLS certificate revocation checking and reduce latency.
  3. Configure DNSSEC and CAA records to enhance DNS security and certificate issuance control.
  4. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Publish privacy, cookie, and terms of service policies to improve compliance and user trust.
  6. Add clear contact information and incident response channels to support security and customer communications.
  7. Improve website content and navigation to provide meaningful business information and enhance user experience.
  8. Optimize website performance to reduce load times and improve accessibility.
Technical notes

Notes

The website is built on Joomla CMS using the Helix Ultimate template framework, incorporating Bootstrap and Font Awesome for styling and icons. The SSL certificate covers both qiata.com and www.qiata.com with 240 days until expiry and supports TLS 1.2 only. The site lacks modern TLS 1.3 support and security enhancements such as HSTS and OCSP stapling. DNS records show no MX or TXT records, and DNSSEC is not enabled. The page load time is slow at 4.8 seconds with only 10 resources and a small page size of ~81 KB. The HTML content is minimal and indicates a 404 error page with no metadata, structured data, forms, or external links. Overall, the technical implementation is basic and requires modernization and content restoration.
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 qiata.com. 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 qiata.com.

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.